From neurips-skills
Positions a NeurIPS submission against current-cycle ML literature, preprints, and neighboring conferences. Outputs a structured related-work gap analysis with technical deltas.
How this skill is triggered — by the user, by Claude, or both
Slash command
/neurips-skills:neurips-related-workThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when novelty or positioning is the main risk. NeurIPS reviewers will often know
Use this skill when novelty or positioning is the main risk. NeurIPS reviewers will often know recent papers from neighboring AI venues and preprint streams; stale comparisons are a serious weakness.
For each close paper, write:
<Prior work> solves <problem> by <mechanism>. It does not address <gap>.
Our paper differs by <technical delta>, which matters because <evidence or theory>.
[Closest prior work] <3-5 papers or categories>
[Missing citation risk] High / Medium / Low
[Technical delta] <one-sentence difference>
[Contemporaneous work handling] <cite/compare/acknowledge>
[Rewrite] <related-work paragraph>
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin neurips-skillsPositions an ICML submission against close ML literature, concurrent submissions, and neighboring-venue papers. Use when novelty or concurrent-submission handling is a risk.
Guides positioning of an AAAI paper's novelty against archival and contemporaneous work, with structured checks for reviewer expectations and dual-submission policy compliance.
Positions an ICLR paper against prior work, concurrent submissions, and benchmark lineages to survive reviewer scrutiny. Use when a reviewer cites a missed paper or disputes novelty.