Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing, the mandatory Paper Checklist, OpenReview submission…
Install Neurips Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .claude/skills/neurips-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .claude/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .agents/skills/neurips-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .agents/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .cursor/skills/neurips-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .cursor/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path NeurIPS-Skills/skills/neurips-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .gemini/skills/neurips-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .gemini/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .github/skills/neurips-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .github/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills neurips-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/NeurIPS-Skills/skills/neurips-workflow .opencode/skills/neurips-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "neurips-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NeurIPS-Skills/skills/neurips-workflow into .opencode/skills/neurips-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neurips-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
neurips-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 474 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing, the mandatory Paper Checklist, OpenReview submission…
- Works in 7 steps: Topic and track fit: use… → Paper shaping: use… → Artifact and supplement planning: use… → …
- Planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing
- SKILL.md covers Stage map, Operating principles, Deadline ladder to schedule… and Track-fork early warning, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Neurips Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing
- The mandatory Paper Checklist
- OpenReview submission
- Double-blind review
Example prompts
- “/neurips-workflow”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Topic and track fit: use neurips-topic-selection.
- Paper shaping: use neurips-writing-style, neurips-related-work, and neurips-experiments.
- Artifact and supplement planning: use neurips-artifact-evaluation, neurips-reproducibility,
- Final pre-submission audit: use neurips-submission.
- Review diagnosis: use neurips-review-process.
- Rebuttal and discussion: use neurips-author-response.
- Acceptance and public release: use neurips-camera-ready.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Neurips Workflow loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 474 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 474 words, ~1,106 tokens.
Download SKILL.mdSave it as
.claude/skills/neurips-workflow/SKILL.md (or your agent's skills folder).- name
- neurips-workflow
- description
- 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.
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
- Topic and track fit: use
neurips-topic-selection. - Paper shaping: use
neurips-writing-style,neurips-related-work, andneurips-experiments. - Artifact and supplement planning: use
neurips-artifact-evaluation,neurips-reproducibility, andneurips-supplementary. - Final pre-submission audit: use
neurips-submission. - Review diagnosis: use
neurips-review-process. - Rebuttal and discussion: use
neurips-author-response. - Acceptance and public release: use
neurips-camera-ready.
Operating principles
- Start official-source checks early; NeurIPS annual policies change.
- Keep track choice explicit. A main-track method paper, E&D paper, position paper, and MLRC paper are not interchangeable.
- Write the checklist in parallel with the paper rather than at the end.
- Maintain one evidence table mapping every central claim to proof, experiment, data, artifact, and limitation.
- Keep an anonymous review artifact and a de-anonymized public release artifact as separate states.
Show full SKILL.md (247 more words)Show less
Deadline ladder to schedule backward from
NeurIPS spreads its gates across the year, so plan backward from the abstract deadline, not the full-paper deadline. The exact dates move every cycle; reopen the current CFP and Main Track Handbook for the live calendar.
| Gate | What locks here | Skill to finish before it |
|---|---|---|
| OpenReview profiles | every author needs an active, complete profile | neurips-submission |
| Abstract deadline | title, abstract, and author list freeze (order may change after) | neurips-topic-selection, neurips-related-work |
| Full-paper deadline | PDF, checklist, and code/data ZIP submitted together | neurips-experiments, neurips-supplementary |
| Reviews released | nothing changes; you read and triage | neurips-review-process |
| Author-response window | rebuttal through OpenReview, no new paper version | neurips-author-response |
| Decision | accept (spotlight/poster) or reject | neurips-camera-ready if accepted |
| Camera-ready | de-anonymize, finalize checklist, public artifacts | neurips-camera-ready, neurips-artifact-evaluation |
Track-fork early warning
Decide the track before drafting, because the Datasets & Benchmarks track, Position Papers track, and
MLRC/TMLR reproducibility route each have a distinct call, checklist emphasis, and review rubric. A
dataset paper forced into the main track, or a reproduction study that belongs in MLRC, wastes a full
cycle. If neurips-topic-selection flags a fork, resolve it before any other stage.
Worked vignette: where this router intervenes
A team has strong benchmark wins for a new retrieval method but no mechanism analysis and a thin
limitations paragraph. The router routes them to neurips-experiments (add ablations and error
analysis) and neurips-writing-style (calibrate the claim and the limitations) before
neurips-submission, rather than letting a leaderboard-only paper reach OpenReview where reviewers
predictably ask for the missing mechanism.
Output format
[Current stage] topic / drafting / pre-submission / review / rebuttal / camera-ready / reroute
[Next skill] <one NeurIPS skill>
[Official source to open] <CFP/handbook/template/OpenReview/checklist>
[Blocking gap] <policy/evidence/artifact/writing>
[Next action] <concrete task>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in NeurIPS-Skills/skills/neurips-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Neurips Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Neurips Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Neurips Workflow
What does Neurips Workflow do?
A skill your agent uses when planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing, the mandatory Paper Checklist, OpenReview submission…. Neurips Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Neurips Workflow?
Neurips Workflow fits situations like: planning and sequencing a full NeurIPS manuscript workflow from topic and track selection through writing; the mandatory Paper Checklist; openReview submission; double-blind review.
How do I install Neurips Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a claude-code`. Or copy the skill folder (NeurIPS-Skills/skills/neurips-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/neurips-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Neurips Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a codex`. Or copy the skill folder (NeurIPS-Skills/skills/neurips-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/neurips-workflow in your project. Codex loads it when a task matches its description.
Can I use Neurips Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill neurips-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neurips-workflow, .gemini/skills/neurips-workflow, .github/skills/neurips-workflow and .opencode/skills/neurips-workflow in your project.
What does Neurips Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Neurips Workflow is instructions for the agent only.
Does Neurips Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Neurips Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Neurips Workflow use?
Neurips Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Neurips Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Neurips Workflow?
Skills that share tags, products or a category with Neurips Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Neurips Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.