鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

nature-reviewer

模拟 Nature 风格的同行评审,基于用户提供的文稿内容生成三份相互独立、视角互补的审稿意见及一份交叉综合评述,聚焦原创性、科学重要性、跨学科价值、技术严谨性与非专业读者可读性,严格区分重大关切与次要意见,所有批评均锚定原文证据,不虚构内容或越界代写作者回应。

访问 GitHub
文档Skills.MD
name
nature-reviewer
description
Provide evidence-grounded mock peer review of scientific manuscripts or excerpts, covering significance, validity, and major/minor concerns. Use for 模拟审稿、投稿前自审、审稿人视角评估; not author rebuttal drafting.

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, and readability 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 synthesis unless 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.
  • After all reports are frozen, run references/forensic-consistency-audit.md as a separate editorial pass. Audit arithmetic, metric bounds, aggregation levels, prose-table ordering, duplicate displays, dispersion anomalies, provenance and reproducibility. Never feed audit findings back into reviewer contexts or edit frozen reports after comparison.
  • 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 verifiable evidence_pointer; mark missing locations instead of inventing them.
  • Separate user-visible concerns into Major Concerns and Minor Comments. Mark a Major Concern Blocking Yes only 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-reviewer structure.
  • 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

  1. Identify the input scope and whether the job is a reviewer-style assessment rather than rebuttal drafting.
  2. 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.
  3. Define the reviewer count and emphasis briefs before launching any reviewer.
  4. 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.
  5. 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 of references/domain-specific-review-gates.md inside that same isolated context.
  6. 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.
  7. After all reports are frozen, run the forensic consistency audit in a separate editorial pass using references/forensic-consistency-audit.md. Classify findings as confirmed internal error, aggregation ambiguity, provenance gap, suspected duplication, unresolved input needed, not assessable, or passed. Do not feed audit findings back into reviewer contexts or edit frozen reports after comparison.
  8. Compare the frozen reports 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. Keep reviewer consensus and forensic audit findings separate.
  9. Generate Cross-review synthesis (post-review; not shown to reviewers) with consensus blocking concerns, other major concerns, forensic consistency findings, the minor-revision checklist, and genuine differences in emphasis or judgment.
  10. Run QA for reviewer isolation, severity calibration, blocking calibration, evidence anchoring, groundedness, coverage, role boundaries, non-invention, and forensic consistency. 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:

▼
text
复制代码
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] - **Forensic consistency findings** [confirmed errors, aggregation ambiguities, provenance gaps, suspected duplication, unresolved author input] - **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 Nature as 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.
  • Do not label a numerical anomaly a confirmed error without arithmetic proof or source data.
  • Do not hide confirmed internal contradictions merely because no reviewer identified them.
  • Do not present an audit finding as reviewer consensus unless at least two frozen reports independently raised the same underlying concern.

Related files

FileOpen when
references/source-basis.mdYou need source provenance, local rule summaries, or source-vs-implementation boundaries
references/reviewer-workflow.mdYou need the invocation order, fact-base extraction flow, or synthesis rules
references/review-axes.mdYou need the evaluation axes or reviewer weighting logic
references/technical-concern-taxonomy.mdYou need the internal 12-axis coverage check, concern ledger, or claim/evidence-pointer rules
references/domain-specific-review-gates.mdThe manuscript has clear chemistry, engineering, materials, atmospheric, climate-ecology, hydrology, or remote-sensing evidence chains
references/report-structure.mdYou need the default output contract or section anatomy
references/role-boundaries.mdYou need constraints on reviewer differences and editor-versus-reviewer boundaries
references/qa-checklist.mdYou are finalizing an output and need groundedness / non-invention checks
references/forensic-consistency-audit.mdYou need the mandatory post-review audit of arithmetic, metric bounds, aggregation level, prose-table consistency, provenance, dispersion anomalies, or reproducibility gates
../nature-shared/core/consistency-sweep.mdYou 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.mdYou need the primary local Nature source text

Source hierarchy

Use sources in this order:

  1. references/editorial criteria and processes.md
  2. manuscript facts supplied by the user
  3. conservative local implementation rules documented in references/source-basis.md
  4. 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.

快捷安装

复制到终端去安装 Skill

npxskillsaddhttps://github.com/yuan1z0825/nature-skills--skillnature-reviewer
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
Skills 推荐
debug
debug 是一个系统化定位软件缺陷根因的技能,适用于用户报告 'fix'、'broken'、'error' 等问题或测试意外失败时。它通过可验证的假设、最小复现、因果链分析和回归测试,确保在修复前准确定位根本原因。
retrieving-developer-knowledge
retrieving-developer-knowledge 用于搜索、获取和整合 Google 官方开发者文档,覆盖 Google Cloud、AI/Gemini、Android、Chrome、Web、Flutter、Go、Firebase 等平台,适用于查询 gcloud CLI 命令、API 语法、IAM 权限或架构对比等场景。
diff-intake
diff-intake 读取 PR 或分支差异,生成结构化 YAML 变更摘要,用于下游 analytics instrumentation 技能。适用于用户提交 PR 链接、分支对比或原始 diff 后需理解变更内容、评估分析覆盖或启动埋点流程的场景。
lean-build
以极简方式构建高风险功能,强调架构一致性、范围严格控制与明确终止条件,通过复用现有接口、消除冗余逻辑、剔除非必要抽象与配置,实现端到端可验证的窄口径交付。
ast-grep
提供基于抽象语法树的结构化代码搜索能力,支持跨语言精准匹配代码模式、定位特定语法结构、识别复杂代码特征,适用于需理解代码语义而非简单文本匹配的深度代码分析场景。
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI