gpd-respond-to-referees

Structure point-by-point responses to referee reports and revise LaTeX manuscripts accordingly.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Responding to journal referee reports requires parsing every comment, triaging by priority, coordinating manuscript edits, and producing a formal response letter. This Skill automates that entire revision pipeline so no referee point is missed and the manuscript stays consistent. ## Core Features & Use Cases - Referee Report Parsing & Triage: Extracts and categorizes each referee comment by type (physics concern, clarity, missing reference, new calculation) and priority (must address, should address, optional), including editor decision context from staged review ledgers. - Coordinated Manuscript Revision: Groups revision items by affected LaTeX section and delegates targeted edits to paper-writer subagents, with revision markers, compilation checks, and a bounded 3-iteration consistency loop. - Dual Response Artifacts: Produces both an internal author-response tracker (.gpd/AUTHOR-RESPONSE.md) and a journal-facing response letter (.gpd/paper/REFEREE_RESPONSE.md plus paper/response-letter.tex), kept synchronized and committed. - Use Case: After receiving a major-revision decision with two referee reports on a physics manuscript, run this Skill to parse the reports, apply section edits, route requested new calculations into research phases, and generate the resubmission response letter. ## Quick Start Ask the AI to respond to the referee report at the given file path and revise the manuscript in the paper directory accordingly.

Frequently Asked Questions about gpd-respond-to-referees

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

FAQPage Schema
How do I write a point-by-point response to referee reports?▼

Provide the referee report as a file path or pasted text. The Skill parses each comment, categorizes it by type and priority, drafts responses, applies manuscript revisions, and generates both an internal tracker and a journal-facing response letter.

How to revise a LaTeX manuscript after peer review comments?▼

Comments are triaged into response-only, manuscript-revision, and new-calculation groups. Revision items are grouped by affected section and delegated to paper-writer agents that make targeted edits marked with REVISED LaTeX comments, followed by compilation and consistency checks.

What files does the referee response workflow require?▼

It requires an existing manuscript with main.tex under paper/, manuscript/, or draft/, plus GPD project state. Staged peer-review artifacts like REVIEW-LEDGER.json and REFEREE-DECISION.json under .gpd/review/ are consumed as decision context when available.

Can referee-requested new calculations be handled during revision?▼

Yes. Comments requiring new derivations, comparisons, or numerical checks are classified as Group C and routed into new research phases. The response letter notes them as work in progress until those phases are executed and results incorporated.

What happens if the revised manuscript fails to compile?▼

The workflow runs pdflatex and bibtex after revisions and fixes compilation errors directly. Consistency issues trigger a bounded revision loop of at most 3 iterations; unresolved issues are reported with options to proceed or fix manually.