response-to-reviewers
Write effective point-by-point responses to peer reviewer comments for revisions
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill response-to-reviewers --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Response to Reviewers Guide A skill for crafting professional, thorough responses to peer reviewer comments during manuscript revision. Covers structure, tone, strategies for handling difficult comments, and templates for common revision scenarios. ## Response Document Structure ### Standard Format ``` Dear Editor, Thank you for the opportunity to revise our manuscript entitled "[Title]" (Manusc
What does the response-to-reviewers skill do?
Write effective point-by-point responses to peer reviewer comments for revisions
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill response-to-reviewers --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.