neurips-workflow
Use when planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing, the mandatory Paper Checklist, OpenReview submission, double-blind review, author response, decision, camera-ready, artifact release, and rerouting to the Datasets & Benchmarks track, a workshop, or MLRC/TMLR.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-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.
# NeurIPS Workflow Use this skill as the router for the NeurIPS depth pack. It helps choose the next skill and stage the work so a manuscript does not arrive at submission with hidden policy or evidence gaps. NeurIPS 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: Hsuan-Tien Lin and Razvan Pascanu, verified 2026-06-22), and the cost model is registration fees, not APCs — proceedings are open-access on OpenReview. Conference organizers rotate yearly, so re-check the current CFP and committees page rather than carrying a name forward. ## Stage map 1. Topic and track fit: use `neurips-topic-selection`. 2. Paper shaping: use `neurips-writing-style`, `neurips-related-work`, and `neurips-experiments`. 3. Artifact and supplement planning: use `neurips-artifact-evaluation`, `neurips-reproducibility`, and `neurips-supplementary`. 4. Final pre-submission audit: use `neurips-submission`. 5. Review diagnosis: use `neurips-review-process`. 6. Rebuttal and discussion: use `neurips-author-response`. 7. Acceptance and public release: use `neurips-c
- Stage map
- Operating principles
- Deadline ladder to schedule backward from
- Track-fork early warning
- Worked vignette: where this router intervenes
- Output format
What does the neurips-workflow skill do?
Use when planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing, the mandatory Paper Checklist, OpenReview submission, double-blind review, author response, decision, camera-ready, artifact release, and rerouting to the Datasets & Benchmarks track, a workshop, or MLRC/TMLR.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-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.