Agent skill

Response To Reviewers

by wentorai in wentorai/research-plugins

Write effective point-by-point responses to peer reviewer comments for revisions

MITAuto-check passedResearch & Science

Install Response To Reviewers

skills CLI
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wentorai/research-plugins response-to-reviewers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .claude/skills/response-to-reviewers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
response-to-reviewers
GitHub stars
298
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
134 words
Files
1
Skills in repo
405
Repo updated
First seen
Licence
MIT

At a glance

Write effective point-by-point responses to peer reviewer comments for revisions

  • Research & Science work in your project
  • SKILL.md covers Response Document Structure, Response Strategy Framework, Handling Difficult Situations and Cover Letter for Revision, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Response To Reviewers is an agent skill from wentorai/research-plugins. Write effective point-by-point responses to peer reviewer comments for revisions

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/response-to-reviewers”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Response To Reviewers loads about 2k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 134 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 134 words, ~2,020 tokens.

Download SKILL.mdSave it as .claude/skills/response-to-reviewers/SKILL.md (or your agent's skills folder).
name
response-to-reviewers
description
Write effective point-by-point responses to peer reviewer comments for revisions

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]"
(Manuscript ID: [ID]). We appreciate the constructive feedback from the
reviewers and have carefully addressed all comments. Below, we provide
a point-by-point response to each comment.

Major changes include:
1. [Summary of major change 1]
2. [Summary of major change 2]
3. [Summary of major change 3]

All changes in the revised manuscript are highlighted in blue.

---

REVIEWER 1

