skills/30-zirui-song-claude-skills/referee-response/SKILL.md
Structure responses to referee reports for R&R submissions
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research referee-responseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help structure and draft responses to referee reports. Ensures consistent formatting and comprehensive responses.
RESPONSE TO REFEREE COMMENTS
Paper: [Title]
Authors: [Names]
Journal: [Journal Name]
Manuscript #: [Number]
Date: [Date]
We thank the editor and referees for their constructive comments.
We have carefully addressed all points raised. Below we provide
point-by-point responses. Referee comments are in italics, and
our responses follow in regular text. All page and line numbers
refer to the revised manuscript.
================================================================
RESPONSE TO EDITOR
================================================================
[Editor comments and responses]
================================================================
RESPONSE TO REFEREE 1
================================================================
[Point-by-point responses]
================================================================
RESPONSE TO REFEREE 2
================================================================
[Point-by-point responses]
For each referee comment:
----------------------------------------------------------------
Comment 1.X: [Brief label for reference]
----------------------------------------------------------------
*[Paste exact referee comment in italics]*
RESPONSE:
[Your response here]
- What we did to address the comment
- Where changes appear in the manuscript (page X, lines Y-Z)
- If we added analysis, summarize the results
- If we respectfully disagree, explain why with evidence
CHANGES MADE:
- Page X: [Description of change]
- Table Y: [Description of new/modified table]
- Section Z: [Description of new text]
The referee raises an important point about [issue]. We have:
1. [Addressed concern directly]
2. Added robustness tests in Table X showing results hold when [alternative]
3. Discussed this limitation on page Y, lines Z
We appreciate this comment on identification. We address this in three ways:
1. Added [placebo test/IV/etc.] in Table X
2. Discussed the assumption more carefully in Section Y
3. Acknowledge remaining limitations on page Z
Thank you for this suggestion. We have added [analysis] in Table X / Figure Y.
The results show [brief summary]. This [strengthens/qualifies] our main findings.
We apologize for the lack of clarity. We have revised the text on page X
to clarify that [explanation]. The revised passage now reads:
"[Quote revised text]"
We appreciate this thoughtful comment. After careful consideration, we
respectfully maintain our original approach because:
1. [Reason 1 with evidence/citation]
2. [Reason 2]
However, we have added discussion of this alternative perspective on page X
and include [robustness test] in the appendix to address related concerns.
Include at the end of your response:
================================================================
SUMMARY OF MAJOR CHANGES
================================================================
1. Added Table X: [Description]
2. Added Figure Y: [Description]
3. Revised Section Z to [description]
4. Added robustness tests for [list]
5. Expanded discussion of [topic] on pages A-B
================================================================
SUPPLEMENTARY MATERIALS ADDED
================================================================
- Online Appendix Table A1: [Description]
- Online Appendix Figure A1: [Description]
- Replication package updated with [additions]
Do:
Don't:
Agreeing:
Partial agreement:
Respectful disagreement:
Acknowledging limitations:
Before submitting your response:
tools
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文(用于「文献综述工具选型」与「一键安装/运行」)。
development
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
documentation
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
tools
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.