Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Write effective point-by-point responses to peer reviewer comments for revisions
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins response-to-reviewers --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .claude/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewersType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins response-to-reviewers --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .agents/skills/response-to-reviewers && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .agents/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins response-to-reviewers --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .cursor/skills/response-to-reviewers && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .cursor/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wentorai/research-plugins.git --path skills/writing/composition/response-to-reviewers--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins response-to-reviewers --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .gemini/skills/response-to-reviewers && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .gemini/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wentorai/research-plugins response-to-reviewersInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .github/skills/response-to-reviewers && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .github/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill response-to-reviewers -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins response-to-reviewers --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing/composition/response-to-reviewers .opencode/skills/response-to-reviewers && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "response-to-reviewers" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/response-to-reviewers into .opencode/skills/response-to-reviewers/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "response-to-reviewers", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
response-to-reviewersWrite effective point-by-point responses to peer reviewer comments for revisions
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.
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 134 words, ~2,020 tokens.
.claude/skills/response-to-reviewers/SKILL.md (or your agent's skills folder).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.
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]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 strategyNever 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)."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."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]"""© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/writing/composition/response-to-reviewers of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Response To Reviewers this skillwentorai/research-plugins | 298 | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
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.
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.
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.
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
wentorai/research-plugins
Adjust writing tone and register for academic audiences and venues
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
Categories
Write effective point-by-point responses to peer reviewer comments for revisions. Response To Reviewers is an agent skill from wentorai/research-plugins.
Response To Reviewers fits situations like: research & Science work in your project.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Response To Reviewers is instructions for the agent only. Our summary lists: Python 3.
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.
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.
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.
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.
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.
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.