Paper workflow
Use when deciding which paper-related skill to use or how to sequence manuscript work under `/data/boom/Papers` from project setup through submission and rebuttal.From its SKILL.md
npx -y skills add kenantang/codex-and-claude-skills --skill paper-workflowAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.0 KB, 599 tokens by cl100k_base, as published. Nobody here has run it
Paper Workflow
Overview
Use this skill as the routing map for paper work. It does not replace the specialized skills. It tells you which one to use next.
Default assumption: unless the user explicitly names a conference venue, the manuscript should follow the journal-oriented, Nature-style workflow.
When writing follows experiments or analysis performed across multiple sessions, freeze a compact handoff first: current paper story, supported findings, unresolved decisions, and the figure list that actually carries those findings.
Routing Map
Use:
paper-bootstrapwhen a project is new, messy, or missing a source of truthnature-portfolio-playbookwhen the target isNature,Nature Methods,Nature Biotechnology, or the venue fit among those journals is still unclearscientific-writingwhen drafting or rewriting sections in prosemanuscript-optimizerwhen the paper's claim structure, evidence chain, terminology, or prose need revisionresults-section-revisionwhen the Results section is scientifically stable but the subsection flow, paragraph openings, or argument progression still feel jumpyfigure-plannerwhen the main bottleneck is figure logic, panel roles, or legend synccitation-verifierwhen bibliography hygiene or source verification is the bottlenecksubmission-auditwhen the paper is near submission or resubmission and needs a preflight passrebuttal-responsewhen reviewer comments exist and a response letter plus aligned manuscript edits are neededconference-paper-writingonly when the user explicitly wants a conference paper for venues such as NeurIPS, ICML, ICLR, ACL, AAAI, or COLM
Default Sequence
For most papers under /data/boom/Papers, prefer this order:
paper-bootstrapnature-portfolio-playbookwhen venue fit or article type is uncertain- Refresh
notes/project_truth.md,notes/result_summary.md, andnotes/paper_handoff.mdafter any major experimental or figure update scientific-writingormanuscript-optimizerfigure-plannerresults-section-revisionwhen Results is substantively right but narratively abruptcitation-verifiersubmission-auditrebuttal-responseafter external review
Common Mistakes
- using conference-style writing skills by default for journal manuscripts
- polishing sections before the active manuscript source of truth is clear
- rewriting the manuscript from experiment memory instead of a current
result_summary.mdorpaper_handoff.md - editing figure legends late without rechecking the Results text
- postponing Nature Portfolio article-type or venue-fit decisions until after the paper is mostly rewritten
- treating citation formatting as the same thing as citation verification
- writing a response letter before deciding the underlying manuscript edits
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.