RecSys Skills

A 12-skill depth pack for ACM RecSys submissions: venue fit against SIGIR/KDD/WSDM/TheWebConf, anonymous ACM two-column submission checks, rebuttal drafting, offline-and-online evaluation rigor, off-policy evaluation, the RecSys Reproducibility track and reproducibility-crisis debates, anonymous code/data artifacts, ACM camera-ready, and project workflow. Grounded in the official RecSys 2026 Call

by @brycewang-stanford 12 skills

Skills in this plugin

12
  1. Recsys Workflow · brycewang-stanford
    Use when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and presentation, with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main, Reproducibility, Industry, Resource, R&P Notes).
    1k repo stars
  2. Recsys Submission · brycewang-stanford
    Use when auditing an ACM RecSys submission before the deadline — routing between the Main, Reproducibility, Industry and Resource tracks, the ACM two-column content-page budgets with appendices counted inside, double-blind anonymization for recommender papers, the anonymous-repository expectation, and desk-reject triage.
    1k repo stars
  3. Recsys Experiments · brycewang-stanford
    Use when designing or auditing ACM RecSys experiments centered on offline-versus-online evaluation — temporal splits, equal-budget baseline tuning, full-ranking versus sampled metrics, off-policy estimators (IPS, SNIPS, doubly robust), A/B tests, exposure and popularity bias, seeds and variance, and matching each recommendation claim to its evidence.
    1k repo stars
  4. Recsys Camera Ready · brycewang-stanford
    Use when preparing an accepted ACM RecSys paper for camera-ready, covering ACM two-column de-anonymization and reflow, the ACM Digital Library rights/copyright form, metadata and DOI, integrating rebuttal-promised fixes without overreach, releasing the previously-anonymous code/data repository publicly, and registration and presentation obligations.
    1k repo stars
  5. Recsys Related Work · brycewang-stanford
    Use when positioning an ACM RecSys submission against recommender-systems literature and its neighbors (SIGIR, KDD, WSDM, TheWebConf, UAI), including the reproducibility-critique line, arXiv and prior versions, concurrent work, ACM Digital Library archival status, and the citation coverage RecSys reviewers expect across recommendation subfields.
    1k repo stars
  6. Recsys Supplementary · brycewang-stanford
    Use when organizing ACM RecSys supporting material under the venue's no-separate-supplement convention — how to split a recommender paper between the body, the appendix that counts inside the page budget, and the anonymous in-paper repository, so tuning grids, extra datasets, and ablations land where reviewers use them.
    1k repo stars
  7. Recsys Writing Style · brycewang-stanford
    Use when revising an ACM RecSys paper for a recommendation-first first page, honest offline-versus-online framing, equal-budget baseline claims, leakage-aware evaluation wording, ACM two-column 8-page compression, double-blind phrasing, and claims scoped to what the ranking evidence actually supports rather than to leaderboard language.
    1k repo stars
  8. Recsys Review Process · brycewang-stanford
    Use when explaining or planning around ACM RecSys peer review — the mutually-anonymous model with at least three PC members and a Senior PC overseer, the rebuttal phase, how the reproducibility-crisis culture shapes reviewer priorities, the offline-versus-online evaluation lens, and how acceptance leads to ACM Digital Library publication.
    1k repo stars
  9. Recsys Author Response · brycewang-stanford
    Use when drafting an ACM RecSys rebuttal during the author-response window, covering the short narrative RecSys allows, anonymity, anchoring answers to submitted evidence and the anonymous repository, the recurring objections about untuned baselines, leakage, and offline-online gaps, and Senior-PC-focused clarification.
    1k repo stars
  10. Recsys Reproducibility · brycewang-stanford
    Use when strengthening the reproducibility of an ACM RecSys paper or preparing a RecSys Reproducibility Track submission — pinning dataset versions and splits, tuning baselines under an equal budget, reporting seeds and variance, avoiding sampled-metric distortion, and structuring a reproduction study with honest divergence analysis.
    1k repo stars
  11. Recsys Topic Selection · brycewang-stanford
    Use when deciding whether a project is a strong ACM RecSys fit, routing among RecSys, SIGIR, KDD, WSDM, TheWebConf, UAI, CHI, and general ML venues, identifying whether the core contribution is genuinely about recommendation, and choosing the right RecSys track before writing begins.
    1k repo stars
  12. Recsys Artifact Evaluation · brycewang-stanford
    Use when packaging ACM RecSys code, datasets, splits, trained models, propensity logs, and seeds as an anonymous in-paper repository during review or a public archive after acceptance, even though RecSys has no separate artifact badge — covering what recommender reviewers open first and how to make a top-N ranking table regenerable end to end.
    1k repo stars