AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Peer Review Response

skill-muhammad1438-academic-writer-skills-peer-review-response · by muhammad1438

Write professional, effective responses to peer reviewer comments for journal manuscript revisions. Use this skill whenever the user needs to write a rebuttal letter, respond to reviewer comments, prepare a revised manuscript submission, handle contradictory reviewer requests, or understand how to appeal a journal decision. Trigger for: "help me respond to reviewers," "write my rebuttal letter,"…

No reviews yet
0 installs
37 views
0.0% view→install

Install

$ agentstack add skill-muhammad1438-academic-writer-skills-peer-review-response

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-muhammad1438-academic-writer-skills-peer-review-response)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Peer Review Response? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Peer Review Response

The peer review response is one of the most high-stakes documents in academic publishing. A poorly written rebuttal can cause editors to reject a paper that might have been accepted. A masterful response can rescue a paper from rejection.


Understanding the Editor's Decision Letter

Decision Types and What They Mean

| Decision | What It Means | Typical Revision Scope | |---|---|---| | Accept | Rare on first submission; paper is accepted as-is | Minor typographical corrections only | | Minor Revision | Accept in principle; small changes needed | 1–2 weeks; targeted fixes | | Major Revision | Accept possible if concerns are adequately addressed | 1–3 months; possibly new analyses | | Reject with Invitation to Resubmit | The paper needs fundamental reworking | Major restructuring; treated as new submission | | Reject | Paper is not suitable for this journal | Consider a different journal |

Reading the Decision Letter Strategically

  1. Read the editor's letter first, not the reviews — The editor often summarises the key issues
  2. Identify which concerns the editor highlights — These carry more weight than reviewer-only concerns
  3. Rank the reviewer comments — Distinguish mandatory changes from suggestions
  4. Check the deadline — Most journals give 30–60 days for major revisions; request an extension if needed

Rebuttal Letter Structure

Standard Format

Part 1: Cover Letter to the Editor

> Dear [Editor Name], > > We thank you and the reviewers for the careful and constructive review of our manuscript entitled "[Title]" (Manuscript ID: [ID]). We have carefully considered all comments and have made substantial revisions to the manuscript. We believe the revised manuscript is significantly improved and we hope it is now suitable for publication in [Journal Name]. > > Below, we provide a detailed point-by-point response to each reviewer's comment. All changes in the revised manuscript are indicated in [red text / tracked changes / a separate document]. > > We remain available to answer any further questions. > > Sincerely, > [Corresponding Author]

Part 2: Point-by-Point Responses

Organise responses under clearly labelled headers:

REVIEWER 1

