Claude Skill

respond-to-referees

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&

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download pedrohcgs-claude-code-my-workflow-.agents_skills_respond-to-referees-fe70774.zip · 1 KB

Install

skills CLI npx skills add https://github.com/pedrohcgs/claude-code-my-workflow/tree/main/.agents/skills/respond-to-referees
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pedrohcgs-claude-code-my-workflow@llmmart
Git git clone https://github.com/pedrohcgs/claude-code-my-workflow.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pedrohcgs/claude-code-my-workflow collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

respond-to-referees

This skill's instructions live in .claude/skills/respond-to-referees/SKILL.md. Read that file now and follow it, with the files it points to. Read 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), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (/commit runs its verifier before it commits). Read the agent's file for what the step checks.
  • Fresh context. If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced not independently verified, and tell the user to repeat that check in Claude Code (/verify-claims for citations) before relying on it.
  • 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.
Files (claude-code-my-workflow)
  • SKILL.md 2.1 KB
    ---
    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), do that step where it appears in the procedure: never later, and never
      skip it. A step that gates what follows still gates it (`/commit` runs its verifier before it
      commits). Read the agent's file for what the step checks.
    - **Fresh context.** If the step needs a context that has not seen your work, for example a claim
      verifier that must never see the draft, run it in a separate session or worker that has not
      seen the draft, if your tool can start one, and give it only what the step says to pass. If it
      cannot, do the step yourself, mark every result it produced *not independently verified*, and
      tell the user to repeat that check in Claude Code (`/verify-claims` for citations) before
      relying on it.
    - **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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.