# Write professional peer-review response letters

Academic researchers struggle to write point-by-point response letters to reviewer comments under deadline pressure. This skill provides structured templates, tone guidance, and conflict resolution strategies for Nature-family and general scientific journal revisions.

## Install

```bash
npx skillstore add community contribution, refactored into static/dynamic layers/yuan1z0825-nature-response
```

## Metadata

- - Slug: yuan1z0825-nature-response
- - Version: 1.0.0
- - Author: Community contribution, refactored into static/dynamic layers
- - GitHub username: Yuan1z0825
- - License: MIT
- - Repository: https://github.com/Yuan1z0825/nature-skills/tree/main/skills/nature-response
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 81
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/yuan1z0825-nature-response
- - Manifest: https://skillstore.pages.dev/api/skills/yuan1z0825-nature-response/manifest

## Capabilities

- Draft point-by-point responses to reviewer comments for major and minor revisions
- Generate professional rebuttal letters with appropriate academic tone and stance
- Handle conflicting reviewer recommendations with structured conflict resolution
- Support Chinese-language academic correspondence \(审稿回复, 修回信\)
- Provide QA checklist for response letter completeness and professionalism
- Classify reviewer comments by type \(major concerns, minor suggestions, clarifications\)

## Use Cases

- Major Revision Response: Draft a comprehensive response letter addressing all major reviewer concerns for a Nature-family manuscript revision request.
- Minor Revision Polish: Quickly generate concise responses to minor reviewer comments and clarification requests.
- Chinese Academic Correspondence: Draft response letters in Chinese for domestic Chinese journals or bilingual correspondence with international reviewers.

## Prompt Templates

### Draft Major Revision Response

```
Here are the reviewer comments for my manuscript: [paste comments]. Please draft a point-by-point response letter addressing each concern. The manuscript is for [journal name] and the decision was major revision.
```

### Revise Existing Draft

```
Please review and improve this response letter draft: [paste draft]. Check for tone, completeness, and professional academic style. Identify any reviewer comments I may have missed.
```

### Handle Conflicting Reviews

```
Reviewer 1 suggests [X] but Reviewer 2 suggests [Y]. How should I handle this conflict in my response letter? Please draft a diplomatic response that addresses both perspectives.
```

### Audit Response Completeness

```
Please audit my response letter against the original reviewer comments: [paste reviewer comments] and [paste response letter]. Flag any unaddressed concerns and suggest improvements.
```

## Limitations

- Cannot guarantee journal acceptance or reviewer satisfaction
- Does not perform actual experiments or generate scientific data
- Response quality depends on the clarity of reviewer comments provided
- Limited to text-based drafting; does not handle supplementary file preparation

## Best Practices

- Always respond to every single reviewer comment, even if briefly, to demonstrate thoroughness
- Maintain a respectful and grateful tone throughout, even when disagreeing with reviewers
- Quote the reviewer's exact words before your response for clarity and easy reference
- Include specific page numbers, figure references, and line numbers when describing changes made
- Use a consistent format \(numbered responses matching reviewer comments\) for professional presentation

## Anti Patterns

- Do not copy-paste the same generic response for multiple comments without addressing each specifically
- Avoid defensive or confrontational language when disagreeing with reviewer assessments
- Do not ignore or skip minor comments, as this signals lack of attention to detail
- Avoid making promises about future work that you cannot or will not complete

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-24T06:07:49.299\+00:00
- - Summary: All 416 static analysis findings are false positives. The skill consists entirely of Markdown documentation files for academic peer-review response letter drafting. No executable code, scripts, or shell commands exist. 'Ruby/shell backtick execution' flags are Markdown inline code formatting, not actual Ruby/shell commands. 'Weak cryptographic algorithm' flags are academic content discussing research methods. No real security risks were identified.

## Stats

- - Views: 0
- - Downloads: 2
- - Favorites: 0
- - Popularity score: 0