nature-reviewer
Skill0 starsChanged 2 months agoMITView on GitHub
Simulate Nature-style or general pre-submission peer review from the referee perspective, not an author rebuttal. Use for reviewer reports, mock peer review, manuscript critique, novelty/significance/technical-soundness assessment, 审稿人视角评估, 模拟审稿, 预审, 投稿前自审, 审稿意见模拟, or 帮我审一下论文. Produce evidence-grounded Major Concerns, Minor Comments, and blocking flags. For multiple reviewers, keep every reviewer mutually blind in a separate context, freeze all reports before comparison, and create any synthesis only afterward as a separate editor/author-facing artifact.
8 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- denghuipan/nature-portfolio-skillsedited, first seen Nov 15, 2026
- dragonadam/nature-skillsedited, first seen Oct 25, 2026
- Luooops/skillsedited, first seen Oct 13, 2026
- yanjumlinnb-boop/nature-skillsedited, first seen Oct 8, 2026
- Yuan1z0825/nature-skillsedited, first seen Aug 31, 2026
- zh123012/claude-skillsedited, first seen Jul 29, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- Yuan1z0825/nature-skills★ 54k84% same
- yanjumlinnb-boop/nature-skills★ 1461% same
- Delagong950/nature-skills★ 419% same
- dragonadam/nature-skills★ 465% same
- denghuipan/nature-portfolio-skills★ 261% same
- Luooops/skills★ 198% same
- zh123012/claude-skills★ 162% 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 repository21 other files it gives its agents.
- journal-style-learnSkill
- nature-academic-searchSkill
- nature-citationSkill
- nature-dataSkill
- nature-downloaderSkill
- nature-experiment-logSkill
- nature-figure-prompt-onlySkill
- nature-figureSkill
- nature-image2pptSkill
- nature-literature-pipelineSkill
- nature-paper2pptSkill
- nature-paper-cardSkill
- nature-paper-to-patentSkill
- nature-polishingSkill
- researchwriteSkill
- nature-readerSkill
- nature-ref-verifierSkill
- nature-responseSkill
- nature-sharedSkill
- nature-statisticsSkill
- nature-writingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
27 rules. 8 are common, 13 are distinctive, and 6 are very specific to this project.
8
Common
Most of the 8 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
When the target is Expert Systems with Applications (ESWA or Expert Syst.
- Very specific: line 32
Use the shared contract for journal authority in place of flagship-Nature publication criteria, and …
- Very specific: line 41
Use this skill to simulate a Nature-style reviewer assessment package from the referee side.
- Distinctive: line 51
Use the 12-axis technical concern taxonomy only as an internal coverage checklist.
- Distinctive: line 54
Run each reviewer in a genuinely separate context, subagent, process, or invocation.
- Distinctive: line 63
Do not impose a concern quota.
- Distinctive: line 65
Keep the critique intellectually sharp but professionally phrased.
- Very specific: line 69
When the manuscript has a clear technical domain, use claim-dependent domain gates as supporting checks, but keep the output inside the …
- Very specific: line 70
Do not claim the editor's final decision or certainty about fit to Nature.
- Common: line 83
If the provided material is partial, perform a bounded review and mark the assessment boundary explicitly.
- Distinctive: line 93
Only after all reports are frozen, compare them in a separate synthesis pass.
- Distinctive: line 95
Run QA for reviewer isolation, severity calibration, blocking calibration, evidence anchoring, groundedness, coverage, role boundaries, and …
- Common: line 160
Do not invent reviewer identities, specialty roles, or selection history.
- Distinctive: line 161
Do not let one reviewer read, cite, anticipate, agree with, or respond to another review.
- Distinctive: line 162
Do not build or distribute a shared concern ledger before individual reports are frozen.
- Distinctive: line 163
Do not rewrite independent reports after comparison merely to reduce duplication or create artificial disagreement.
- Distinctive: line 164
Do not call reports mutually blind when they were generated in a shared context without an explicit limitation notice.
- Distinctive: line 165
Do not use dash punctuation or colons as habitual sentence connectors when clearer punctuation, headings, or sentence boundaries work.
- Common: line 166
Do not invent experiments, validations, controls, citations, figure details, line numbers, or prior-work distinctions not present in the …
- Common: line 167
Do not silently turn reviewer assessment into author rebuttal drafting.
- Common: line 168
Do not present the review as an editorial decision letter.
- Very specific: line 169
Do not state that the manuscript belongs in Nature as a settled fact.
- Common: line 170
Do not omit technical failings when the provided evidence does not establish the authors' case.
- Distinctive: line 171
Do not create Major or Minor concerns merely to fill a quota or make reviewer reports look balanced.
- Distinctive: line 172
Do not downgrade a core evidence, validity, ethics, or integrity problem to Minor because it is easy to describe, and do not upgrade a …
- Common: line 192
Use sources in this order:
- Common: line 199
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 8 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
Additional configured journals
For Applied Soft Computing (ASC), Engineering Applications of Artificial
Intelligence (EAAI), ISA Transactions, Knowledge-Based Systems (KBS),
Measurement, Neurocomputing, or IEEE Transactions on Reliability, use
../nature-shared/journal-formats/index.md to resolve the exact journal.
Preserve this skill’s task workflow and evidence safeguards. Apply only the
selected reference’s relevant scope; do not impose flagship-Nature significance
or import another journal’s numerical, citation, or production defaults.
These seven profiles do not yet establish verified official submission limits;
verify the target’s current official source when such requirements affect work.
ESWA journal context
When the target is Expert Systems with Applications (ESWA or
Expert Syst. Appl., case-insensitive), read
../nature-shared/journal-formats/eswa.md before applying journal-specific defaults.
Use the shared contract for journal authority in place of flagship-Nature
publication criteria, and ../nature-shared/core/eswa-ml-rul-style.md for
applicable ML/RUL assessment lenses. Assess applied-system fit, substantive
contribution and technical evidence without requiring Nature-level broad interest.
Label output criteria as ESWA; keep reviewer isolation, evidence pointers and
Major/Minor rules. The simulated reviewer count is a local choice, not ESWA policy.
Pass the ESWA contract with the same immutable source packet to each reviewer.
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. - Use the 12-axis technical concern taxonomy only as an internal coverage checklist; it supplements but never replaces the five source-grounded axes.
- Return exactly
3 mutually blind reviewer reports + 1 post-review synthesisunless the user explicitly asks for another structure. - Give every reviewer only the same immutable manuscript/source packet, the same journal criteria, and that reviewer's preassigned emphasis. Never provide another review, a shared concern ledger, a draft synthesis, or hints about what another reviewer noticed.
- Run each reviewer in a genuinely separate context, subagent, process, or invocation. If the environment cannot isolate contexts, generate one reviewer report per invocation or explicitly state that mutual blindness cannot be guaranteed; never present shared-context drafting as independent peer review.
- Define emphasis briefs before any report is generated. They are working lenses, not reviewer identities, specialties, institutions, or biographies.
- Freeze each individual report before comparing them. Natural duplication or disagreement is valid evidence of independent review and must not be edited away to manufacture diversity.
- Identify who would be interested in the results and why.
- Identify technical failings that must be addressed before the authors' case is established.
- Give every substantive concern a stable ID, a faithful
claim_pointer, and a verifiableevidence_pointer; mark missing locations instead of inventing them. - Separate user-visible concerns into
Major ConcernsandMinor Comments. Mark a Major ConcernBlocking Yesonly when the current manuscript cannot establish its central case until that concern is resolved; Minor Comments are never blocking. - Do not impose a concern quota. If no grounded concern exists at a level, state that explicitly instead of inventing one.
- Keep the critique intellectually sharp but professionally phrased; severity comes from impact on the manuscript's case, not from hostile wording.
- Avoid em dashes, en dashes, and colons as routine prose punctuation throughout reviewer reports and synthesis. Prefer a new sentence, comma, semicolon, parentheses, or a short heading followed by a new line. Retain ordinary hyphens in standard compound terms and stable IDs such as
R1-M1. Preserve punctuation in source-faithful titles, quotations, formulas, identifiers, URLs, times, and required machine-readable syntax when changing it would be inaccurate. - Distinguish clearly between what is supported, what is weak, and what is not assessable from the provided material.
- When the manuscript has a clear technical domain, use claim-dependent domain gates as supporting checks, but keep the output inside the same 3-reviewer
nature-reviewerstructure. - 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.
- Build one immutable review packet containing only the supplied manuscript, verified source anchors, assessment boundary, and common journal criteria. Do not add analytical conclusions or suspected concerns to this packet.
- Define the reviewer count and emphasis briefs before launching any reviewer.
- Launch each reviewer in an isolated context. Pass only the immutable review packet, that reviewer's emphasis brief, the common report skeleton, and the same grounding rules.
- Inside each isolated review, independently assess readiness and the source-grounded axes, then build that reviewer's own concern ledger using
references/technical-concern-taxonomy.md. If relevant, load only the applicable section ofreferences/domain-specific-review-gates.mdinside that same isolated context. - Finalize and freeze every reviewer report. Do not show a completed or partial report to another reviewer, and do not redistribute concerns to control overlap.
- Only after all reports are frozen, compare them in a separate synthesis pass. Reconcile independently created concerns to shared synthesis keys, and label consensus only when at least two reports independently raise the same underlying concern.
- Generate
Cross-review synthesis (post-review; not shown to reviewers)with consensus blocking concerns, other major concerns, the minor-revision checklist, and genuine differences in emphasis or judgment. - Run QA for reviewer isolation, severity calibration, blocking calibration, evidence anchoring, groundedness, coverage, role boundaries, and non-invention. Overlap is measured only after freezing and must never trigger retroactive rewriting of individual reports.
Output format
Unless the user asks for another format, return:
Review setup
- **Input scope** [value]
- **Assessment boundary** [value]
- **Shared manuscript claim summary** [value]
- **Visible evidence base** [value]
- **Missing materials affecting confidence** [value]
Reviewer 1
- **Overall assessment** [text]
- **Who would be interested in the results, and why** [text]
- **Major strengths** [text]
- **Major Concerns** [items]
- **Minor Comments** [items]
- **Technical failings that need to be addressed before the case is established** [IDs or summary]
- **Assessment against Nature-style criteria** [text]
- **Recommendation posture** [text]
For each Major Concern
- **Concern ID** R1-M1
- **Severity** Major
- **Blocking** Yes / No
- **Axis** [value]
- **Claim pointer** [value]
- **Evidence pointer** [value]
- **Concern** [text]
- **Why it matters** [text]
- **Resolution test** [text]
For each Minor Comment
- **Concern ID** R1-m1
- **Severity** Minor
- **Axis** [value]
- **Affected element** [value]
- **Evidence pointer** [value]
- **Issue** [text]
- **Required correction** [text]
Reviewer 2
[Same structure]
Reviewer 3
[Same structure]
Cross-review synthesis (post-review; not shown to reviewers)
- **Consensus strengths** [text]
- **Consensus blocking concerns** [items]
- **Other consensus major concerns** [items]
- **Where emphasis differs across reviewers** [text]
- **Minor revision checklist** [items]
- **Broad-interest / significance readout** [text]
- **Most important issues to resolve before a strong Nature-style case is established** [items]
Risk / unsupported claims
- [specific unsupported or not-assessable items]Red lines
- Do not invent reviewer identities, specialty roles, or selection history.
- Do not let one reviewer read, cite, anticipate, agree with, or respond to another review.
- Do not build or distribute a shared concern ledger before individual reports are frozen.
- Do not rewrite independent reports after comparison merely to reduce duplication or create artificial disagreement.
- Do not call reports mutually blind when they were generated in a shared context without an explicit limitation notice.
- Do not use dash punctuation or colons as habitual sentence connectors when clearer punctuation, headings, or sentence boundaries work.
- 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.
- Do not create Major or Minor concerns merely to fill a quota or make reviewer reports look balanced.
- Do not downgrade a core evidence, validity, ethics, or integrity problem to Minor because it is easy to describe, and do not upgrade a local presentation issue merely to sound severe.
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/technical-concern-taxonomy.md | You need the internal 12-axis coverage check, concern ledger, or claim/evidence-pointer rules |
| references/domain-specific-review-gates.md | The manuscript has clear chemistry, engineering, materials, atmospheric, climate-ecology, hydrology, or remote-sensing evidence chains |
| 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 |
| ../nature-shared/core/consistency-sweep.md | You are checking the manuscript against itself: headline counts that do not reconcile with the Methods, one metric at two precisions, a superlative contradicted by the paper's own table, overlapping error bars presented as an advantage, or internal summaries that disagree |
| 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 - domain-specific supporting gates in
references/domain-specific-review-gates.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.

