Assist in drafting professional peer review response letters. Trigger when user mentions "reviewer comments", "response letter", "peer review", "revise and resubmit", "R&R", "reviewer feedback", or needs help responding to academic journal reviewers.
Assist researchers in crafting professional, polite, and effective responses to peer reviewer comments for academic journal submissions.
This skill parses reviewer comments, drafts structured responses, and adjusts tone to ensure:
Collect and structure the following:
Standard academic response letter format:
Dear Editor and Reviewers,
Thank you for your constructive feedback on our manuscript titled
"[Title]" submitted to [Journal]. We have carefully addressed all
comments and revised the manuscript accordingly. Below is our
point-by-point response to each reviewer's comments.
Reviewer #1:
[Numbered responses]
Reviewer #2:
[Numbered responses]
...
Sincerely,
[Authors]
For each reviewer comment, generate a response containing:
Accepting a suggestion:
Comment: The methodology section lacks detail on data preprocessing.
Response: We thank the reviewer for this important observation.
We have expanded the methodology section to include detailed
descriptions of data preprocessing steps, including normalization,
outlier removal, and feature selection procedures (Page 5, Lines 120-135).
Partial acceptance with modification:
Comment: The authors should use Method X instead of Method Y.
Response: We appreciate the reviewer's suggestion. While Method X
is indeed widely used, we found that Method Y is more appropriate
for our specific dataset due to [brief rationale]. However, we have
added a comparative discussion of both methods in the revised
manuscript (Page 8, Lines 200-210) to acknowledge this alternative
approach.
Politely declining:
Comment: The authors should remove Figure 3 as it seems redundant.
Response: We thank the reviewer for this suggestion. Upon careful
consideration, we believe Figure 3 provides essential visual
support for the key finding discussed in Section 4.2. To enhance
clarity, we have revised the figure caption to better emphasize
its unique contribution (Page 10, Figure 3 caption).
Adjust language based on context:
| Tone | Use Case | Example Phrasing |
|---|---|---|
| Diplomatic | General revisions | "We thank..." / "We appreciate..." / "We have revised..." |
| Assertive | Defending methodology | "We respectfully note..." / "Our approach is justified because..." |
| Grateful | Major improvements | "We are grateful for..." / "This significantly improved..." |
Accept multiple input formats:
Returns a complete response letter with:
User: Help me draft a response to these reviewer comments:
Reviewer 1:
1. The introduction should better motivate the problem
2. Figure 2 is unclear
3. Have you considered Smith et al. 2023?
My changes:
1. Added motivation paragraph
2. Redrew Figure 2 with clearer labels
3. Added citation and discussion
Journal: Nature Communications
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
--interactive | flag | No | - | Interactive mode: Guided wizard with prompts (uses input()). Recommended for first-time users or complex responses |
--input-file | str | No | - | Path to reviewer comments file (automation mode) |
--output | str | No | - | Output file path for response letter |
--tone | str | No | "diplomatic" | Response tone: "diplomatic", "formal", or "assertive" |
--format | str | No | "markdown" | Output format: "markdown", "plain_text", or "latex" |
--include-diff | bool | No | true | Whether to summarize changes made |
Usage Modes:
--interactive for guided setup with prompts (recommended for first-time users)--input-file with pre-prepared reviewer commentsreferences/response_templates.md - Common response patternsreferences/tone_guide.md - Academic tone guidelinesreferences/examples/ - Sample response lettersBefore finalizing, verify:
| Risk Indicator | Assessment | Level |
|---|---|---|
| Code Execution | Python/R scripts executed locally | Medium |
| Network Access | No external API calls | Low |
| File System Access | Read input files, write output files | Medium |
| Instruction Tampering | Standard prompt guidelines | Low |
| Data Exposure | Output files saved to workspace | Low |
# Python dependencies
pip install -r requirements.txt