recsys-workflow
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).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-workflow --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 Workflow Use this as the project-management skill for a RecSys submission. Replace all dates with the current official timetable and work backwards from the submission-system cutoffs. RecSys is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Chairs (2026 General Chairs:
What does the recsys-workflow skill do?
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).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-workflow --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.