recsys-submission
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.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# RecSys Submission Run this audit before anything is uploaded to the RecSys submission system. RecSys is a single-community but multi-track venue: the same manuscript can be legal in one track and desk-rejectable in another, so the audit begins with "which track is this PDF for?" and only then checks format. Reopen the current edition's Call for Contributions — every number below is a 2026-cycle
What does the recsys-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.