Referee Response
- 1 installs
- 3.2k repo stars
- Updated August 4, 2026
- brycewang-stanford/awesome-agent-skills-for-empirical-research
referee-response is a Claude skill that drafts a structured point-by-point response letter to academic peer-review referee comments.
About
A skill that drafts a structured, point-by-point response letter to peer-review referee comments. It parses each referee point, reads the manuscript to ground the reply, and writes a response plus a description of the changes made with section references. A researcher uses it after a revise-and-resubmit decision to prepare the response document. It follows academic conventions such as thanking the referee and quoting each comment.
- Drafts a point-by-point response letter to referee comments
- Reads the manuscript (index.qmd) to ground each response
- Runs after a revise-and-resubmit decision
Referee Response by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,361 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
referee-response capabilities & compatibility
- Use cases
- documentation · copywriting
What referee-response says it does
Drafts a point-by-point response letter to referee comments with suggested edits. Use after a revise-and-resubmit.
Read `index.qmd` to understand the current manuscript content, structure, and arguments.
Thank the referee for constructive comment
npx skills add https://github.com/brycewang-stanford/awesome-agent-skills-for-empirical-research --skill referee-responseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 3.2k |
| Last updated | August 4, 2026 |
| Repository | brycewang-stanford/awesome-agent-skills-for-empirical-research ↗ |
What it does
Draft a point-by-point response letter to peer-review referee comments after a revise-and-resubmit.
Who is it for?
Preparing a response-to-referees letter after a revise-and-resubmit decision.
Skip if: Running the analysis or edits the referees request, which other empirical-research skills handle.
When should I use this skill?
You have received referee comments and need to draft a response letter after a revise-and-resubmit.
What you get
A structured response letter addressing each referee point with described changes and section references.
- Point-by-point response letter
- Per-point change descriptions with section references
By the numbers
- Uses a 3-part response template (Point, Response, Changes made)
Files
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
1. Read the referee comments:
- If a file path is provided, read that file
- If "paste" is specified, ask the user to paste the comments
2. Read index.qmd to understand the current manuscript content, structure, and arguments.
3. Parse the referee comments into individual points. Each point typically starts with a number, letter, or dash.
4. 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."]5. 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
6. 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]7. Save the response letter to notes/referee-response-R<N>.md where N is the revision round number (check existing files to determine the round).
8. Generate a separate list of suggested manuscript edits — specific changes to index.qmd or notebooks that address the referee's concerns. Present these to the user but do NOT apply them without explicit approval.
9. 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
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71FAQ
What does the referee-response skill do?
It drafts a structured point-by-point response to referee comments, parsing each point, grounding replies in the manuscript, and describing the changes made.
When do I use it?
After a revise-and-resubmit decision, when you need to prepare the response-to-referees document.