Comment 1.1: [Quote or paraphrase the reviewer's comment]

Response: [Your response]
[Reference to specific changes: "We have revised Section 3.2,
paragraph 2 (lines 145-158) to address this concern."]

Comment 1.2: ...

---

REVIEWER 2

Comment 2.1: ...

---

We believe these revisions have substantially strengthened the manuscript
and hope you find it suitable for publication in [Journal Name].

Sincerely,
[Authors]

Response Strategy Framework

python
def classify_reviewer_comment(comment: str) -> dict:
    """
    Classify a reviewer comment to determine the appropriate response strategy.

    Returns strategy recommendation for each comment type.
    """
    strategies = {
        'factual_error': {
            'description': 'Reviewer points out a genuine error',
            'strategy': 'Acknowledge, correct, and thank the reviewer',
            'template': 'We thank the reviewer for identifying this error. '
                       'We have corrected [specific change] in [location].',
            'tone': 'grateful'
        },
        'clarification_needed': {
            'description': 'Reviewer misunderstood due to unclear writing',
            'strategy': 'Rewrite the unclear section; do not blame the reviewer',
            'template': 'We appreciate this comment and recognize that our original '
                       'wording was unclear. We have revised [section] to clarify that...',
            'tone': 'constructive'
        },
        'additional_analysis': {
            'description': 'Reviewer requests new analyses or experiments',
            'strategy': 'Perform if feasible; explain limitations if not',
            'template': 'We have performed the requested analysis. [Results]. '
                       'These results are now presented in [Figure/Table X].',
            'tone': 'responsive'
        },
        'methodological_concern': {
            'description': 'Reviewer questions methodology',
            'strategy': 'Provide justification with references; add robustness checks',
            'template': 'This is an excellent point. Our methodological choice was based on '
                       '[rationale + citation]. As a robustness check, we have also...',
            'tone': 'scholarly'
        },
        'scope_expansion': {
            'description': 'Reviewer asks to expand beyond paper scope',
            'strategy': 'Acknowledge value; explain scope boundaries respectfully',
            'template': 'We agree this is an interesting direction. However, this analysis '
                       'is beyond the scope of the current study because [reason]. '
                       'We have added this as a direction for future research in the Discussion.',
            'tone': 'respectful_boundary'
        },
        'disagreement': {
            'description': 'You disagree with the reviewer substantively',
            'strategy': 'Present evidence-based counter-argument respectfully',
            'template': 'We appreciate this perspective. After careful consideration, '
                       'we respectfully maintain our original interpretation because [evidence]. '
                       'However, we have added a discussion of this alternative view in [section].',
            'tone': 'diplomatic'
        }
    }

    # Simple keyword-based classification
    comment_lower = comment.lower()
    if any(w in comment_lower for w in ['error', 'mistake', 'incorrect', 'wrong']):
        return strategies['factual_error']
    elif any(w in comment_lower for w in ['unclear', 'confusing', 'what do you mean']):
        return strategies['clarification_needed']
    elif any(w in comment_lower for w in ['additional', 'also analyze', 'please include']):
        return strategies['additional_analysis']
    elif any(w in comment_lower for w in ['method', 'approach', 'why did you']):
        return strategies['methodological_concern']
    elif any(w in comment_lower for w in ['beyond', 'also consider', 'broader']):
        return strategies['scope_expansion']
    else:
        return strategies['clarification_needed']  # default safe strategy

Handling Difficult Situations

When You Disagree with a Reviewer

Never dismiss a reviewer's concern outright. The formula:

1. Acknowledge the reviewer's point
   "We appreciate this thoughtful observation."

2. Present your reasoning with evidence
   "Our approach is supported by [Author, Year] who demonstrated..."

3. Show you have considered the alternative
   "We have added a paragraph discussing this alternative interpretation
    (Section 4.3, lines 312-325)."

4. Offer a compromise when possible
   "As a compromise, we have added a sensitivity analysis using the
    reviewer's suggested approach, which yields consistent results
    (Supplementary Table S3)."
When a Requested Analysis is Infeasible
Structure:
1. Explain why it cannot be done
   "Unfortunately, [specific reason] prevents us from performing this
    analysis. [Data was not collected / sample size is insufficient /
    IRB protocol does not cover this]."

2. Offer the closest feasible alternative
   "As an alternative, we have conducted [alternative analysis],
    which addresses the same underlying concern."

3. Acknowledge the limitation
   "We have added this as a limitation in Section 5.2."

Cover Letter for Revision

python
def generate_cover_letter(journal: str, manuscript_id: str, title: str,
                           major_changes: list[str],
                           editor_name: str = "Editor") -> str:
    """Generate a revision cover letter template."""
    changes_list = '\n'.join(f'  {i+1}. {c}' for i, c in enumerate(major_changes))

    return f"""Dear {editor_name},

We are pleased to submit our revised manuscript entitled "{title}"
(Manuscript ID: {manuscript_id}) for consideration in {journal}.

We thank you and the reviewers for the constructive and insightful
comments, which have significantly improved the quality of our work.
We have carefully addressed all reviewer comments in the attached
point-by-point response document.

The major revisions include:
{changes_list}

All changes are highlighted in blue in the revised manuscript.
A clean version is also provided.

We believe the revised manuscript now fully addresses the reviewers'
concerns and is suitable for publication in {journal}.

Sincerely,
[Corresponding Author Name]
[Affiliation]
[Email]"""

Revision Tracking Best Practices

  • Use track changes or highlight all modified text in the revised manuscript
  • Provide both a marked-up version and a clean version
  • Reference specific line numbers, figure numbers, or section numbers
  • If the revision substantially changes a figure or table, include the old and new versions side by side in the response document
  • Submit the revision within the editor's requested timeline (typically 30-90 days)

© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/writing/composition/response-to-reviewers of wentorai/research-plugins.

Open the folder on GitHubat commit bf44b3c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Response To Reviewers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Response To Reviewers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Response To Reviewers this skillwentorai/research-plugins2981 repos~2kAutomated safety check: PassMIT
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from wentorai/research-plugins

All 405 skills in this repo
  • Abstract Writing Guide

    wentorai/research-plugins

    Craft structured research abstracts that maximize clarity and journal acceptance

    298 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Academic Citation Manager

    wentorai/research-plugins

    Manage academic citations across BibTeX, APA, MLA, and Chicago formats

    298 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Academic Paper Summarizer

    wentorai/research-plugins

    Summarize academic papers with structured extraction of key elements

    298 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Academic Study Methods

    wentorai/research-plugins

    Evidence-based study techniques for academic learning and retention

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Academic Tone Guide

    wentorai/research-plugins

    Adjust writing tone and register for academic audiences and venues

    298 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Academic Translation Guide

    wentorai/research-plugins

    Academic translation, post-editing, and Chinglish correction guide

    298 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Questions about Response To Reviewers

What does Response To Reviewers do?

Write effective point-by-point responses to peer reviewer comments for revisions. Response To Reviewers is an agent skill from wentorai/research-plugins.

When should I use Response To Reviewers?

Response To Reviewers fits situations like: research & Science work in your project.

How do I install Response To Reviewers in Claude Code?

Run `npx skills add wentorai/research-plugins --skill response-to-reviewers -a claude-code`. Or copy the skill folder (skills/writing/composition/response-to-reviewers in wentorai/research-plugins) into .claude/skills/response-to-reviewers in your project. Claude Code loads it when a task matches its description.

How do I install Response To Reviewers in Codex?

Run `npx skills add wentorai/research-plugins --skill response-to-reviewers -a codex`. Or copy the skill folder (skills/writing/composition/response-to-reviewers in wentorai/research-plugins) into .agents/skills/response-to-reviewers in your project. Codex loads it when a task matches its description.

Can I use Response To Reviewers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wentorai/research-plugins --skill response-to-reviewers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/response-to-reviewers, .gemini/skills/response-to-reviewers, .github/skills/response-to-reviewers and .opencode/skills/response-to-reviewers in your project.

What does Response To Reviewers need to run?

SKILL.md names no scripts, command-line tools or credentials: Response To Reviewers is instructions for the agent only. Our summary lists: Python 3.

Does Response To Reviewers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Response To Reviewers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Response To Reviewers use?

Response To Reviewers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Response To Reviewers use?

About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Response To Reviewers?

Skills that share tags, products or a category with Response To Reviewers: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Response To Reviewers?

wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 405 skills in this directory. The repository was last updated on June 19, 2026.

Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.