referee-responselisted

Organizes and formats an author's response to peer review — extracts every distinct point from the referee reports and the editor's letter, tags severity and type, maps the dependencies so the revision runs in the right order, flags which points the author may want to push back on, and builds the response-to-reviewers letter as a numbered comment → response → location table with the substantive answers left for the author to write. It formats and checks the response; it never writes the scientific content of an answer. Use when the user has referee or reviewer reports, a revise-and-resubmit decision, or an editor's letter and says "respond to reviewers", "plan the revision", "map the referee comments", "draft the response letter", or "check I addressed everything". The reviewer-side twin is journal-review; prose polish afterwards goes to sci-edit.
scdenney/open-science-skills · ★ 57 · Code & Development · score 77

Install: claude install-skill scdenney/open-science-skills

# Referee Response Turns scattered reviewer comments into an ordered revision plan and a response letter the author fills in. The author writes every substantive answer; this skill makes sure each point is found, ordered, answered somewhere, and formatted the way editors expect. **Related skills.** `$journal-review` writes a referee report for someone else's manuscript; this skill answers one written about yours. `$sci-edit` polishes the letter's prose after the author has written the answers. `$paper-review-lite` and `$citation-check` are useful before resubmission when a referee's point implies the manuscript needs a fresh audit. ## Inputs One or more referee reports, the editor's decision letter if available, and the manuscript (current draft, and the submitted version if the two differ). If a report is a PDF or Word file, read it with `$doc-to-markdown` first. Ask once for anything missing that the steps below need; do not guess at a report's content. ## Modes Infer from the request; an argument forces it. - `plan` (default when no letter exists yet): steps 1–3. - `letter`: steps 1–4, producing the letter skeleton. - `check`: step 5 over a letter the author has filled in. ## Step 1 — Extract every point List every distinct request, criticism, or question across all reports and the editor's letter. One row per point, even when a referee bundles several into one paragraph. For each point record: - referee (R1, R2, editor), and the location in the report; - the poi