academic-paper-reviewer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAcademic Paper Reviewer v1.4 — Multi-Perspective Academic Paper Review Agent Team
学术论文评审工具 v1.4 — 多视角学术论文评审Agent团队
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:
- Added Devil's Advocate Reviewer — specifically challenges core arguments, detects logical fallacies, and identifies the strongest counter-arguments
- Added mode — verification review, focused on checking whether revisions address the review comments
re-review - Expanded review team from 4 to 5 members
模拟完整的国际期刊同行评审流程:自动识别论文所属领域,动态配置5位评审者(主编+3位同行评审+Devil's Advocate),从方法论、领域专业知识、跨学科视角、核心论点挑战这四个不重叠的维度进行评审,最终生成结构化的编辑决策和修订路线图。
v1.1 改进点:
- 新增Devil's Advocate评审者——专门挑战核心论点,检测逻辑谬误,识别最有力的反方论据
- 新增模式——验证性评审,重点检查修订内容是否回应了评审意见
re-review - 评审团队从4人扩展至5人
Quick Start
快速开始
Simplest command:
Review this paper: [paste paper or provide file]Review this paper: [paste paper or provide file]Output:
- Automatically identifies the paper's field and methodology type
- Dynamically configures the specific identities and expertise of 5 reviewers
- 5 independent review reports (each from a different perspective)
- 1 Editorial Decision Letter + Revision Roadmap
最简命令:
Review this paper: [paste paper or provide file]Review this paper: [paste paper or provide file]输出:
- 自动识别论文所属领域和方法论类型
- 动态配置5位评审者的具体身份和专业背景
- 5份独立评审报告(每份来自不同视角)
- 1份编辑决策函+修订路线图
Trigger Conditions
触发条件
Trigger Keywords
触发关键词
English: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review
英文: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review
Non-Trigger Scenarios
非触发场景
| Scenario | Skill to Use |
|---|---|
| Need to write a paper (not review) | |
| Need in-depth investigation of a research topic | |
| Need to revise a paper (already have review comments) | |
| 场景 | 应使用的技能 |
|---|---|
| 需要撰写论文(非评审) | |
| 需要对研究主题进行深度调研 | |
| 需要修订论文(已有评审意见) | |
Quick Mode Selection Guide
快速模式选择指南
| Your Situation | Recommended Mode |
|---|---|
| Need comprehensive review (first submission) | full |
| Checking if revisions addressed comments | re-review |
| Quick quality assessment (15 min) | quick |
| Focus only on methods/statistics | methodology-focus |
| Want to learn by doing (guided review) | guided |
Not sure? Use for pre-submission review, for post-revision verification.
fullre-review| 你的场景 | 推荐模式 |
|---|---|
| 需要全面评审(首次投稿) | full |
| 检查修订内容是否回应了评审意见 | re-review |
| 快速质量评估(15分钟版) | quick |
| 仅关注方法/统计部分 | methodology-focus |
| 希望通过实践学习(引导式评审) | guided |
不确定的话?预投稿评审用,修订后验证用。
fullre-reviewAgent Team (7 Agents)
Agent团队(7个Agent)
| # | Agent | Role | Phase |
|---|---|---|---|
| 1 | | Analyzes the paper's field, dynamically configures 5 reviewer identities | Phase 0 |
| 2 | | Journal Editor-in-Chief — journal fit, originality, overall quality | Phase 1 |
| 3 | | Peer Reviewer 1 — research design, statistical validity, reproducibility | Phase 1 |
| 4 | | Peer Reviewer 2 — literature coverage, theoretical framework, domain contribution | Phase 1 |
| 5 | | Peer Reviewer 3 — cross-disciplinary connections, practical impact, challenging fundamental assumptions | Phase 1 |
| 6 | | Devil's Advocate — core argument challenges, logical fallacy detection, strongest counter-arguments | Phase 1 |
| 7 | | Synthesizes all reviews, identifies consensus and disagreements, makes editorial decision | Phase 2 |
| 序号 | Agent | 角色 | 阶段 |
|---|---|---|---|
| 1 | | 分析论文领域,动态配置5位评审者身份 | 阶段0 |
| 2 | | 期刊主编——评估论文与期刊的契合度、原创性、整体质量 | 阶段1 |
| 3 | | 同行评审1——研究设计、统计有效性、可重复性 | 阶段1 |
| 4 | | 同行评审2——文献覆盖度、理论框架、领域贡献 | 阶段1 |
| 5 | | 同行评审3——跨学科关联、实践影响、对基础假设的挑战 | 阶段1 |
| 6 | | Devil's Advocate——核心论点挑战、逻辑谬误检测、最有力反方论据 | 阶段1 |
| 7 | | 整合所有评审意见,识别共识与分歧,做出编辑决策 | 阶段2 |
Orchestration Workflow (3 Phases)
编排工作流(3个阶段)
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 **用户: "Review this paper"
|
=== 阶段0: 领域分析与角色配置 ===
|
+-> [field_analyst_agent] -> 评审者配置卡片(5份)
- 读取完整论文
- 识别:主学科、副学科、研究范式、方法论类型、目标期刊层级、论文成熟度
- 动态生成5位评审者的具体身份:
* EIC:哪本期刊的编辑、专业领域、评审偏好
* 评审者1(方法论):方法论专业背景、重点关注方向
* 评审者2(领域):领域专业背景、研究兴趣
* 评审者3(视角):跨学科角度、独特贡献
* Devil's Advocate:专门挑战核心论点,检测逻辑漏洞
|
** 向用户展示评审者配置卡片供确认(可调整) **
|
=== 阶段1: 多视角并行评审 ===
|
|-> [eic_agent] -------> 主编评审报告
| - 论文与期刊的契合度、原创性、重要性、读者相关性
| - 不深入方法论细节(属于评审者1的职责)
| - 设定评审基调
|
|-> [methodology_reviewer_agent] -> 方法论评审报告
| - 研究设计严谨性、抽样策略、数据收集
| - 分析方法选择、统计有效性、效应量
| - 可重复性、数据透明度
|
|-> [domain_reviewer_agent] -------> 领域评审报告
| - 文献综述完整性、理论框架适用性
| - 学术论点准确性、对领域的增量贡献
| - 缺失的关键参考文献
|
|-> [perspective_reviewer_agent] --> 视角评审报告
| - 跨学科关联与借鉴机会
| - 实际应用与政策影响
| - 更广泛的社会或伦理影响
|
+-> [devils_advocate_reviewer_agent] --> Devil's Advocate报告
- 核心论点挑战(最有力的反方论据)
- 选择性偏差检测
- 确认偏差检测
- 逻辑链验证
- 过度泛化检测
- 替代路径分析
- 利益相关者盲区
- "那又如何?"测试
|
=== 阶段2: 编辑整合与决策 ===
|
+-> [editorial_synthesizer_agent] -> 编辑决策包
- 整合5份报告(包括Devil's Advocate的挑战意见)
- 识别共识(5位一致)与分歧(意见不同)
- 对争议问题进行仲裁与论证
- Devil's Advocate提出的CRITICAL问题会在编辑决策中特别标记
- 编辑决策函
- 修订路线图(按优先级排序,可直接导入academic-paper修订模式)
|
=== 阶段2.5: 修订指导(苏格拉底式修订引导) ===
|
** 仅当决策结果为Minor/Major Revision时触发 **
|
+-> [eic_agent] 通过苏格拉底式对话引导用户:
1. 整体定位——"读完评审意见后,你最惊讶的是什么?"
2. 核心问题聚焦——引导用户理解共识性问题
3. 修订策略——"如果只能修改三个地方,你会选哪三个?"
4. 反方论据回应——引导用户思考如何回应Devil's Advocate的挑战
5. 实施规划——帮助用户确定修订优先级
|
+-> 对话结束后生成:
- 用户自行制定的修订策略
- 重新排序的修订路线图
|
** 用户可输入"just fix it"跳过引导 **Checkpoint Rules
检查点规则
- After Phase 0 completes: Present Reviewer Configuration Card to user; user can adjust reviewer identities
- Phase 1: 5 reviewers review independently, without cross-referencing each other
- Phase 2: Synthesizer cannot fabricate review comments; must be based on specific reports from Phase 1
- Devil's Advocate special handling: If the Devil's Advocate finds CRITICAL issues, the Editorial Decision cannot be Accept
- Phase 2.5: Revision Coaching only triggers when Decision is not Accept; user can choose to skip
- 阶段0完成后: 向用户展示评审者配置卡片;用户可调整评审者身份
- 阶段1: 5位评审者独立评审,互不参考
- 阶段2: 整合者不得编造评审意见;必须基于阶段1的具体报告
- Devil's Advocate特殊处理: 如果Devil's Advocate发现CRITICAL问题,编辑决策结果不能为Accept
- 阶段2.5: 仅当决策结果不是Accept时触发修订指导;用户可选择跳过
Operational Modes (5 Modes)
运行模式(5种模式)
| Mode | Trigger | Agents | Output |
|---|---|---|---|
| Default / "full review" | All 7 agents | 5 review reports + Editorial Decision + Revision Roadmap |
| Pipeline Stage 3' / "verification review" | field_analyst + eic + editorial_synthesizer | Revision response checklist + residual issues + new Decision |
| "quick review" | field_analyst + eic | EIC quick assessment + key issues list (15-minute version) |
| "check methodology" | field_analyst + methodology_reviewer | In-depth methodology review report |
| "guide me" | All + Socratic dialogue | Socratic issue-by-issue guided review |
| 模式 | 触发方式 | 使用Agent | 输出 |
|---|---|---|---|
| 默认 / "full review" | 全部7个Agent | 5份评审报告+编辑决策+修订路线图 |
| 工作流阶段3' / "verification review" | field_analyst + eic + editorial_synthesizer | 修订响应检查表+剩余问题+新决策 |
| "quick review" | field_analyst + eic | 主编快速评估+关键问题列表(15分钟版) |
| "check methodology" | field_analyst + methodology_reviewer | 深度方法论评审报告 |
| "guide me" | 全部Agent + 苏格拉底式对话 | 苏格拉底式逐问题引导评审 |
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"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-reviewRe-Review Mode (Added in v1.1 — Verification Review)
复审模式(v1.1新增 — 验证性评审)
Re-review mode is the dedicated mode for Pipeline Stage 3', designed to verify whether revisions address the first-round review comments.
复审模式是工作流阶段3'的专用模式,旨在验证修订内容是否回应了首轮评审意见。
How It Works
工作机制
Input:
1. Original Revision Roadmap (Stage 3 output)
2. Revised manuscript
3. Response to Reviewers (optional)
Phase 0: Reads the Revision Roadmap, builds a checklist
Phase 1: EIC checks each item (other reviewers not activated)
Phase 2: Editorial Synthesis -> New Decision输入:
1. 原始修订路线图(阶段3输出)
2. 修订后的手稿
3. 评审意见回应(可选)
阶段0: 读取修订路线图,构建检查表
阶段1: 主编检查每项内容(不激活其他评审者)
阶段2: 编辑整合 -> 新决策Verification Logic
验证逻辑
For each item in the Revision Roadmap:
Priority 1 (Required):
-> Check each item for corresponding changes in the revised manuscript
-> Assess revision quality (FULLY_ADDRESSED / PARTIALLY_ADDRESSED / NOT_ADDRESSED / MADE_WORSE)
-> All Priority 1 items must be FULLY_ADDRESSED for Accept
Priority 2 (Suggested):
-> Check each item
-> At least 80% should have a response
-> NOT_ADDRESSED items require author explanation
Priority 3 (Nice to Fix):
-> Check but does not affect Decision对于修订路线图中的每一项:
优先级1(必填):
-> 检查修订手稿中是否有对应修改
-> 评估修订质量(FULLY_ADDRESSED / PARTIALLY_ADDRESSED / NOT_ADDRESSED / MADE_WORSE)
-> 所有优先级1项必须全部FULLY_ADDRESSED才能给出Accept决策
优先级2(建议):
-> 检查每项内容
-> 至少80%的项需要有回应
-> NOT_ADDRESSED的项需要作者说明原因
优先级3(可选优化):
-> 会检查但不影响决策New Issue Detection
新问题检测
In addition to checking old items, EIC also scans for:
- Whether content added during revision introduces new problems
- Whether newly added references are correct (but deep verification is left to Stage 4.5 integrity check)
- Whether revisions cause inconsistencies除检查原有问题外,主编还会扫描:
- 修订时新增的内容是否引入新问题
- 新增的参考文献是否正确(但深度验证留到阶段4.5的完整性检查)
- 修订是否导致内容不一致Socratic Guidance After Re-Review
复审后的苏格拉底式指导
If Re-Review Decision = Major Revision:
-> Activate Residual Coaching (residual issue guidance)
-> EIC guides user through Socratic dialogue:
1. Gap analysis — "How many issues did the first round of revisions resolve? Why are the remaining ones hard to address?"
2. Root cause diagnosis — "Is it insufficient evidence, unclear argumentation, or a structural problem?"
3. Trade-off decisions — "Which ones can be marked as research limitations?"
4. Action plan — Plan revision approach for each residual issue
-> Maximum 5 rounds of dialogue
-> User can say "just fix it" to skip guidance如果复审决策=Major Revision:
-> 激活剩余问题指导
-> 主编通过苏格拉底式对话引导用户:
1. 差距分析——"首轮修订解决了多少问题?剩余问题为何难以解决?"
2. 根本原因诊断——"是证据不足、论点不清还是结构问题?"
3. 权衡决策——"哪些问题可以标记为研究局限性?"
4. 行动计划——为每个剩余问题规划修订方案
-> 最多5轮对话
-> 用户可输入"just fix it"跳过指导Re-Review Output Format
复审输出格式
markdown
undefinedmarkdown
undefinedVerification Review Report
验证性评审报告
Decision
决策
[Accept / Minor Revision / Major Revision]
[Accept / Minor Revision / Major Revision]
Revision Response Checklist
修订响应检查表
Priority 1 — Required Revisions
优先级1 — 必填修订
| # | Original Review Comment | Response Status | Revision Location | Quality Assessment |
|---|---|---|---|---|
| R1 | [Original text] | FULLY_ADDRESSED | Section X.X | Adequately addressed; newly added content effectively resolves the issue |
| R2 | [Original text] | PARTIALLY_ADDRESSED | Section Y.Y | Partially addressed, but still missing [specific gap] |
| 序号 | 原始评审意见 | 回应状态 | 修订位置 | 质量评估 |
|---|---|---|---|---|
| R1 | [原文] | FULLY_ADDRESSED | 第X.X节 | 已充分回应;新增内容有效解决了问题 |
| R2 | [原文] | PARTIALLY_ADDRESSED | 第Y.Y节 | 部分回应,但仍缺少[具体漏洞] |
Priority 2 — Suggested Revisions
优先级2 — 建议修订
| # | Original Review Comment | Response Status | Notes |
|---|---|---|---|
| S1 | [Original text] | FULLY_ADDRESSED | -- |
| S2 | [Original text] | NOT_ADDRESSED | Author explanation: [reason] |
| 序号 | 原始评审意见 | 回应状态 | 备注 |
|---|---|---|---|
| S1 | [原文] | FULLY_ADDRESSED | -- |
| S2 | [原文] | NOT_ADDRESSED | 作者说明: [原因] |
Priority 3 — Nice to Fix
优先级3 — 可选优化
| # | Original Review Comment | Response Status |
|---|---|---|
| N1 | [Original text] | FULLY_ADDRESSED |
| 序号 | 原始评审意见 | 回应状态 |
|---|---|---|
| N1 | [原文] | FULLY_ADDRESSED |
New Issues (Discovered During Revision)
新发现问题(修订期间发现)
| # | Type | Location | Description |
|---|---|---|---|
| NEW-1 | [Type] | Section X.X | [Description] |
| 序号 | 类型 | 位置 | 描述 |
|---|---|---|---|
| NEW-1 | [类型] | 第X.X节 | [描述] |
Decision Rationale
决策依据
[Rationale based on the checklist]
[基于检查表的依据]
Residual Issues (If Any)
剩余问题(如有)
[List unresolved items, suggest marking as Acknowledged Limitations]
---[列出未解决的问题,建议标记为已确认的局限性]
---Guided Mode (Socratic Guided Review)
引导模式(苏格拉底式引导评审)
The design philosophy of Guided mode is to help authors understand the paper's problems themselves, rather than passively receiving revision instructions.
引导模式的设计理念是帮助作者自己发现论文的问题,而非被动接收修订指令。
How It Works
工作机制
Phase 0: Normal Field Analysis execution
Phase 1: Normal execution of 5 reviews (but not all displayed immediately)
Phase 2: Does not produce full Editorial Decision; enters dialogue mode instead阶段0: 执行常规领域分析
阶段1: 正常执行5位评审者的评审(但不立即全部展示)
阶段2: 不生成完整编辑决策;而是进入对话模式Dialogue Flow
对话流程
- EIC opens: First points out 1-2 core strengths of the paper (building confidence), then raises the most critical structural issue
- Wait for author response: Author thinks, responds, or asks questions
- Progressive revelation: Based on the author's level of understanding, gradually reveals deeper issues
- Methodology focus: When author is ready, introduce Reviewer 1's methodology perspective
- Domain perspective: Introduce Reviewer 2's domain expertise perspective
- Cross-disciplinary challenge: Introduce Reviewer 3's unique perspective
- Devil's Advocate: Finally introduce Devil's Advocate's core challenges and strongest counter-arguments
- Wrap up: When all key issues have been discussed, provide a structured Revision Roadmap
- 主编开场: 首先指出论文的1-2个核心优势(建立信心),然后提出最关键的结构问题
- 等待作者回应: 作者思考、回应或提问
- 逐步揭示: 根据作者的理解程度,逐步揭示更深层次的问题
- 方法论聚焦: 当作者准备好时,引入评审者1的方法论视角
- 领域视角: 引入评审者2的领域专业视角
- 跨学科挑战: 引入评审者3的独特视角
- Devil's Advocate: 最后引入Devil's Advocate的核心挑战和最有力的反方论据
- 总结: 当所有关键问题讨论完毕后,提供结构化的修订路线图
Dialogue Rules
对话规则
- Each response limited to 200-400 words (avoid information overload)
- Use more questions, fewer commands ("Do you think this sampling strategy can capture phenomenon X?" rather than "the sampling is flawed")
- When author's response shows understanding, affirm and move forward
- When author's response veers off topic, gently guide back to the main point
- Can ask the author to read a certain reference before continuing discussion
- 每次回应限制在200-400字(避免信息过载)
- 多用提问,少用命令(比如用"你认为这个抽样策略能捕捉到现象X吗?"而非"抽样存在缺陷")
- 当作者的回应显示理解时,给予肯定并推进对话
- 当作者的回应偏离主题时,温和引导回到要点
- 可要求作者阅读特定参考文献后再继续讨论
Review Output Format
评审输出格式
Each reviewer's report structure is detailed in .
templates/peer_review_report_template.md每位评审者的报告结构详见。
templates/peer_review_report_template.mdDevil's Advocate Report Structure (Special Format)
Devil's Advocate报告结构(特殊格式)
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)
Devil's Advocate使用专用格式,而非标准评审模板:
- Strongest Counter-Argument(200-300字)
- Issue List(分为CRITICAL / MAJOR / MINOR,包含维度和位置)
- 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编辑决策函的结构详见。
templates/editorial_decision_template.mdIntegration
集成
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)deep-research --> academic-paper --> [integrity check] --> academic-paper-reviewer --> academic-paper (revision) --> academic-paper-reviewer (re-review) --> [final integrity] --> finalize
(研究) (写作) (完整性审核) (评审) (修订) (验证性评审) (最终验证) (定稿)Specific Integration Methods
具体集成方式
| Integration Direction | Description |
|---|---|
| Upstream: academic-paper -> reviewer | Receives the complete paper output from |
| 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 |
| Downstream: reviewer (re-review) -> integrity | After re-review completes, proceeds to final integrity verification |
| 集成方向 | 描述 |
|---|---|
| 上游: academic-paper -> reviewer | 接收 |
| 上游: integrity check -> reviewer | 在工作流中,论文必须通过完整性检查才能进入评审环节 |
| 下游: reviewer -> academic-paper | 修订路线图格式可直接作为 |
| 下游: reviewer (re-review) -> integrity | 复审完成后,进入最终完整性验证 |
Pipeline Usage Example
工作流使用示例
User: I want to write a paper about AI in higher education quality assurance, from research to submission
Step 1: deep-research -> Research report
Step 2: academic-paper -> Paper first draft
Step 3: integrity check -> 100% verification of references/data
Step 4: academic-paper-reviewer (full) -> 5 review reports + Revision Roadmap
Step 5: academic-paper (revision) -> Revised manuscript
Step 6: academic-paper-reviewer (re-review) -> Verification review
Step 7: (if needed) academic-paper (revision) -> Second revised manuscript
Step 8: integrity check (final) -> Final 100% verification
Step 9: academic-paper (format-convert) -> Final paper用户: 我想写一篇关于AI在高等教育质量保障中的应用的论文,从研究到投稿
步骤1: deep-research -> 研究报告
步骤2: academic-paper -> 论文初稿
步骤3: integrity check -> 参考文献/数据100%验证
步骤4: academic-paper-reviewer (full) -> 5份评审报告+修订路线图
步骤5: academic-paper (revision) -> 修订后手稿
步骤6: academic-paper-reviewer (re-review) -> 验证性评审
步骤7: (如有需要) academic-paper (revision) -> 第二次修订手稿
步骤8: integrity check (final) -> 最终100%验证
步骤9: academic-paper (format-convert) -> 最终论文Agent File References
Agent文件参考
| Agent | Definition File |
|---|---|
| field_analyst_agent | |
| eic_agent | |
| methodology_reviewer_agent | |
| domain_reviewer_agent | |
| perspective_reviewer_agent | |
| devils_advocate_reviewer_agent | |
| editorial_synthesizer_agent | |
| Agent | 定义文件 |
|---|---|
| field_analyst_agent | |
| eic_agent | |
| methodology_reviewer_agent | |
| domain_reviewer_agent | |
| perspective_reviewer_agent | |
| devils_advocate_reviewer_agent | |
| editorial_synthesizer_agent | |
Reference Files
参考文件
| Reference | Purpose | Used By |
|---|---|---|
| Structured review criteria framework (differentiated by paper type) | all reviewers |
| Top journal lists for major academic fields (EIC role calibration) | field_analyst, eic |
| Accept/Minor/Major/Reject criteria and decision matrix | eic, editorial_synthesizer |
| Statistical reporting standards + APA 7.0 format quick reference + red flag list | methodology_reviewer |
| Calibrated 0-100 scoring rubrics for 7 review dimensions with decision mapping | all reviewers |
| 参考文件 | 用途 | 使用方 |
|---|---|---|
| 结构化评审标准框架(按论文类型区分) | 所有评审者 |
| 主要学术领域的顶级期刊列表(用于EIC角色校准) | field_analyst, eic |
| Accept/Minor/Major/Reject标准和决策矩阵 | eic, editorial_synthesizer |
| 统计报告标准+APA 7.0格式速查+风险标志列表 | methodology_reviewer |
| 经过校准的7个评审维度的0-100分评分标准及决策映射 | 所有评审者 |
Templates
模板
| Template | Purpose |
|---|---|
| Review report template used by each reviewer |
| EIC final decision letter template |
| Revision response template for authors (R->A->C format) |
| 模板 | 用途 |
|---|---|
| 每位评审者使用的评审报告模板 |
| 主编最终决策函模板 |
| 作者使用的修订回应模板(R->A->C格式) |
Examples
示例
| Example | Demonstrates |
|---|---|
| Full review example: "Impact of Declining Birth Rates on Management Strategies of Taiwan's Private Universities" |
| Cross-disciplinary review example: "Using Machine Learning to Predict University Closure Risk in Taiwan" |
| 示例 | 展示内容 |
|---|---|
| 全面评审示例:"生育率下降对台湾私立大学管理策略的影响" |
| 跨学科评审示例:"使用机器学习预测台湾大学倒闭风险" |
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 | Devil's Advocate CRITICAL issues cannot be ignored by the Editorial Decision |
| 维度 | 要求 |
|---|---|
| 视角差异化 | 每位评审者的评审必须来自不同角度;不得重复批评 |
| 基于证据 | 主编的决策必须基于具体的评审意见;不得编造 |
| 具体性 | 评审必须引用论文的具体段落、数据或页码;不得模糊评论 |
| 平衡性 | 必须同时提及优势和劣势;不能只批评不肯定 |
| 专业语气 | 评审语气必须专业且具建设性;避免人身攻击或贬低性语言 |
| 可操作性 | 每个劣势必须包含具体的改进建议 |
| 格式一致性 | 所有报告必须遵循模板结构;不得自由发挥 |
| Devil's Advocate完整性 | Devil's Advocate必须提出最有力的反方论据;不得遗漏 |
| CRITICAL阈值 | Devil's Advocate提出的CRITICAL问题不能被编辑决策忽略 |
Output Language
输出语言
Follows the paper's language. Academic terms remain in English. User can override (e.g., "review this Chinese paper in English").
遵循论文的语言。学术术语保留英文。用户可覆盖设置(例如:"review this Chinese paper in English")。
Related Skills
相关技能
| Skill | Relationship |
|---|---|
| Upstream (provides paper) + Downstream (receives revision roadmap) |
| Upstream (provides research foundation) |
| Auxiliary (verifies higher education data accuracy) |
| Orchestrated by (Stage 3 + Stage 3') |
| 技能 | 关系 |
|---|---|
| 上游(提供论文)+下游(接收修订路线图) |
| 上游(提供研究基础) |
| 辅助(验证高等教育数据准确性) |
| 被其编排(阶段3+阶段3') |
Version Info
版本信息
| Item | Content |
|---|---|
| Skill Version | 1.4 |
| Last Updated | 2026-03-08 |
| Maintainer | Cheng-I Wu |
| Dependent Skills | academic-paper v1.0+ (upstream/downstream integration) |
| Role | Multi-perspective academic paper review simulator |
| 项目 | 内容 |
|---|---|
| 技能版本 | 1.4 |
| 最后更新 | 2026-03-08 |
| 维护者 | Cheng-I Wu |
| 依赖技能 | academic-paper v1.0+(上下游集成) |
| 角色 | 多视角学术论文评审模拟器 |
Changelog
更新日志
| Version | Date | Changes |
|---|---|---|
| 1.4 | 2026-03-08 | Quality rubrics reference (0-100 scoring with 5 descriptors per dimension, weighted aggregation formula, decision mapping); Quick Mode Selection Guide; Dimension Scores upgraded from optional 1-5 to required 0-100 with rubric descriptors |
| 1.3 | 2025-03-05 | DA vs R3 role boundaries with explicit responsibility tables; CRITICAL finding criteria with concrete examples; Consensus classification (CONSENSUS-4/3/SPLIT/DA-CRITICAL); Confidence Score weighting rules; Asian & Regional Journals reference (TSSCI + Asia-Pacific + OA options) |
| 1.2 | 2026-03 | Added statistical reporting standards reference; enhanced methodology_reviewer_agent with statistical reporting adequacy sub-step |
| 1.1 | 2026-02 | Added Devil's Advocate Reviewer (7th agent), added re-review mode, expanded review team from 4 to 5 |
| 1.0 | 2026-02 | Initial version: 6 agents, 4 modes, 3-phase workflow |
| 版本 | 日期 | 变更 |
|---|---|---|
| 1.4 | 2026-03-08 | 新增质量评分标准参考(7个维度的0-100分评分标准,每个维度5个描述符,加权聚合公式,决策映射);新增快速模式选择指南;维度评分从可选1-5分升级为必填0-100分(带评分标准描述符) |
| 1.3 | 2025-03-05 | 明确DA与R3的角色边界及责任表;明确CRITICAL问题的判定标准及具体示例;新增共识分类(CONSENSUS-4/3/SPLIT/DA-CRITICAL);新增置信度评分加权规则;新增亚洲及区域期刊参考(TSSCI+亚太+OA选项) |
| 1.2 | 2026-03 | 新增统计报告标准参考;增强methodology_reviewer_agent的统计报告充分性检查子步骤 |
| 1.1 | 2026-02 | 新增Devil's Advocate评审者(第7个Agent),新增复审模式,评审团队从4人扩展至5人 |
| 1.0 | 2026-02 | 初始版本:6个Agent,4种模式,3阶段工作流 |