brycewang-stanford/Auto-Empirical-Research-Skills / skills/29-quarcs-lab-project20XXy/dot-claude/skills/referee-response
referee-response
VerifiedDrafts a point-by-point response letter to referee comments with suggested edits. Use after a revise-and-resubmit.
Draft Referee Response
Draft a structured point-by-point response to referee comments.
Arguments
$ARGUMENTS— path to a file containing referee comments (e.g.,notes/referee-report-R1.txt), or the word "paste" to accept inline input
Steps
-
Read the referee comments:
- If a file path is provided, read that file
- If "paste" is specified, ask the user to paste the comments
-
Read
index.qmdto understand the current manuscript content, structure, and arguments. -
Parse the referee comments into individual points. Each point typically starts with a number, letter, or dash.
-
For each referee point, draft a structured response:
**Point N:** [Quote or paraphrase the referee's comment] **Response:** [Address the comment — acknowledge the concern, explain what was done or why you disagree, provide additional evidence or reasoning] **Changes made:** [Describe specific edits with section references, e.g., "We have added two paragraphs to Section 3 (@sec-data) clarifying the sample selection."] -
Use appropriate response conventions:
- Thank the referee for constructive comments
- Be respectful even when disagreeing
- Distinguish between changes made and changes not made (with justification)
- Reference specific sections, tables, and figures in the manuscript
- If a comment requires new analysis, note what was done and where results appear
-
Organize the response by referee:
# Response to Referee Comments ## Referee 1 [Point-by-point responses] ## Referee 2 [Point-by-point responses] ## Editor [Point-by-point responses] -
Save the response letter to
notes/referee-response-R<N>.mdwhere N is the revision round number (check existing files to determine the round). -
Generate a separate list of suggested manuscript edits — specific changes to
index.qmdor notebooks that address the referee's concerns. Present these to the user but do NOT apply them without explicit approval. -
Report the response letter file path and the list of suggested edits.
Error handling
- If the comments file does not exist, ask for the correct path.
- If the comments are too brief or ambiguous to parse into individual points, present them as-is and ask the user to help segment them.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |