nature-reviewer
Skill14 starsChanged 5 months agoApache-2.0View on GitHub
Simulate a Nature-style reviewer assessment from the referee perspective rather than an author rebuttal. Use when the user wants a pre-submission review, reviewer report, peer-review style critique, novelty/significance/technical soundness assessment, reviewer-style manuscript evaluation, 审稿人视角评估, 预审稿意见, or Nature reviewer report. Return 3 reviewer reports plus a cross-review synthesis, grounded only in the local Nature reviewer source basis. Also trigger on general pre-submission review requests during academic writing even without the word "Nature", such as getting a mock peer review for any journal, critiquing a draft as a reviewer would, assessing novelty/rigor before submission, and Chinese phrasings like 审稿人视角、模拟审稿、预审、帮我审一下论文、投稿前自审、审稿意见模拟、找论文问题.
8 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- 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
- zh123012/claude-skillsedited, first seen Jul 29, 2026
Used with
Projects with it also use nature-downloader, nature-experiment-log 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 5 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 5 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
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 versions8 projects use a version of this.
Word for word · 1
- denghuipan/nature-portfolio-skills★ 2100% same
Edited · 6
- Yuan1z0825/nature-skills★ 54k29% same
- Delagong950/nature-skills★ 428% same
- dragonadam/nature-skills★ 499% same
- Luooops/skills★ 132% same
- zh123012/claude-skills★ 173% same
- szzjayson25-hub/nature-academic-skills★ 028% same
Wrote their own version · 1
- 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-responseSkill
- nature-writingSkill
- openclaw-medical-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 8 are common, 2 are distinctive, and 3 are very specific to this project.
8
Common
Most of the 7 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
- Very specific: line 20
Use this skill to simulate a Nature-style reviewer assessment package from the referee side.
- Very specific: line 35
Do not claim the editor's final decision or certainty about fit to Nature.
- Common: line 48
If the provided material is partial, perform a bounded review and mark the assessment boundary explicitly.
- Distinctive: line 54
Check readiness and label missing evidence or missing sections instead of inventing them.
- Distinctive: line 58
Run QA for groundedness, coverage, role boundaries, and non-invention.
- Common: line 100
Do not invent reviewer identities, specialty roles, or selection history.
- Common: line 101
Do not invent experiments, validations, controls, citations, figure details, line numbers, or prior-work distinctions not present in the …
- Common: line 102
Do not silently turn reviewer assessment into author rebuttal drafting.
- Common: line 103
Do not present the review as an editorial decision letter.
- Very specific: line 104
Do not state that the manuscript belongs in Nature as a settled fact.
- Common: line 105
Do not omit technical failings when the provided evidence does not establish the authors' case.
- Common: line 121
Use sources in this order:
- Common: line 127
If a user asks for policy-level certainty beyond this local source, state the limit instead of improvising broader journal policy.
“Common” is measured: kept by at least 6 in 10 of the 7 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 Assessment Skill
Use this skill to simulate a Nature-style reviewer assessment package from the referee
side.
This skill is for reviewer-style manuscript evaluation, not for drafting the authors'
response. If the user wants rebuttal writing, route to nature-response.
Default stance
- Ground the review only in the local source basis plus manuscript facts supplied by the user.
- Evaluate the manuscript against source-grounded axes:
originality,scientific importance,interdisciplinary readership,technical soundness, andreadability for nonspecialists. - Return exactly
3 reviewer reports + 1 cross-review synthesisunless the user explicitly asks for another structure. - The three reviewers may differ only in
emphasis; do not invent reviewer identities, specialties, institutions, or biographies. - Identify who would be interested in the results and why.
- Identify technical failings that must be addressed before the authors' case is established.
- Distinguish clearly between what is supported, what is weak, and what is not assessable from the provided material.
- Do not claim the editor's final decision or certainty about fit to
Nature.
Accepted inputs
The skill may receive:
- full manuscript draft
- abstract, summary paragraph, or cover-summary style text
- introduction, results, discussion, or methods excerpts
- figure legends, selected figures, or result notes
- author notes in Chinese or English describing the claimed contribution
- pre-submission positioning notes
If the provided material is partial, perform a bounded review and mark the assessment boundary explicitly.
Workflow
- Identify the input scope and whether the job is a reviewer-style assessment rather than rebuttal drafting.
- Extract a shared manuscript fact base: main claim, visible evidence, claimed significance, likely readership, and visible limitations.
- Check readiness and label missing evidence or missing sections instead of inventing them.
- Assess the manuscript using the source-grounded axes.
- Generate
Reviewer 1,Reviewer 2, andReviewer 3using shared facts but different emphasis. - Generate a
Cross-review synthesisthat captures consensus and weighting differences. - Run QA for groundedness, coverage, role boundaries, and non-invention.
Output format
Unless the user asks for another format, return:
Review setup
- Input scope:
- Assessment boundary:
- Shared manuscript claim summary:
- Visible evidence base:
- Missing materials affecting confidence:
Reviewer 1
- Overall assessment:
- Who would be interested in the results, and why:
- Major strengths:
- Major concerns:
- Technical failings that need to be addressed before the case is established:
- Assessment against Nature-style criteria:
- Recommendation posture:
Reviewer 2
[Same structure]
Reviewer 3
[Same structure]
Cross-review synthesis
- Consensus strengths:
- Consensus technical risks:
- Where emphasis differs across reviewers:
- Broad-interest / significance readout:
- Most important issues to resolve before a strong Nature-style case is established:
Risk / unsupported claims
- [specific unsupported or not-assessable items]Red lines
- Do not invent reviewer identities, specialty roles, or selection history.
- Do not invent experiments, validations, controls, citations, figure details, line numbers, or prior-work distinctions not present in the input.
- Do not silently turn reviewer assessment into author rebuttal drafting.
- Do not present the review as an editorial decision letter.
- Do not state that the manuscript belongs in
Natureas a settled fact. - Do not omit technical failings when the provided evidence does not establish the authors' case.
Related files
| File | Open when |
| references/source-basis.md | You need source provenance, local rule summaries, or source-vs-implementation boundaries |
| references/reviewer-workflow.md | You need the invocation order, fact-base extraction flow, or synthesis rules |
| references/review-axes.md | You need the evaluation axes or reviewer weighting logic |
| references/report-structure.md | You need the default output contract or section anatomy |
| references/role-boundaries.md | You need constraints on reviewer differences and editor-versus-reviewer boundaries |
| references/qa-checklist.md | You are finalizing an output and need groundedness / non-invention checks |
| [references/editorial criteria and processes.md](references/editorial criteria and processes.md) | You need the primary local Nature source text |
Source hierarchy
Use sources in this order:
references/editorial criteria and processes.md- manuscript facts supplied by the user
- conservative local implementation rules documented in
references/source-basis.md
If a user asks for policy-level certainty beyond this local source, state the limit instead of improvising broader journal policy.
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.