Comment 1:
[Quote the reviewer's comment verbatim]

Response:
[Your response]

Manuscript Change:
[State exactly what was changed and where: "Lines 145–152 in the revised manuscript now read: '...'"]

The Point-by-Point Response Template

For every reviewer comment, use this three-part structure:

Part 1: Acknowledgement

Begin by acknowledging the reviewer's point — even if you disagree with it. > "We thank the reviewer for this insightful comment." > "We appreciate the reviewer raising this important issue." > "We agree with the reviewer that this point required clarification."

Part 2: Action Taken / Your Response

Explain what you did (or why you respectfully disagree). > "In response, we have [added a new analysis / revised the Methods section / added Figure X / added a paragraph on page Y]." > "We respectfully disagree with this interpretation because [reason with evidence]."

Part 3: Manuscript Change

State precisely where the change appears in the revised manuscript. > "The revised manuscript now reads (lines 145–152): '[exact new text]'" > "Table 3 has been added to address this concern, showing [description]."


The Professional Tone Principle

Never argue, always acknowledge. The goal is not to win a debate — it is to address the reviewer's underlying concern, even if you believe they are wrong.

When the Reviewer is Right

Simply agree, thank them, and describe the change: > "The reviewer is correct. We have revised the Discussion accordingly (lines 312–318)."

When the Reviewer is Partially Right

Acknowledge the valid element, address what you disagree with respectfully: > "We appreciate the reviewer's concern regarding the sample size. We agree that a larger sample would strengthen the study, and we have added this as a limitation (lines 389–392). However, we note that our sample size was calculated a priori using a power analysis targeting 80% power (Methods, lines 89–95), and is consistent with comparable published studies [cite 2–3]."

When the Reviewer is Wrong

Disagree diplomatically with evidence, never with irritation: > "We respectfully disagree with the reviewer's characterisation of our analysis as [X]. Our approach follows the procedure described by [Author, Year], which is the standard method for [Y]. We have added a sentence clarifying this rationale (line 201)."

Avoid:

  • "As we clearly stated in the original manuscript..." (condescending)
  • "The reviewer has misunderstood..." (hostile)
  • "This comment is outside the scope of our paper..." (dismissive without explanation)

Handling Specific Challenging Situations

Contradictory Reviewer Requests

When two reviewers ask for opposite things: > "Reviewer 1 suggested [X], while Reviewer 2 suggested [Y]. After careful consideration, we have [chosen approach Z / adopted a compromise]. We have [added a paragraph / revised the methods] to address both concerns, as detailed below."

Always explain your reasoning. Do not simply ignore one reviewer.

Requests for New Experiments You Cannot Perform

Be transparent about constraints: > "We appreciate the reviewer's suggestion to conduct [X experiment]. This would indeed provide additional validation. However, this experiment falls outside the scope of the current study and our current facilities/timeline/ethics approval. We have added this as a direction for future research (Discussion, lines 398–401) and have acknowledged this as a limitation (lines 419–422)."

Requests That Would Fundamentally Change the Paper

Acknowledge the value of the suggestion while defending your scope: > "The reviewer's suggestion to expand the analysis to include [Y population] is scientifically interesting. However, this would substantially alter the scope and focus of the paper. We believe the current focus on [X] is a strength of the paper, as it allows us to... We have clarified the scope and its rationale in the Introduction (lines 34–38)."


Common Response Phrases

Acknowledging

  • "We thank the reviewer for this valuable comment."
  • "We agree with the reviewer that this point needed clarification."
  • "The reviewer raises an important concern that we have addressed."
  • "This is an insightful observation."

Agreeing and Changing

  • "In response to this comment, we have..."
  • "We have revised [section] to address this concern."
  • "Following the reviewer's suggestion, we have added..."
  • "We have rewritten [paragraph] to clarify this point."

Disagreeing Diplomatically

  • "We respectfully disagree with this interpretation."
  • "While we appreciate this suggestion, we believe that..."
  • "We note that [counter-evidence]."
  • "With respect, we believe this concern is addressed by..."

Offering Compromise

  • "As a compromise, we have..."
  • "We have added [X] to partially address this concern while maintaining our original approach because..."

Tracking Changes Across Revisions

Best Practices

  • Use tracked changes or red text in the revised manuscript so reviewers and editors can quickly find changes
  • Number all changes in your response letter and cross-reference to manuscript line numbers
  • Do not change line numbers after writing your response — submit the tracked-changes version first to get final line numbers, then update your response letter

Version Management Checklist

  • [ ] Revised manuscript with all changes tracked or highlighted
  • [ ] Clean version of revised manuscript (no tracking)
  • [ ] Point-by-point response letter
  • [ ] Cover letter to editor
  • [ ] Any supplementary materials added in revision

The Appeals Process

When to Appeal a Rejection

Grounds for appeal:

  • Factual error: The reviewer made a clear factual mistake that materially affected their recommendation
  • Misunderstanding: The reviewer fundamentally misunderstood the purpose or methods of the paper
  • Inappropriate reviewer expertise: The reviewer lacked the necessary expertise to evaluate your work

Do not appeal because: you believe the reviewer was too critical, or the standard you think the paper meets is higher than the rejection implies.

How to Write an Appeal

> "We respectfully appeal the decision to reject manuscript [ID]. We believe the decision was based on a factual misunderstanding in Reviewer 2's assessment. Specifically, Reviewer 2 states [quote], which we respectfully note is incorrect because [specific factual correction with evidence/citation]. We believe that, if this point is reconsidered, the manuscript meets the standards of [Journal]. We would be grateful if the editor would reconsider the manuscript in light of this clarification."


Resubmission Checklist

Before submitting the revised manuscript:

  • [ ] Every reviewer comment has been addressed (even if the response is to disagree)
  • [ ] All changes are traceable (line numbers, tracked changes, or highlighted text)
  • [ ] The response letter is professionally toned throughout
  • [ ] The cover letter thanks the editor and summarises the key revisions
  • [ ] All new references cited in the response are also added to the reference list
  • [ ] No new errors have been introduced by the revisions
  • [ ] Word count and format still comply with journal guidelines
  • [ ] The response letter is not so long it becomes burdensome (aim for concision)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.