Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Craft effective point-by-point reviewer response letters. An agent skill from wentorai/research-plugins.
$ npx skills add wentorai/research-plugins --skill review-response-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins review-response-guide --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/research/paper-review/review-response-guide .claude/skills/review-response-guide && 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 "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .claude/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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/research/paper-review/review-response-guideType 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 review-response-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins review-response-guide --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/research/paper-review/review-response-guide .agents/skills/review-response-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .agents/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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 review-response-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins review-response-guide --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/research/paper-review/review-response-guide .cursor/skills/review-response-guide && 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 "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .cursor/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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/research/paper-review/review-response-guide--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 review-response-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins review-response-guide --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/research/paper-review/review-response-guide .gemini/skills/review-response-guide && 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 "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .gemini/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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 review-response-guideInstalls 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 review-response-guide -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/research/paper-review/review-response-guide .github/skills/review-response-guide && 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 "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .github/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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 review-response-guide -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 review-response-guide --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/research/paper-review/review-response-guide .opencode/skills/review-response-guide && 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 "review-response-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/research/paper-review/review-response-guide into .opencode/skills/review-response-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-response-guide", 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.
review-response-guideCraft effective point-by-point reviewer response letters. An agent skill from wentorai/research-plugins.
Review Response Guide is an agent skill from wentorai/research-plugins. Craft effective point-by-point reviewer response letters
Its SKILL.md is about 2.4k 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, covering Peer review. 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.
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.
Review Response Guide loads about 2.4k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 160 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). 160 words, ~2,385 tokens.
.claude/skills/review-response-guide/SKILL.md (or your agent's skills folder).A skill for crafting effective, professional point-by-point response letters to peer reviewer comments. Covers response letter structure, strategies for different types of reviewer feedback, prioritization of revisions, managing conflicting reviewer opinions, and navigating the revision-resubmission cycle to maximize acceptance probability.
A well-organized response letter follows a consistent structure that makes it easy for editors and reviewers to verify that all concerns have been addressed.
Response Letter Structure:
1. COVER LETTER TO EDITOR (1 page max)
- Thank the editor and reviewers
- Summarize the 3-5 most significant changes
- Highlight any points where you respectfully disagree
- Note if conflicting reviewer requests required a judgment call
- State that all changes are marked in the revised manuscript
2. SUMMARY OF CHANGES (optional but recommended)
- Bulleted list of all major changes
- Brief enough to read in 2 minutes
- Organized by theme, not by reviewer
3. POINT-BY-POINT RESPONSES
For each reviewer, for each comment:
---
REVIEWER [N], Comment [M]:
[Quote the reviewer's comment verbatim, italicized]
RESPONSE:
[Your substantive response]
CHANGES MADE:
[Exact description of what changed, with page/line numbers
or quoted text from the revised manuscript]
---
4. ADDITIONAL CHANGES (if any)
- Changes you made that were not requested by reviewers
- Example: "We also updated Figure 3 to use colorblind-
friendly colors throughout."Visual formatting for clarity:
1. Use consistent fonts:
- Reviewer comments: italic
- Your responses: regular weight
- Changes made: indented or in a different color
2. Numbering system:
- R1.1, R1.2, R1.3 for Reviewer 1's comments
- R2.1, R2.2 for Reviewer 2's comments
- Major comments first, then minor comments
3. Cross-references:
- When one response addresses multiple comments:
"See our response to R1.3 above, which also addresses
this concern."
- When changes span multiple sections:
"See revised manuscript, pp. 8-9, paragraphs 2-3
(marked in blue)."
4. Length calibration:
- Major comments: 100-300 words per response
- Minor comments: 20-50 words per response
- Total response letter: typically 5-20 pages
- Longer is fine if substantive; never pad with fluffWhen reviewers question your methodology:
Scenario: "The sample size is too small for the claims made."
Strong response structure:
1. Acknowledge the concern explicitly
2. Provide quantitative justification (power analysis)
3. Add additional analysis if possible
4. Acknowledge remaining limitations honestly
Example:
"We appreciate this important concern about statistical power.
We have now added a formal power analysis (Supplementary
Section S2) showing that our sample of N=120 provides 82%
power to detect the medium effect size (d=0.5) that our
hypotheses predicted, based on prior work by Chen et al.
(2021). Our observed effects were larger than this threshold
(d=0.72, 95% CI [0.41, 1.03]). We have also added a
sensitivity analysis (new Table S3) confirming that results
are robust to different analytical choices. We acknowledge
the power limitation for detecting small effects and have
added this to the Limitations section (p. 18, lines 4-8)."When reviewers ask for more analysis:
If feasible - do it:
"We thank the reviewer for this excellent suggestion.
We have conducted the requested analysis and present
the results in new Table 4 (p. 12). The findings are
consistent with our main results, strengthening our
conclusions."
If partially feasible - do what you can:
"We have conducted [part A] of the suggested analysis
(new Figure S5). Unfortunately, [part B] is not possible
with our current dataset because [specific reason].
We have added this as a direction for future research
(p. 19, line 12)."
If not feasible - explain clearly:
"This analysis would require [data/resource] that is not
available in our study because [reason]. However, we have
conducted [alternative analysis] that addresses the
underlying concern. We also now discuss this limitation
explicitly (p. 17)."When Reviewer 1 and Reviewer 2 disagree:
This happens frequently. The key is to:
1. Acknowledge both perspectives
2. Explain your reasoning transparently
3. Ask the editor to adjudicate if needed
Example:
"Reviewer 1 suggests removing the qualitative analysis
(R1.4), while Reviewer 2 asks us to expand it (R2.7).
We believe the qualitative component adds important
context to our quantitative findings, consistent with
mixed-methods best practices (Creswell, 2018). We have
therefore retained the qualitative analysis but tightened
it from 4 pages to 2 pages, focusing on the most
illustrative quotes. We respectfully ask the editor to
advise if further adjustment is needed."
In the cover letter:
"We note a point of divergence between Reviewers 1 and 2
regarding the qualitative analysis (R1.4 vs R2.7). We have
described our proposed compromise in the detailed responses
and welcome the editor's guidance on this matter."Strategy: Correct respectfully, blame your own writing
Never: "The reviewer is incorrect about..."
Never: "The reviewer failed to understand..."
Never: "As any expert in this field would know..."
Instead:
"We appreciate this comment, which indicates that our
description of [topic] was not sufficiently clear. We have
rewritten Section 3.2 (pp. 9-10) to clarify that [correct
information]. The key point, which we now state explicitly
in the second paragraph, is that [clarification]. We hope
the revised text prevents this misunderstanding."
Why this works:
- Acknowledges the reviewer's effort
- Takes responsibility for the miscommunication
- Improves the paper for future readers who might have
the same misunderstanding
- Corrects the record without antagonizing the reviewerStrategy: Maintain professionalism, address substance
If a comment is dismissive without substance:
Reviewer: "This paper is not interesting."
Response: "We have revised the Introduction to more
clearly articulate the significance of our research
question and its implications for [field]. Specifically,
we now explain [relevance point 1], [relevance point 2],
and [relevance point 3] (pp. 2-3)."
If a comment reveals the reviewer did not read the paper:
Reviewer: "The authors did not control for age."
Response: "We appreciate this concern. Age was included
as a covariate in all models, as described in Section 3.4
(p. 11, line 3) and reported in Table 2, Column 3. We have
added bold formatting to make this control variable more
visible in the table."
If appropriate, raise concerns with the editor:
In the cover letter (not the response):
"We note that Comment R2.5 appears to request an analysis
that is already reported in Table 4 of our manuscript.
We welcome the editor's assessment of whether our response
adequately addresses this concern."Step-by-step revision workflow:
1. Cooling-off period (1-2 days):
Read reviews once, then set them aside.
Initial emotional reactions are normal.
2. Comment triage (1 day):
Create a spreadsheet with columns:
- Reviewer, Comment number, Category, Difficulty, Action
Categories: major/minor, methodological/theoretical/editorial
Difficulty: easy/medium/hard
3. Easy wins first (1-2 days):
Address minor comments: typos, formatting, missing references
These require minimal thought and build momentum
4. Hard problems (1-2 weeks):
Address major methodological and theoretical concerns
Run additional analyses
Rewrite substantial sections
Consult co-authors on strategy
5. Response letter drafting (2-3 days):
Write point-by-point responses
Include specific page/line numbers for all changes
6. Co-author review (3-5 days):
All co-authors review the revised manuscript AND the
response letter before resubmission
7. Final checks (1 day):
Verify all page/line numbers are correct
Check that tracked changes match response descriptions
Ensure formatting meets journal requirements
Timeline: Allow 4-8 weeks for a major revision
Deadline: Most journals give 60-90 days; request extension
if needed (editors almost always grant it)A well-crafted response letter demonstrates intellectual maturity, thoroughness, and respect for the peer review process. The strongest response letters share a common trait: they treat every reviewer comment as an opportunity to improve the paper, even when the reviewer is wrong, because the revision process ultimately serves the reader.
© 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/research/paper-review/review-response-guide 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.
Review Response Guide 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 |
|---|---|---|---|---|---|---|
| Review Response Guide this skillwentorai/research-plugins | 298 | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
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
Craft effective point-by-point reviewer response letters. An agent skill from wentorai/research-plugins. Review Response Guide is an agent skill from wentorai/research-plugins.
Review Response Guide fits situations like: tasks that involve Peer review.
Run `npx skills add wentorai/research-plugins --skill review-response-guide -a claude-code`. Or copy the skill folder (skills/research/paper-review/review-response-guide in wentorai/research-plugins) into .claude/skills/review-response-guide in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wentorai/research-plugins --skill review-response-guide -a codex`. Or copy the skill folder (skills/research/paper-review/review-response-guide in wentorai/research-plugins) into .agents/skills/review-response-guide 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 review-response-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-response-guide, .gemini/skills/review-response-guide, .github/skills/review-response-guide and .opencode/skills/review-response-guide in your project.
SKILL.md names no scripts, command-line tools or credentials: Review Response Guide is instructions for the agent only.
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.
Review Response Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.5k 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 Review Response Guide: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k 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.