neurips-submission
Use when auditing a NeurIPS main-track submission for current-cycle CFP, OpenReview, formatting, anonymity, track, contribution-type, checklist, code/data, dual-submission, and LLM/agent policy compliance.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-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.
# NeurIPS Submission Use this skill for a submission-readiness audit before a paper enters OpenReview. Treat every annual rule as volatile: reopen the current CFP, Main Track Handbook, paper template, and submission portal before final advice. ## Core checks - Target the right track. NeurIPS main track, Evaluations & Datasets, Position Papers, Reproducibility/MLRC, competitions, workshops, and Journal-to-Conference tracks have separate calls and portals; do not assume transfer is possible after submission. - Confirm that all authors have active OpenReview profiles and that author names are entered by the abstract deadline. After that, only author order may change under the 2026 handbook. - Verify the yearly LaTeX style file, PDF-only submission format, content-page limit, file-size limit, and whether references, text appendices, checklist, and code/data are handled separately. - Confirm double-blind compliance across the main PDF, supplement, repository links, uploaded ZIPs, acknowledgments, self-citations, prompts, demos, model cards, dataset cards, and metadata. - Check dual-submission exposure. Overlapping archival submissions can cause desk rejection; do not submit the same wor
- Core checks
- NeurIPS-specific risks
- Audit workflow
- Output format
What does the neurips-submission skill do?
Use when auditing a NeurIPS main-track submission for current-cycle CFP, OpenReview, formatting, anonymity, track, contribution-type, checklist, code/data, dual-submission, and LLM/agent policy compliance.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-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.