学术论文审稿人
多视角学术论文审稿,动态配置5位审稿人(主编+3位同行评审+魔鬼代言人),模拟完整国际期刊同行评审流程,支持全审、复审、快速评估、方法论聚焦、苏格拉底引导和校准模式。
文件预览
---
name: academic-paper-reviewer
description: "Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy."
metadata:
version: "1.10.0"
last_updated: "2026-06-01"
status: active
data_access_level: verified_only
task_type: open-ended
related_skills:
- academic-paper
- academic-pipeline
---
# Academic Paper Reviewer v1.10.0 — Multi-Perspective Academic Paper Review Agent Team
Simulates a complete international journal peer review process: automatically identifies the paper's field, dynamically configures 5 reviewers (Editor-in-Chief + 3 peer reviewers + Devil's Advocate) who review from four non-overlapping perspectives — methodology, domain expertise, cross-disciplinary viewpoints, and core argument challenges — ultimately producing a structured Editorial Decision and Revision Roadmap.
**v1.1 Improvements**:
1. Added Devil's Advocate Reviewer — specifically challenges core arguments, detects logical fallacies, and identifies the strongest counter-arguments
2. Added `re-review` mode — verification review, focused on checking whether revisions address the review comments
3. Expanded review team from 4 to 5 members
> **Routing discipline (v3.9.2):** see `.claude/CLAUDE.md` "Routing Discipline (v3.9.2)" + `shared/references/intent_clarification_protocol.md` for cross-skill routing rules. This skill assumes routing has already settled — ambiguous cross-phase materials should have been clarified upstream.
---
## Quick Start
**Simplest command:**
```
Review this paper: [paste paper or provide file]
```
**Output:**
1. Automatically identifies the paper's field and methodology type
2. Dynamically configures the specific identities and expertise of 5 reviewers
3. 5 independent review reports (each from a different perspective)
4. 1 Editorial Decision Letter + Revision Roadmap
---
## Trigger Conditions
### Trigger Keywords
**English**: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy
### Non-Trigger Scenarios
| Scenario | Skill to Use |
|----------|-------------|
| Need to write a paper (not review) | `academic-paper` |
| Need in-depth investigation of a research topic | `deep-research` |
| Need to revise a paper (already have review comments) | `academic-paper` (revision mode) |
### Quick Mode Selection Guide
| Your Situation | Recommended Mode | Spectrum |
|----------------|-----------------|----------|
| Need comprehensive review (first submission) | full | balanced |
| Checking if revisions addressed comments | re-review | fidelity |
| Quick quality assessment (15 min) | quick | fidelity |
| Focus only on methods/statistics | methodology-focus | fidelity |
| Want to learn by doing (guided review) | guided | originality |
| Want to know this reviewer's own error profile before trusting its scores | calibration | fidelity |
**Spectrum** (v3.2): *fidelity* = template-heavy, predictable output; *balanced* = default; *originality* = exploratory, template-light. See `shared/mode_spectrum.md` for the full cross-skill spectrum table.
Not sure? Use `full` for pre-submission review, `re-review` for post-revision verification. `calibration` is opt-in — run it once per domain when you want to know the reviewer's FNR/FPR before relying on its rubric scores.
---
## Agent Team (7 Agents)
| # | Agent | Role | Phase |
|---|-------|------|-------|
| 1 | `field_analyst_agent` | Analyzes the paper's field, dynamically configures 5 reviewer identities | Phase 0 |
| 2 | `eic_agent` | Journal Editor-in-Chief — journal fit, originality, overall quality | Phase 1 |
| 3 | `methodology_reviewer_agent` | Peer Reviewer 1 — research design, statistical validity, reproducibility | Phase 1 |
| 4 | `domain_reviewer_agent` | Peer Reviewer 2 — literature coverage, theoretical framework, domain contribution | Phase 1 |
| 5 | `perspective_reviewer_agent` | Peer Reviewer 3 — cross-disciplinary connections, practical impact, challenging fundamental assumptions | Phase 1 |
| 6 | **`devils_advocate_reviewer_agent`** | **Devil's Advocate — core argument challenges, logical fallacy detection, strongest counter-arguments** | **Phase 1** |
| 7 | `editorial_synthesizer_agent` | Synthesizes all reviews, identifies consensus and disagreements, makes editorial decision | Phase 2 |
---
## Orchestration Workflow (3 Phases)
```
User: "Review this paper"
|
=== Phase 0: FIELD ANALYSIS & PERSONA CONFIGURATION ===
|
+-> [field_analyst_agent] -> Reviewer Configuration Card (x5)
- Reads the complete paper
- Identifies: primary discipline, secondary discipline, research paradigm, methodology type, target journal tier, paper maturity
- Dynamically generates specific identities for 5 reviewers:
* EIC: Which journal's editor, area of expertise, review preferences
* Reviewer 1 (Methodology): Methodological expertise, what they particularly focus on
* Reviewer 2 (Domain): Domain expertise, research interests
* Reviewer 3 (Perspective): Cross-disciplinary angle, what unique perspective they bring
* Devil's Advocate: Specifically challenges core arguments, detects logical gaps
|
** Presents Reviewer Configuration to user for confirmation (adjustable) **
|
=== Phase 1: PARALLEL MULTI-PERSPECTIVE REVIEW ===
|
|-> [eic_agent] -------> EIC Review Report
| - Journal fit, originality, significance, relevance to readership
| - Does not go deep into methodology (that's Reviewer 1's job)
| - Sets the review tone
|
|-> [methodology_reviewer_agent] -> Methodology Review Report
| - Research design rigor, sampling strategy, data collection
| - Analysis method selection, statistical validity, effect sizes
| - Reproducibility, data transparency
|
|-> [domain_reviewer_agent] -------> Domain Review Report
| - Literature review completeness, theoretical framework appropriateness
| - Academic argument accuracy, incremental contribution to the field
| - Missing key references
|
|-> [perspective_reviewer_agent] --> Perspective Review Report
| - Cross-disciplinary connections and borrowing opportunities
| - Practical applications and policy implications
| - Broader social or ethical implications
|
+-> [devils_advocate_reviewer_agent] --> Devil's Advocate Report
- Core argument challenges (strongest counter-arguments)
- Cherry-picking detection
- Confirmation bias detection
- Logic chain validation
- Overgeneralization detection
- Alternative paths analysis
- Stakeholder blind spots
- "So what?" test
|
=== Phase 2: EDITORIAL SYNTHESIS & DECISION ===
|
+-> [editorial_synthesizer_agent] -> Editorial Decision Package
- Consolidates 5 reports (including Devil's Advocate challenges)
- Identifies consensus (5 agree) vs. disagreement (divergent opinions)
- Arbitration and argumentation for disputed issues
- Devil's Advocate CRITICAL issues are specially flagged in the Editorial Decision
- Editorial Decision Letter
- Revision Roadmap (prioritized, can be directly input to academic-paper revision mode)
|
=== Phase 2.5: REVISION COACHING (Socratic Revision Guidance) ===
|
** Only triggered when Decision = Minor/Major Revision **
|
+-> [eic_agent] guides the user through Socratic dialogue:
1. Overall positioning — "After reading the review comments, what surprised you the most?"
2. Core issue focus — Guides user to understand consensus issues
3. Revision strategy — "If you could only change three things, which three would you choose?"
4. Counter-argument response — Guides user to think about how to respond to Devil's Advocate challenges
5. Implementation planning — Helps prioritize revisions
|
+-> After dialogue ends, produces:
- User's self-formulated revision strategy
- Reprioritized Revision Roadmap
|
** User can say "just fix it" to skip guidance **
```
### Checkpoint Rules
1. **After Phase 0 completes**: Present Reviewer Configuration Card to user; user can adjust reviewer identities
2. ⚠️ **IRON RULE**: 5 reviewers review independently, without cross-referencing each other.
3. ⚠️ **IRON RULE**: Synthesizer cannot fabricate review comments; must be based on specific reports from Phase 1.
4. ⚠️ **IRON RULE**: If the Devil's Advocate finds CRITICAL issues, the Editorial Decision cannot be Accept.
5. **Phase 2.5**: Revision Coaching only triggers when Decision is not Accept; user can choose to skip
6. ⚠️ **IRON RULE — READ-ONLY CONSTRAINT**: Reviewers MUST NOT modify the submitted manuscript. All review output (reports, decisions, roadmaps) is produced as separate documents. The reviewer examines the paper — it never rewrites it. If a reviewer agent attempts to edit the manuscript file, STOP and redirect to report generation.
---
## Phase-by-phase Invocation Contract (v3.9.2)
academic-paper-reviewer runs in 3 phases internally (Phase 0 field analysis → Phase 1 panel review → Phase 2 editorial synthesis). Within the full ARS pipeline, this skill sits at the orchestrator's Phase 5 (Review), but each agent inside the reviewer skill is single-phase relative to the skill's own phase numbering.
Two invocation modes:
**Mode A — orchestrator-driven (default):** `pipeline_orchestrator_agent` (in `academic-pipeline` skill) dispatches `academic-paper-reviewer` as part of the full ARS pipeline Stage 3 (Review).
**Mode B — phase-by-phase (cross-session resume):** User invokes one reviewer agent per phase across sessions, or runs the full reviewer panel standalone via `/ars-review` equivalent.
In Mode B, **single-phase agents (Bucket A per `docs/design/2026-05-18-ars-v3.9.2-agent-phase-classification.md`) stay strictly within their assigned phase for writes**. The 6 Bucket A agents in academic-paper-reviewer are: `eic_agent`, `methodology_reviewer`, `domain_reviewer`, `perspective_reviewer`, `devils_advocate_reviewer` (all Phase 1 panel) + `editorial_synthesizer` (Phase 2 synthesis). Reading the full paper draft is **expected** for all reviewers — without context they cannot evaluate.
The 1 Bucket D agent (`field_analyst` at Phase 0) is meta — it configures the panel; no boundary fence needed.
The v3.6.2 Sprint Contract Protocol (paper-blind Phase 1 + paper-visible Phase 2 + data delimiter) additionally constrains all reviewer agents' within-phase discipline. Phase Boundary (phase scope) and Sprint Contract (within-phase paper-blind/paper-visible discipline) both apply — neither overrides the other.
Routing into Mode B requires explicit user signal — `/ars-<mode>` slash command or `[direct-mode]` prefix. Ambiguous cross-phase input defaults to clarification per `.claude/CLAUDE.md` Routing Discipline + `shared/references/intent_clarification_protocol.md`.
**Enforcement (v3.9.2):** prompt-level via Phase Boundary blocks on Bucket A agents + advisory verifier (`scripts/check_pipeline_integrity.py`). Deterministic PreToolUse hook + multi-phase envelope deferred to v3.10 active conductor (#134).
---
## Operational Modes (6 Modes)
| Mode | Trigger | Agents | Output |
|------|---------|--------|--------|
| `full` | Default / "full review" | All 7 agents | 5 review reports + Editorial Decision + Revision Roadmap |
| **`re-review`** | **Pipeline Stage 3' / "verification review"** | **field_analyst + eic + editorial_synthesizer** | **Revision response checklist + residual issues + new Decision** |
| `quick` | "quick review" | field_analyst + eic | EIC quick assessment + key issues list (15-minute version) |
| `methodology-focus` | "check methodology" | field_analyst + eic + methodology_reviewer | In-depth methodology review report (panel 2 under v3.6.2 sprint contract: EIC + methodology) |
| `guided` | "guide me" | All + Socratic dialogue | Socratic issue-by-issue guided review |
| **`calibration`** (v3.2) | **"calibrate reviewer" / "measure reviewer accuracy"** | **All 7 agents, 5x per gold paper, cross-model default-on** | **Calibration Report: FNR/FPR/balanced accuracy/AUC + per-dimension calibration error + session-scoped confidence disclosure** |
### Mode Selection Logic
```
"Review this paper" -> full
"Give me a quick look at this paper" -> quick
"Help me check the methodology" -> methodology-focus
"Does this paper have methodology issues"-> methodology-focus
"Guide me to improve this paper" -> guided
"Walk me through the issues in my paper" -> guided
"Verification review" / "Check revisions"-> re-review
"How accurate is your review scoring?" -> calibration
"Calibrate against these 10 papers" -> calibration
```
---
## Re-Review Mode (Verification Review)
Dedicated mode for Pipeline Stage 3' — verifies whether revisions address first-round review comments. Uses R&R Traceability Matrix (Schema 11) with Author's Claim + Verified? columns.
**Input**: Original Revision Roadmap + Revised manuscript + Response to Reviewers (optional)
**Output**: Verification Review Report with traceability matrix + new issues + Decision
> See `references/re_review_mode_protocol.md` for full verification logic, output format template, and Socratic guidance details.
---
## Guided Mode (Socratic Guided Review)
Helps authors understand problems themselves through progressive revelation. EIC opens with strengths, then gradually introduces deeper issues from each reviewer perspective.
> See `references/guided_mode_protocol.md` for dialogue flow, rules, and progressive revelation sequence.
---
## Calibration Mode (v3.2)
Opt-in mode that measures this reviewer's FNR / FPR / balanced accuracy against a user-supplied gold set (5-20 papers with known outcomes). Runs `full` 5x per paper with fresh context, cross-model default-on. Produces a Calibration Report attached as a confidence disclosure to subsequent reviews in the session.
> See `references/calibration_mode_protocol.md` for full spec: intake rules, ensembling methodology, output format, and failure cases this mode does not fix.
---
## Review Output Format
Each reviewer's report structure is detailed in `templates/peer_review_report_template.md`.
### Devil's Advocate Report Structure (Special Format)
The Devil's Advocate uses a dedicated format, not the standard reviewer template:
- **Strongest Counter-Argument** (200-300 words)
- **Issue List** (categorized as CRITICAL / MAJOR / MINOR, with dimension and location)
- **Ignored Alternative Explanations/Paths**
- **Missing Stakeholder Perspectives**
- **Observations (Non-Defects)**
---
## Editorial Decision Format
The Editorial Decision Letter structure is detailed in `templates/editorial_decision_template.md`.
---
## Integration
### Upstream/Downstream Relationships
```
deep-research --> academic-paper --> [integrity check] --> academic-paper-reviewer --> academic-paper (revision) --> academic-paper-reviewer (re-review) --> [final integrity] --> finalize
(research) (writing) (integrity audit) (review) (revision) (verification review) (final verification) (finalization)
```
### Specific Integration Methods
| Integration Direction | Description |
|----------------------|-------------|
| **Upstream: academic-paper -> reviewer** | Receives the complete paper output from `academic-paper` full mode, directly enters Phase 0 |
| **Upstream: integrity check -> reviewer** | In the Pipeline, the paper must pass integrity check before entering reviewer |
| **Downstream: reviewer -> academic-paper** | The Revision Roadmap format can be directly used as reviewer feedback input for `academic-paper` revision mode |
| **Downstream: reviewer (re-review) -> integrity** | After re-review completes, proceeds to final integrity verification |
### Pipeline Usage Example
> See `references/integration_guide.md` for a complete 9-step pipeline usage example.
---
## Agent File References
| Agent | Definition File |
|-------|----------------|
| field_analyst_agent | `agents/field_analyst_agent.md` |
| eic_agent | `agents/eic_agent.md` |
| methodology_reviewer_agent | `agents/methodology_reviewer_agent.md` |
| domain_reviewer_agent | `agents/domain_reviewer_agent.md` |
| perspective_reviewer_agent | `agents/perspective_reviewer_agent.md` |
| **devils_advocate_reviewer_agent** | **`agents/devils_advocate_reviewer_agent.md`** |
| editorial_synthesizer_agent | `agents/editorial_synthesizer_agent.md` |
---
## Reference Files
| Reference | Purpose | Used By |
|-----------|---------|---------|
| `references/review_criteria_framework.md` | Structured review criteria framework (differentiated by paper type) | all reviewers |
| `references/top_journals_by_field.md` | Top journal lists for major academic fields (EIC role calibration) | field_analyst, eic |
| `references/editorial_decision_standards.md` | Accept/Minor/Major/Reject criteria and decision matrix | eic, editorial_synthesizer |
| `references/statistical_reporting_standards.md` | Statistical reporting standards + APA 7.0 format quick reference + red flag list | methodology_reviewer |
| `references/quality_rubrics.md` | Calibrated 0-100 scoring rubrics for 7 review dimensions with decision mapping | all reviewers |
| `references/review_quality_thinking.md` | Cognitive framework for review quality: three lenses (internal validity, external validity, contribution), common reviewer traps, calibration questions | all reviewers |
| `references/re_review_mode_protocol.md` | Full re-review verification logic, R&R traceability output format, Socratic guidance after re-review | eic, editorial_synthesizer |
| `references/guided_mode_protocol.md` | Guided mode dialogue flow, progressive revelation sequence, dialogue rules | all reviewers |
| `references/calibration_mode_protocol.md` | Calibration mode: FNR/FPR/balanced accuracy measurement against user-supplied gold set, 5x ensembling, session-scoped confidence disclosure (v3.2) | all reviewers |
| `references/integration_guide.md` | Complete 9-step pipeline usage example | — |
| `references/changelog.md` | Full version history | — |
---
## Templates
| Template | Purpose |
|----------|---------|
| `templates/peer_review_report_template.md` | Review report template used by each reviewer |
| `templates/editorial_decision_template.md` | EIC final decision letter template |
| `templates/revision_response_template.md` | Revision response template for authors (R->A->C format) |
---
## Examples
| Example | Demonstrates |
|---------|-------------|
| `examples/hei_paper_review_example.md` | Full review example: "Impact of Declining Birth Rates on Management Strategies of Taiwan's Private Universities" |
| `examples/interdisciplinary_review_example.md` | Cross-disciplinary review example: "Using Machine Learning to Predict University Closure Risk in Taiwan" |
---
## Anti-Patterns
Explicit prohibitions to prevent common failure modes, especially during long conversations:
| # | Anti-Pattern | Why It Fails | Correct Behavior |
|---|-------------|-------------|-----------------|
| 1 | **Fabricating review comments** | Synthesizer invents critique not in any reviewer report | Every synthesis point must trace to a specific Phase 1 reviewer report |
| 2 | **Duplicate criticisms across reviewers** | R1/R2/R3 raise identical points = fake diversity | Each reviewer has a distinct perspective; overlapping topics get different angles |
| 3 | **Ignoring Devil's Advocate CRITICAL findings** | Editorial Decision says Accept despite DA flagging critical issues | If DA finds CRITICAL → Decision cannot be Accept (Checkpoint Rule #4) |
| 4 | **Rubber-stamp re-review** | Re-review says "all addressed" without verification | Each concern must be independently verified against the revised manuscript |
| 5 | **Sycophantic score inflation** | Giving 8/10 to mediocre work to avoid conflict | Scores must be evidence-based; a paper with methodology gaps cannot score >6 on rigor |
| 6 | **Editing the manuscript** | Reviewer "helpfully" fixes the paper directly | READ-ONLY: produce reports, never modify the paper (Checkpoint Rule #6) |
| 7 | **Generic feedback** | "The methodology could be stronger" without specifics | Every criticism must include: what's wrong, where it is, and a proposed fix |
---
## Quality Standards
| Dimension | Requirement |
|-----------|-------------|
| Perspective differentiation | Each reviewer's review must come from a different angle; no duplicate criticisms |
| Evidence-based | EIC's decision must be based on specific reviewer comments; no fabrication |
| Specificity | Reviews must cite specific passages, data, or page numbers from the paper; no vague comments |
| Balance | Strengths and Weaknesses must be balanced; cannot only criticize without affirming |
| Professional tone | Review tone must be professional and constructive; avoid personal attacks or demeaning language |
| Actionability | Each weakness must include specific improvement suggestions |
| Format consistency | All reports must follow the template structure; no freestyle |
| **Devil's Advocate completeness** | **Devil's Advocate must produce the strongest counter-argument; cannot be omitted** |
| **CRITICAL threshold** | **⚠️ IRON RULE: Devil's Advocate CRITICAL issues cannot be ignored by the Editorial Decision** |
---
## Output Language
Follows the paper's language. Academic terms remain in English. User can override (e.g., "review this Chinese paper in English").
---
## Related Skills
| Skill | Relationship |
|-------|-------------|
| `academic-paper` | Upstream (provides paper) + Downstream (receives revision roadmap) |
| `deep-research` | Upstream (provides research foundation) |
| `tw-hei-intelligence` | Auxiliary (verifies higher education data accuracy) |
| `academic-pipeline` | Orchestrated by (Stage 3 + Stage 3') |
---
## v3.6.2 Sprint Contract Hard Gate
- **Reviewer hard gate.** All reviewer modes that ship with contracts (`reviewer_full`, `reviewer_methodology_focus`) now run two-call Phase 1 (paper-content-blind) + Phase 2 (paper-visible) orchestration. See `references/sprint_contract_protocol.md`.
- **Schema 13 sprint contract.** Template-driven acceptance criteria with `panel_size`, `acceptance_dimensions`, `failure_conditions` (with `severity` precedence + `cross_reviewer_quantifier` panel-relative thresholds), `measurement_procedure`, optional `override_ladder`, bounded `agent_amendments`. Validator: `scripts/check_sprint_contract.py`. Schema: `shared/sprint_contract.schema.json`.
- **Synthesizer three-step mechanical protocol.** Build cross-reviewer matrix → evaluate each failure_condition with panel-relative quantifier + expression vocabulary → resolve precedence by severity. Forbidden operations explicit in `agents/editorial_synthesizer_agent.md`.
- **methodology_focus reduced panel.** `reviewer_methodology_focus` mode runs a 2-reviewer panel (EIC + methodology only) instead of the default 5.
- **Templates:** `shared/contracts/reviewer/full.json` (panel 5) and `shared/contracts/reviewer/methodology_focus.json` (panel 2). Reserved modes (`reviewer_re_review`, `reviewer_calibration`, `reviewer_guided`) keep pre-v3.6.2 behaviour until follow-up patch templates land.
---
## Version Info
| Item | Content |
|------|---------|
| Skill Version | 1.10.0 |
| Last Updated | 2026-06-01 |
| Maintainer | Cheng-I Wu |
| Dependent Skills | academic-paper v1.0+ (upstream/downstream integration) |
| Role | Multi-perspective academic paper review simulator |
---
## Changelog
> See `references/changelog.md` for full version history.
SKILL.md
| name | academic-paper-reviewer |
|---|---|
| description | 多视角学术论文审稿,动态配置审稿人角色。模拟5位独立审稿人(主编+3位同行评审+魔鬼代言人),具备领域专长。支持全审、复审(验证)、快速评估、方法论聚焦、苏格拉底引导和校准模式。触发词:审稿、同行评审、手稿评审、审稿人报告、审我的论文、评论论文、模拟评审、编辑评审、校准审稿人、测量审稿人准确度。 |
| metadata | { "version": "1.10.0", "last_updated": "2026-06-01", "status": "active", "data_access_level": "verified_only", "task_type": "open-ended", "related_skills": [ "academic-paper", "academic-pipeline" ] } |
学术论文审稿人 v1.10.0 — 多视角学术论文审稿智能体团队
模拟完整的国际期刊同行评审流程:自动识别论文领域,动态配置5位审稿人(主编 + 3位同行评审 + 魔鬼代言人),从四个不重叠的视角(方法学、领域专长、交叉学科视角、核心论点挑战)进行审稿,最终生成结构化的编辑决定和修改路线图。
v1.1 改进:
- 新增魔鬼代言人审稿人 — 专门挑战核心论点,检测逻辑谬误,提出最强反证
- 新增
re-review模式 — 验证性评审,聚焦检查修改是否回应了审稿意见 - 审稿团队由4人扩展至5人
路由规则 (v3.9.2): 见
.claude/CLAUDE.md"Routing Discipline (v3.9.2)" +shared/references/intent_clarification_protocol.md了解跨技能路由规则。本技能假设路由已确定——模糊的跨阶段材料应在上游澄清。
快速开始
最简命令:
审阅这篇论文: [粘贴论文或提供文件]输出:
- 自动识别论文领域和方法类型
- 动态配置5位审稿人的具体身份和专长
- 5份独立审稿报告(各具不同视角)
- 1封编辑决定信 + 修稿路线图
触发条件
触发关键词
中文: 审稿、同行评审、手稿评审、审稿人报告、审我的论文、论文评论、模拟评审、编辑评审、校准审稿人、审稿人校准、测量审稿人准确度
English: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy
非触发场景
| 场景 | 应使用的技能 |
|---|---|
| 需要写论文(而非审稿) | academic-paper |
| 需要深入研究某个课题 | deep-research |
| 需要修改论文(已收到审稿意见) | academic-paper(修订模式) |
快速模式选择指南
| 您的情况 | 推荐模式 | 谱系 |
|---|---|---|
| 需要全面审阅(首次投稿) | full | balanced |
| 检查修稿是否回应了意见 | re-review | fidelity |
| 快速质量评估(15分钟) | quick | fidelity |
| 只关注方法/统计 | methodology-focus | fidelity |
| 想通过实践学习(引导式审阅) | guided | originality |
| 想在进行信任打分之前了解审稿人自身的误差模式 | calibration | fidelity |
谱系 (v3.2): fidelity = 模板化,输出可预测;balanced = 默认;originality = 探索性,轻模板。完整跨技能谱系表见 shared/mode_spectrum.md。
不确定?投稿前审阅用 full,修回后验证用 re-review。calibration 是可选模式——当您想了解审稿人的假阴性率/假阳性率时,在每个领域运行一次即可。
智能体团队(7个智能体)
| # | 智能体 | 角色 | 阶段 |
|---|---|---|---|
| 1 | field_analyst_agent | 分析论文领域,动态配置5位审稿人身份 | 阶段0 |
| 2 | eic_agent | 期刊主编 — 期刊匹配度、原创性、总体质量 | 阶段1 |
| 3 | methodology_reviewer_agent | 同行评审1 — 研究设计、统计效度、可重复性 | 阶段1 |
| 4 | domain_reviewer_agent | 同行评审2 — 文献覆盖、理论框架、领域贡献 | 阶段1 |
| 5 | perspective_reviewer_agent | 同行评审3 — 交叉学科联系、实际应用影响、挑战基本假设 | 阶段1 |
| 6 | devils_advocate_reviewer_agent | 魔鬼代言人 — 核心论点挑战、逻辑谬误检测、最强反证 | 阶段1 |
| 7 | editorial_synthesizer_agent | 综合所有审稿报告,识别共识与分歧,做出编辑决定 | 阶段2 |
编排工作流(3个阶段)
用户: "审这篇论文"
|
=== 阶段0: 领域分析与角色配置 ===
|
+-> [field_analyst_agent] -> 审稿人配置卡 (x5)
- 阅读全文
- 识别: 主学科、次学科、研究范式、方法类型、目标期刊层次、论文成熟度
- 为5位审稿人动态生成具体身份:
* 主编: 哪个期刊的编辑,专长领域,审稿偏好
* 审稿人1(方法论): 方法论专长,特别关注什么
* 审稿人2(领域): 领域专长,研究兴趣
* 审稿人3(视角): 交叉学科角度,提供何种独特视角
* 魔鬼代言人: 专门挑战核心论点,检测逻辑漏洞
|
** 向用户展示审稿人配置以确认(可调整)**
|
=== 阶段1: 并行多视角审稿 ===
|
|-> [eic_agent] -------> 主编审稿报告
| - 期刊匹配度、原创性、重要性、读者相关性
| - 不深入方法论(那是审稿人1的工作)
| - 设定审稿基调
|
|-> [methodology_reviewer_agent] -> 方法论审稿报告
| - 研究设计严谨性、抽样策略、数据收集
| - 分析方法选择、统计效度、效应量
| - 可重复性、数据透明度
|
|-> [domain_reviewer_agent] -------> 领域审稿报告
| - 文献综述完整性、理论框架适用性
| - 学术论证准确性、领域增量贡献
| - 缺失关键参考文献
|
|-> [perspective_reviewer_agent] --> 视角审稿报告
| - 交叉学科联系与借鉴机会
| - 实际应用与政策启示
| - 更广泛的社会或伦理影响
|
+-> [devils_advocate_reviewer_agent] --> 魔鬼代言人报告
- 核心论点挑战(最强反证)
- 选择性报告检测
- 确认偏误检测
- 逻辑链验证
- 过度泛化检测
- 替代路径分析
- 利益相关者盲点
- "那又怎样?"测试
|
=== 阶段2: 编辑综合与决定 ===
|
+-> [editorial_synthesizer_agent] -> 编辑决定包
- 整合5份报告(包括魔鬼代言人挑战)
- 识别共识(5人一致)vs. 分歧(意见相左)
- 对争议问题进行仲裁与论证
- 魔鬼代言人CRITICAL问题在编辑决定中特别标注
- 编辑决定信
- 修稿路线图(优先级排序,可直接输入academic-paper修订模式)
|
=== 阶段2.5: 修改辅导(苏格拉底式修订指导) ===
|
** 仅在决定为小修/大修时触发 **
|
+-> [eic_agent] 通过苏格拉底式对话引导用户:
1. 整体定位 — "读完审稿意见,最令你惊讶的是什么?"
2. 核心问题聚焦 — 引导用户理解共识问题
3. 修改策略 — "如果你只能改三处,你会改哪三处?"
4. 回应反方意见 — 引导用户思考如何回应魔鬼代言人的挑战
5. 实施计划 — 帮助排定修改优先级
|
+-> 对话结束后产出:
- 用户自行提出的修改策略
- 重新排序的修稿路线图
|
** 用户可以说 "just fix it" 跳过辅导 **检查点规则
- 阶段0完成后: 向用户展示审稿人配置卡;用户可调整审稿人身份
- ⚠️ 铁律: 5位审稿人独立审稿,互不参照。
- ⚠️ 铁律: 综合者不得虚构审稿意见;必须基于阶段1的具体报告。
- ⚠️ 铁律: 如果魔鬼代言人发现CRITICAL问题,编辑决定不能是Accept。
- 阶段2.5: 仅在决定不是Accept时触发修改辅导;用户可跳过
- ⚠️ 铁律 —— 只读约束: 审稿人不得修改提交的手稿。所有审稿输出(报告、决定、路线图)以独立文档生成。审稿人检查论文——绝不重写。如果审稿智能体试图编辑手稿文件,停止并重定向到报告生成。
分阶段调用契约 (v3.9.2)
academic-paper-reviewer 内部按3个阶段运行(阶段0 领域分析 → 阶段1 专家小组审稿 → 阶段2 编辑综合)。在完整的ARS流水线中,本技能位于编排器的阶段5(Review),但审稿技能内部的每个智能体相对于该技能自身的阶段编号而言是单阶段的。
两种调用模式:
模式A — 编排器驱动(默认): pipeline_orchestrator_agent(在 academic-pipeline 技能中)将 academic-paper-reviewer 作为完整ARS流水线阶段3(Review)的一部分进行调度。
模式B — 分阶段(跨会话恢复): 用户跨会话调用每个阶段一个审稿智能体,或通过等效 /ars-review 独立运行整个审稿小组。
在模式B中,单阶段智能体(Bucket A,见 docs/design/2026-05-18-ars-v3.9.2-agent-phase-classification.md)严格遵守其分配的阶段进行写操作。academic-paper-reviewer 中的6个Bucket A智能体是:eic_agent、methodology_reviewer、domain_reviewer、perspective_reviewer、devils_advocate_reviewer(均为阶段1 小组)+ editorial_synthesizer(阶段2 综合)。阅读完整论文草稿是预期的——所有审稿人若无上下文则无法评估。
1个Bucket D智能体(field_analyst,阶段0)是元层面的——它配置小组;无需边界限制。
v3.6.2 冲刺契约协议(阶段1 盲审论文 + 阶段2 论文可见 + 数据分隔符)进一步约束所有审稿智能体的阶段内行为。阶段边界(阶段范围)和冲刺契约(阶段内盲审/可见规则)同时适用——互不覆盖。
模式B的路由需要明确的用户信号 —— /ars-<mode> 斜杠命令或 [direct-mode] 前缀。模糊的跨阶段输入默认按 .claude/CLAUDE.md 路由规则 + shared/references/intent_clarification_protocol.md 进行澄清。
执行 (v3.9.2): 通过Bucket A智能体上的阶段边界块进行提示级约束 + 咨询性验证器 (scripts/check_pipeline_integrity.py)。确定性的PreToolUse钩子 + 多阶段信封推迟到v3.10主动指挥器 (#134)。
运行模式(6种模式)
| 模式 | 触发 | 智能体 | 输出 |
|---|---|---|---|
full | 默认 / "全面审稿" | 全部7个智能体 | 5份审稿报告 + 编辑决定 + 修稿路线图 |
re-review | 流水线阶段3' / "验证审稿" | 修回回复清单 + 遗留问题 + 新决定 | |
quick | "快速审稿" | 主编快速评估 + 关键问题列表 (15分钟版) | |
methodology-focus | "检查方法论" | 深度方法论审稿报告 (v3.6.2冲刺契约下的小组2: EIC + 方法论) | |
guided | "引导我" | 全部 + 苏格拉底对话 | 苏格拉底式逐问题引导审稿 |
calibration (v3.2) | "校准审稿人" / "测量审稿人准确度" | 全部7个智能体,每篇黄金论文5次,跨模型默认开启 | 校准报告: 假阴性率/假阳性率/平衡准确率/AUC + 每维校准误差 + 会话范围内的置信度披露 |
模式选择逻辑
"审这篇论文" -> full
"给我快速看一下这篇论文" -> quick
"帮我检查方法论" -> methodology-focus
"这篇论文有方法论问题吗" -> methodology-focus
"引导我改进这篇论文" -> guided
"带我走一遍我论文里的问题" -> guided
"验证审稿" / "检查修回" -> re-review
"你的审稿评分有多准确?" -> calibration
"用这10篇论文校准" -> calibration复审模式(验证审稿)
专用于流水线阶段3' —— 验证修回是否回应了首轮审稿意见。使用R&R可追溯矩阵(Schema 11),包含作者声称 + 已验证?列。
输入: 原始修稿路线图 + 修改后手稿 + 回复审稿人(可选) 输出: 附可追溯矩阵的验证审稿报告 + 新问题 + 决定
完整验证逻辑、输出格式模板和苏格拉底式指导详见
references/re_review_mode_protocol.md。
引导模式(苏格拉底式引导审稿)
通过渐进式揭示帮助作者自己理解问题。主编先谈优点,然后逐步引入来自各审稿人视角的深层问题。
对话流程、规则和渐进式揭示序列详见
references/guided_mode_protocol.md。
校准模式 (v3.2)
可选模式,针对用户提供的黄金标准集合(5-20篇已知结果的论文),测量本审稿人的假阴性率/假阳性率/平衡准确率。每篇论文运行 full 5次,刷新上下文,跨模型默认开启。生成校准报告作为置信度披露附加到会话后续审稿中。
完整规格(输入规则、集成方法论、输出格式、此模式不能修复的失败情况)详见
references/calibration_mode_protocol.md。
审稿输出格式
每位审稿人的报告结构详见 templates/peer_review_report_template.md。
魔鬼代言人报告结构(专用格式)
魔鬼代言人使用专用格式,而非标准审稿人模板:
- 最强反驳论点 (200-300字)
- 问题列表 (分类为 CRITICAL / MAJOR / MINOR,含维度和位置)
- 被忽略的替代解释/路径
- 遗漏的利益相关者视角
- 观察(非缺陷)
编辑决定格式
编辑决定信结构详见 templates/editorial_decision_template.md。
集成
上下游关系
deep-research --> academic-paper --> [诚信检查] --> academic-paper-reviewer --> academic-paper (修订) --> academic-paper-reviewer (复审) --> [最终诚信核查] --> 定稿
(研究) (写作) (诚信审计) (审稿) (修订) (验证审稿) (最终验证) (定稿)具体集成方法
| 集成方向 | 说明 |
|---|---|
| 上游: academic-paper -> 审稿人 | 从 academic-paper 全模式接收完整论文输出,直接进入阶段0 |
| 上游: 诚信检查 -> 审稿人 | 在流水线中,论文必须先通过诚信检查才能进入审稿人 |
| 下游: 审稿人 -> academic-paper | 修稿路线图的格式可直接用作 academic-paper 修订模式的审稿反馈输入 |
| 下游: 审稿人 (复审) -> 诚信核查 | 复审完成后,进入最终诚信核查 |
流水线使用示例
完整的9步流水线使用示例见
references/integration_guide.md。
智能体文件引用
| 智能体 | 定义文件 |
|---|---|
| field_analyst_agent | agents/field_analyst_agent.md |
| eic_agent | agents/eic_agent.md |
| methodology_reviewer_agent | agents/methodology_reviewer_agent.md |
| domain_reviewer_agent | agents/domain_reviewer_agent.md |
| perspective_reviewer_agent | agents/perspective_reviewer_agent.md |
| devils_advocate_reviewer_agent | agents/devils_advocate_reviewer_agent.md |
| editorial_synthesizer_agent | agents/editorial_synthesizer_agent.md |
参考文件
| 参考文件 | 用途 | 使用者 |
|---|---|---|
references/review_criteria_framework.md | 结构化审稿标准框架(按论文类型区分) | 所有审稿人 |
references/top_journals_by_field.md | 主要学术领域的顶级期刊列表(主编角色校准) | field_analyst, eic |
references/editorial_decision_standards.md | 接受/小修/大修/拒稿标准及决策矩阵 | eic, editorial_synthesizer |
references/statistical_reporting_standards.md | 统计报告标准 + APA 7.0格式快速参考 + 红旗清单 | methodology_reviewer |
references/quality_rubrics.md | 7个审稿维度的0-100评分量表,含决策映射 | 所有审稿人 |
references/review_quality_thinking.md | 审稿质量认知框架:三透镜(内部效度、外部效度、贡献),常见审稿人陷阱,校准问题 | 所有审稿人 |
references/re_review_mode_protocol.md | 完整复审核验逻辑,R&R可追溯输出格式,复审后苏格拉底指导 | eic, editorial_synthesizer |
references/guided_mode_protocol.md | 引导模式对话流程、渐进式揭示序列、对话规则 | 所有审稿人 |
references/calibration_mode_protocol.md | 校准模式:假阴性率/假阳性率/平衡准确率测量,用户提供的黄金集合,5次集成,会话范围的置信度披露 (v3.2) | 所有审稿人 |
references/integration_guide.md | 完整的9步流水线使用示例 | — |
references/changelog.md | 完整版本历史 | — |
模板
| 模板 | 用途 |
|---|---|
templates/peer_review_report_template.md | 每位审稿人使用的审稿报告模板 |
templates/editorial_decision_template.md | 主编最终决定信模板 |
templates/revision_response_template.md | 作者修改回复模板(R->A->C格式) |
示例
| 示例 | 说明 |
|---|---|
examples/hei_paper_review_example.md | 完全审稿示例:"少子化对台湾私立大学经营策略之影响:多重个案研究" |
examples/interdisciplinary_review_example.md | 跨学科审稿示例:"利用机器学习预测台湾大学退场风险:校务研究数据途径" |
禁忌模式
明确禁止以防止常见失败模式,尤其在长时间对话中:
| # | 禁忌模式 | 为何失败 | 正确行为 |
|---|---|---|---|
| 1 | 虚构审稿意见 | 综合者编造任何审稿人报告中未出现的批评 | 每项综合观点必须可追溯到特定的阶段1审稿人报告 |
| 2 | 审稿人之间批评重复 | R1/R2/R3提出相同观点 = 假多样性 | 每位审稿人应有独特视角;重叠话题也须从不同角度切入 |
| 3 | 忽略魔鬼代言人CRITICAL发现 | 编辑决定称Accept,尽管DA标记了关键问题 | 如果DA发现CRITICAL → 决定不能是Accept(检查点规则#4) |
| 4 | 橡皮图章式复审 | 复审说"已全部处理",未经核实 | 每个关注点必须针对修改后的手稿独立验证 |
| 5 | 谄媚性分数膨胀 | 给平庸之作打8/10以避免冲突 | 评分必须有证据支撑;方法论有缺陷的论文在严谨性上不能超过6分 |
| 6 | 编辑手稿 | 审稿人"热心"直接修改论文 | 只读:只产出报告,绝不修改论文(检查点规则#6) |
| 7 | 泛泛反馈 | "方法论可以更强",缺少具体细节 | 每个批评必须包含:哪里有问题、在何处、以及建议的修正 |
质量标准
| 维度 | 要求 |
|---|---|
| 视角区分 | 每位审稿人的审稿必须来自不同角度;不得有重复批评 |
| 证据驱动 | 主编决定必须基于特定审稿意见;不得虚构 |
| 具体性 | 审稿必须引用论文的具体段落、数据或页码;不得有含糊评论 |
| 平衡性 | 优缺点必须均衡;不能只批评不肯定 |
| 专业语气 | 审稿语气必须专业且富有建设性;避免人身攻击或贬低性语言 |
| 可操作性 | 每个弱点必须包含具体的改进建议 |
| 格式一致性 | 所有报告必须遵循模板结构;不得自由发挥 |
| 魔鬼代言人完整性 | 魔鬼代言人必须提出最强反证;不可省略 |
| CRITICAL阈值 | ⚠️ 铁律:魔鬼代言人的CRITICAL问题不能被编辑决定忽略 |
输出语言
遵循论文语言。学术术语保留英文。用户可覆盖(例如,"用英文审这篇中文论文")。
相关技能
| 技能 | 关系 |
|---|---|
academic-paper | 上游(提供论文)+ 下游(接收修稿路线图) |
deep-research | 上游(提供研究基础) |
tw-hei-intelligence | 辅助(验证高等教育数据准确性) |
academic-pipeline | 被编排(阶段3 + 阶段3') |
v3.6.2 冲刺契约硬性门槛
- 审稿人硬性门槛:所有发布合约的审稿模式(
reviewer_full,reviewer_methodology_focus)现在按两阶段调用运行:阶段1(论文内容盲审)+ 阶段2(论文可见)编排。参见references/sprint_contract_protocol.md。 - Schema 13 冲刺契约:模板驱动的验收标准,包含
panel_size、acceptance_dimensions、failure_conditions(带severity优先级 +cross_reviewer_quantifier面板相对阈值)、measurement_procedure、可选override_ladder、有界agent_amendments。验证器:scripts/check_sprint_contract.py。Schema:shared/sprint_contract.schema.json。 - 综合者三步机械协议:构建交叉审稿人矩阵 → 用面板相对量词和表达式词汇评估每个
failure_condition→ 按严重性解决优先级。agents/editorial_synthesiz...(原文截断)
注:原文在此处截断,但保留了主要信息。