paper-review-committee

Orchestrate committee-style academic peer reviews for PDF, DOCX, or DOC manuscripts.

Updated May 8, 2026
One-click install
npx skills add https://github.com/super-lee-hub/fusion-reviewer --skill paper-review-committee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper-review-committee
Source: https://github.com/super-lee-hub/fusion-reviewer/tree/main/codex-skill
Command: npx skills add https://github.com/super-lee-hub/fusion-reviewer --skill paper-review-committee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It solves the problem of turning academic paper review into a consistent, evidence-grounded committee workflow that produces structured reviewer opinions and final artifacts instead of ad-hoc feedback.

Core Features & Use Cases

  • Committee-style peer review orchestration: Normalizes the manuscript once, classifies its research paradigm, and coordinates 8 reviewer perspectives (3 generalist + 5 specialist).
  • Evidence preparation and validation: Produces shared evidence bundles for downstream review (normalization, page/line indexing, diagnostics) and enforces schema/contract discipline.
  • Structured outcomes and revision-response review: Finalizes reviewer/editor JSON into stable artifacts including final report and (for revisions) a dedicated revision-response assessment.

Quick Start

Tell the host agent to run the committee review root-orchestrator workflow for your PDF/DOCX/DOC manuscript, then finalize the run after the reviewer JSON outputs exist in the generated run directory.

Frequently Asked Questions about paper-review-committee

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an academic peer review on a PDF manuscript?▼

Run an academic peer review on a PDF by instructing the host agent to execute the committee review root-orchestrator workflow, which normalizes the manuscript once and coordinates multiple reviewer perspectives to produce structured JSON artifacts.

What is a committee-style manuscript review workflow?▼

A committee-style manuscript review workflow normalizes your document, classifies its research paradigm, and coordinates eight distinct reviewer perspectives to generate evidence-grounded reviewer opinions and finalized structured JSON artifacts.

Can I use this to review revisions and compare author responses to previous concerns?▼

Yes, you can review revisions by running a dedicated revision-response review that compares previous reviewer concerns against the author responses and the revised manuscript to produce a structured assessment.

Does the structured peer review process support DOCX and DOC files?▼

Yes, the structured peer review process supports DOCX and DOC files alongside PDF manuscripts, normalizing each format to produce a shared evidence bundle with page and line indexing for downstream review.

How are reviewer opinions structured and saved during the manuscript review?▼

Reviewer opinions are structured and saved as individual structured JSON files written by leaf tasks under the <run_dir>/reviews/{agent_id}.json path, relying on a shared evidence bundle and manuscript paradigm classification.

How does the manuscript paradigm classification affect the review criteria?▼

Manuscript paradigm classification selects method-appropriate review criteria by evaluating the shared evidence bundle, ensuring the eight coordinated reviewers apply relevant standards to the specific research methodology.