nature-response
Skill14 starsChanged 5 months agoApache-2.0View on GitHub
Draft, audit, or revise point-by-point reviewer response letters for Nature-family manuscript revisions. Use when the user provides reviewer comments, editor decision letters, revision notes, response drafts, or asks how to respond to major/minor revision requests, rebuttal letters, response to reviewers, peer-review reports, 审稿意见回复, 逐点回复, 修回信, 大修回复, 小修回复, or 如何回复 reviewer. Also trigger on general peer-review response needs during academic writing/revision even without the word "Nature", such as replying to reviewers for any journal, writing a rebuttal/response letter, handling revision comments, and Chinese phrasings like 回复审稿人、审稿回复、返修、 修改稿回复、写rebuttal、回应审稿意见、应对审稿.
10 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- AfonsoZhang/auto-research-systemedited, first seen Nov 15, 2026
- denghuipan/nature-portfolio-skillsword for word, first seen Nov 15, 2026
- dragonadam/nature-skillsedited, first seen Oct 25, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- szzjayson25-hub/nature-academic-skillsedited, first seen Sep 12, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
Used with
Projects with it also use nature-downloader, nature-literature-pipeline and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vcis-wangchenxuSkillnature-downloader
Help legally obtain, organize, and archive academic papers, PDFs, BibTeX, supplementary files, code links, and benchmark documents for RL, MARL, LLM, and LLM Agent research. Do not bypass paywalls or access controls.
Also in 4 projects that use this
vcis-wangchenxuSkillnature-literature-pipeline
Build a repeatable literature discovery, scoring, reading, and archiving pipeline for RL, MARL, LLM, and LLM Agent research. Use for daily/weekly paper tracking, topic watchlists, benchmark monitoring, and research-note automation.
Also in 4 projects that use this
Delagong950Skillnature-ref-verifier
Multi-source cross-validation of academic references. Verify authors, title, year, volume, issue, and pages against PubMed, CrossRef, and publisher pages. Detect fabricated citations.
Also in 4 projects that use this
Delagong950Skillnature-experiment-log
Standardized lab notebook with structured YAML-frontmatter experiment logs. Supports Obsidian vault integration, image/voice/text input, and batch/tracking systems.
Also in 3 projects that use this
Yuan1z0825Skillnature-shared
Internal shared-reference support package for installed Nature Skills, including nature-writing, nature-polishing, nature-response, nature-reader, and nature-paper2ppt. Do not invoke it as a standalone user workflow. Load only the specific core or journal-format file requested by another Nature skill.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 1
- denghuipan/nature-portfolio-skills★ 2100% same
Edited · 6
- Yuan1z0825/nature-skills★ 54k29% same
- dragonadam/nature-skills★ 499% same
- AfonsoZhang/auto-research-system★ 127% same
- Luooops/skills★ 129% same
- zh123012/claude-skills★ 166% same
- szzjayson25-hub/nature-academic-skills★ 035% same
Wrote their own version · 3
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- Delagong950/nature-skills★ 4same name
- vcis-wangchenxu/agent_nature-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- nature-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-figureSkill
- nature-paper2pptSkill
- nature-paper-to-patentSkill
- nature-polishingSkill
- nature-readerSkill
- nature-reviewerSkill
- nature-writingSkill
- openclaw-medical-skillsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Do not try to apply the response logic from memory or from this router.
- Distinctive: line 29
Follow these four steps every time the skill is invoked.
- Very specific: line 33
Read manifest.yaml. Then read every file listed under always_load:
- Very specific: line 46
Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting.
- Very specific: line 52
Never invent experiments, citations, line numbers, figure panels, supplementary items, editor instructions, or manuscript changes.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nature Reviewer Response — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (the default stance and red lines, and the response workflow with output format). - A dynamic layer (this file plus
manifest.yaml) that loads the core every time and reaches for the deeper response references only when a step needs them.
Do not try to apply the response logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these four steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. Then read every file listed under always_load:
static/core/stance.md— the editor-facing purpose, the default stance, the red lines, and the source hierarchy that apply to every response job.static/core/workflow.md— accepted inputs, the ten-step workflow, and the output package format.
2. No content axis — identify mode and language inline
Unlike nature-writing or nature-figure, nature-response has no fragment axis. Its variation is identified at runtime, not by loading different content bodies:
- task mode —
draft/audit/revise/triage-only/appeal-like. - decision type — minor revision, major revision, revise-and-resubmit, transfer after review, or unclear.
- user language — if the user writes Chinese, also produce the 中文核对 block.
Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting. Route appeal-like cases separately; do not draft an appeal as the default path.
3. Run the workflow
Follow the ten-step workflow in core/workflow.md: identify mode and decision type, extract editor instructions (IDs E.1) then reviewer comments (R1.1, R2.1), classify each item, build a strategy summary, draft point-by-point responses from the preserved comments, map every claimed change to a manuscript location or an explicit placeholder, flag missing author input, run QA, and return the package with a readiness state.
Never invent experiments, citations, line numbers, figure panels, supplementary items, editor instructions, or manuscript changes. Mark anything the author must supply as AUTHOR_INPUT_NEEDED.
4. Reach for references only when needed
The files under references/ are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest — for example references/comment-taxonomy.md to classify comments, references/action-mapping.md for tracker fields, references/tone-and-stance.md for disagreement wording, references/difficult-cases.md for impossible experiments / conflicting reviewers / appeal-like cases, references/chinese-author-alignment.md for Chinese author notes, and references/qa-checklist.md before finalizing.
Why this split
- The static layer is versioned and reviewable; the core stays small for a normal response.
- The dynamic layer keeps each invocation cheap: the difficult-case, taxonomy, and QA depth load only when a step needs them.
- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
- This structure mirrors
nature-writing,nature-polishing,nature-reader,nature-paper2ppt,nature-figure, andnature-citation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

