gpd-peer-review

Conducts a staged six-pass peer review of a manuscript and its research artifacts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-peer-review-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-peer-review
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-peer-review
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-peer-review-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-pass manuscript reviews tend to be overly charitable, missing weak physical interpretation, thin novelty, or unsupported significance claims. This Skill replaces that with a staged, evidence-aware referee panel that fails closed on unsupported scientific claims. ## Core Features & Use Cases - Six-stage review panel: Runs a full-manuscript reader, literature reviewer, mathematical-soundness reviewer, physical-soundness reviewer, significance reviewer, and a final adjudicating referee, each in a fresh context with compact JSON stage artifacts. - Strict preflight and evidence contracts: Validates project state, manuscript presence, artifact manifests, bibliography audits, and reproducibility manifests before reviewing, and blocks on missing review-grade evidence. - Revision round handling: Detects prior referee reports and author responses to run R2/R3 rounds with suffixed artifacts, then routes the outcome to respond-to-referees, manuscript edits, or arxiv submission. - Use Case: After drafting a physics paper in a GPD project, run the review to get a claim index, per-stage concern reports, a validated referee decision, and a LaTeX/Markdown referee report with an accept/revise/reject recommendation. ## Quick Start Ask the agent to peer review the manuscript in the paper directory of the current GPD project.

Frequently Asked Questions about gpd-peer-review

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

FAQPage Schema
How do I run a peer review on my manuscript with this skill?▼

Invoke the skill with an optional paper directory or manuscript path as the argument. If no argument is given, it searches paper/main.tex, manuscript/main.tex, and draft/main.tex in order, then runs preflight checks before spawning the review panel.

What artifacts does the staged peer review produce?▼

It writes a claim index, five stage review JSON files, a review ledger, and a referee decision JSON under .gpd/review/, plus REFEREE-REPORT.md and REFEREE-REPORT.tex in .gpd/. A consistency report and optional compiled PDF are also produced when supported.

What inputs are required before the review can start?▼

Strict preflight requires project state, a roadmap, conventions, a manuscript, and review-grade artifacts including ARTIFACT-MANIFEST.json, BIBLIOGRAPHY-AUDIT.json, and a reproducibility manifest. Missing items block the review and are reported to the user.

How does the skill handle revision rounds after author responses?▼

It detects existing REFEREE-REPORT and AUTHOR-RESPONSE files to set the round number, then writes round-suffixed artifacts such as STAGE-reader-R2.json. The final referee reads prior reports and responses to judge whether earlier concerns are resolved.

What happens if a review stage or the referee agent fails?▼

The workflow stops immediately and reports the failure rather than skipping stages. Later stages depend on earlier artifacts like the claim map, and final adjudication is never silently omitted.