respond-to-referees · git:20261106.064d774 · 2026-11-06 · sha256 cc445810b1efb89d
respond-to-referees git:20261106.064d774A
Immutable. This exact content never changes and is served at /api/v1/blob/cc445810b1efb89d.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jh72i4n5nqyqmyvo/cc445810b1efb89d50ac9d418c2a2bef29b9efa6531f8b8bbdbfea4fad687e90.json
Then /plugin install respond-to-referees@markdownregistry-jh72i4n5nqyqmyvo in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: respond-to-referees description: Generate a structured response-to-referees document from a referee report and the revised manuscript. Maps each referee comment to the specific revision, classifies coverage (addressed / partially / deferred / disagreement), and drafts polite but firm responses. Use during the R&R (revise-and-resubmit) stage of paper revision. --- <!-- Generated by scripts/sync-agent-skills.py from .claude/skills/respond-to-referees/SKILL.md. Do not edit: change the source and re-run the script. --> # respond-to-referees This skill's instructions live in [`.claude/skills/respond-to-referees/SKILL.md`](../../../.claude/skills/respond-to-referees/SKILL.md). Read that file now and follow it, with the files it points to. Read [`AGENTS.md`](../../../AGENTS.md) first if you have not already. It was written for Claude Code. Running it from Codex, Antigravity or another agent: - **Arguments.** Where it says `$ARGUMENTS`, use what the user asked for. - **Claude Code agents.** Where a step hands work to an agent in `.claude/agents/` (through the `Agent` or `Task` tool), read that agent's file and do the step yourself after the main work. Tell the user the step was not an independent review: the same agent did both. - **Claude Code settings.** `allowed-tools`, `model`, `effort`, `argument-hint` and `disable-model-invocation` in the source's frontmatter configure Claude Code. Ignore them. - **Guards.** Claude Code's guard hooks do not run for you. Follow the rules in `AGENTS.md` yourself; the git pre-commit gate and CI still apply to your commits.