paper-writer
VerifiedMedical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers. Triggers: 'write paper', 'paper-write', 'start manuscript', '論文を書く', '論文執筆', '論文プロジェクト', 'manuscript', 'research paper', '原稿作成'.
templates/revision-cover-letter.md
View on GitHub# Revision Cover Letter Template
## How to Use This Template
This template is specifically for **resubmission/revision** cover letters, not initial submission cover letters (see `cover-letter.md` for initial submissions). The revision cover letter accompanies your revised manuscript and point-by-point response to reviewers.
1. Replace all placeholders in `[BRACKETS]`
2. Customize the summary of changes to match your actual revisions
3. Reference the separate point-by-point response document
4. Keep the letter concise (ideally 1-2 pages)
5. Have all co-authors review before submission
---
## English Version
### Template
---
**Date:** [Month Day, Year]
**To:**
[Editor Name], [Editor Title]
[Journal Name]
**Re:** Revised Manuscript [MANUSCRIPT-ID]
**Title:** "[Full Manuscript Title]"
---
Dear [Dr./Prof. Editor Last Name],
Thank you for the opportunity to revise our manuscript entitled "[Full Manuscript Title]" (Manuscript ID: [MANUSCRIPT-ID]) for [Journal Name]. We are grateful to you and the reviewers for the thorough and constructive evaluation of our work.
We have carefully considered all comments and have revised the manuscript accordingly. We believe the revisions have substantially strengthened the paper. Below, we summarize the major changes made in response to the reviewers' feedback.
#### Summary of Major Changes
1. **[Brief description of major change 1]** -- In response to Reviewer [X], Comment [Y], we have [describe what was done]. (See revised manuscript, [Section/Page/Lines])
2. **[Brief description of major change 2]** -- Following Reviewer [X]'s suggestion, we have [describe what was done]. (See revised manuscript, [Section/Page/Lines])
3. **[Brief description of major change 3]** -- To address concerns raised by Reviewer [X] regarding [topic], we have [describe what was done]. (See revised manuscript, [Section/Page/Lines])
4. **[Additional analyses or data]** -- As requested by Reviewer [X], we have performed [describe new analysis/experiment] and included the results in [Table/Figure/Supplementary].
5. **[Writing and presentation improvements]** -- We have [improved clarity of writing / reorganized sections / enhanced figures / etc.] throughout the manuscript.
A detailed point-by-point response to each reviewer comment is provided in the accompanying document titled "Response to Reviewers." In that document, we address every comment individually with specific page and line references to the revised manuscript.
All changes in the revised manuscript are highlighted using [track changes / colored text / markup], making it easy to identify the modifications.
We confirm that:
- All authors have reviewed and approved the revised manuscript
- No changes have been made to the author list
- All new data and analyses are original and have not been published elsewhere
- [Any additional journal-specific declarations]
We hope that the revised manuscript is now suitable for publication in [Journal Name]. We look forward to your decision.
Sincerely,
[Corresponding Author Name], [Degree(s)]
[Title/Position]
[Department]
[Institution]
[Address]
[Email]
[Phone]
On behalf of all co-authors:
[List all co-author names]
---
### Tips for Framing Changes Positively
| Instead of... | Write... |
|--------------|----------|
| "The reviewer was incorrect about..." | "We appreciate the reviewer's perspective and would like to clarify that..." |
| "We disagree with this comment" | "This is an important point. After careful consideration, we have chosen to [approach] because..." |
| "We could not do the requested analysis" | "While the suggested analysis was not feasible due to [reason], we have addressed this concern by [alternative approach]..." |
| "We fixed the errors the reviewer found" | "We thank the reviewer for identifying these issues and have corrected them throughout the manuscript" |
| "We already addressed this in the original manuscript" | "We appreciate this comment. To improve clarity, we have expanded our discussion of this point on Page X, Lines Y-Z" |
| "We deleted the section as requested" | "Following the reviewer's recommendation, we have streamlined the manuscript by [restructuring/condensing] this section" |
| "The reviewer misunderstood our methods" | "We realize our original description may not have been sufficiently clear. We have rewritten the Methods section to better explain..." |
### Key Principles for Positive Framing
1. **Lead with gratitude.** Every paragraph about changes should acknowledge the reviewer's contribution.
2. **Use active, positive language.** "We have strengthened..." not "We were forced to change..."
3. **Show how changes improved the paper.** Frame every revision as making the manuscript better, not just complying with demands.
4. **Be specific about improvements.** "We added a subgroup analysis (new Table 3) that reveals important age-related differences" is better than "We did the analysis."
5. **Avoid defensive language.** Even when you disagree, frame your response as a scientific discussion, not a debate.
### How to Reference the Point-by-Point Response
Always explicitly mention the accompanying response document. Use one of these formulations:
> "A comprehensive point-by-point response to all reviewer comments is provided as a separate document accompanying this cover letter."
> "Please find enclosed our detailed responses to each reviewer comment, including specific references to the revised manuscript pages and line numbers."
> "The accompanying 'Response to Reviewers' document addresses each comment individually, with the revised text quoted for easy reference."
---
## 日本語版
### テンプレート
---
**日付:** [YYYY年MM月DD日]
**宛先:**
[雑誌名]
編集委員長 [編集者名] 先生
**件名:** 改訂原稿の再投稿(原稿番号:[MANUSCRIPT-ID])
**論文タイトル:** 「[論文タイトル]」
---
[編集者名] 先生
拝啓
時下ますますご清祥のこととお慶び申し上げます。
この度は、私どもの原稿「[論文タイトル]」(原稿番号:[MANUSCRIPT-ID])に対して改訂の機会を賜り、誠にありがとうございます。編集委員長ならびに査読者の先生方からいただいた丁寧かつ建設的なご指摘に深く感謝申し上げます。
すべてのご指摘を慎重に検討し、原稿を改訂いたしました。改訂により論文が大幅に改善されたものと確信しております。以下に、主要な変更点を要約いたします。
#### 主要な変更点
1. **[主要な変更点1の概要]** -- 査読者[X]のコメント[Y]に対応し、[変更内容]を行いました。(改訂原稿 [セクション/ページ/行] 参照)
2. **[主要な変更点2の概要]** -- 査読者[X]のご提案に従い、[変更内容]を行いました。(改訂原稿 [セクション/ページ/行] 参照)
3. **[主要な変更点3の概要]** -- 査読者[X]より[トピック]に関してご懸念をいただいたため、[変更内容]を行いました。(改訂原稿 [セクション/ページ/行] 参照)
4. **[追加解析・データ]** -- 査読者[X]のご要望に基づき、[追加解析の内容]を実施し、結果を[表/図/補足資料]に掲載いたしました。
5. **[記述・表現の改善]** -- 原稿全体にわたり、[記述の明確化/構成の見直し/図表の改善]を行いました。
各査読者のコメントに対する詳細な回答は、別添の「査読者への回答」に項目ごとに記載しております。改訂原稿の該当ページ・行番号を明示し、修正後の本文を引用しております。
改訂原稿では、[変更履歴機能/カラーテキスト]により変更箇所を明示しております。
以下の点を確認いたします:
- 全著者が改訂原稿を確認・承認済みであること
- 著者リストに変更がないこと
- 新たなデータ・解析はすべてオリジナルであり、他誌に未発表であること
- [雑誌固有の宣言事項がある場合は追記]
改訂原稿が[雑誌名]への掲載にふさわしいものとなっていることを願っております。ご審査のほど、何卒よろしくお願い申し上げます。
敬具
[責任著者名]
[学位]
[職位]
[所属]
[住所]
[メールアドレス]
[電話番号]
共著者を代表して:
[共著者名一覧]
---
### 日本語カバーレターのポイント
1. **冒頭の挨拶を忘れない** -- 「拝啓」「時下ますますご清祥のこと...」は日本語の学術書簡で標準的な形式
2. **敬語を一貫して使う** -- 査読者は「先生」、コメントは「ご指摘」「ご提案」
3. **簡潔かつ具体的に** -- 主要変更点を箇条書きで明確に記載
4. **査読者への回答文書への参照** -- 別添文書の存在を明記
5. **結びの挨拶** -- 「敬具」で締める
6. **全著者の承認を明記** -- これは必須事項
### 査読者への回答文書への参照方法(日本語)
> 「各査読者のコメントに対する詳細な回答は、別添の『査読者への回答』に記載しております。」
> 「添付の回答書において、すべてのご指摘に対して個別に回答し、改訂原稿の該当箇所を明示しております。」
---
## Checklist Before Submitting the Revision
### Cover Letter
- [ ] Editor name and journal name are correct
- [ ] Manuscript ID matches
- [ ] All major changes are summarized
- [ ] Point-by-point response document is referenced
- [ ] All authors are listed and have approved
- [ ] Tone is positive and grateful throughout
- [ ] Letter is concise (1-2 pages maximum)
### Accompanying Documents
- [ ] Revised manuscript with track changes
- [ ] Clean version of revised manuscript (if required)
- [ ] Point-by-point response to reviewers (see `response-to-reviewers.md`)
- [ ] Updated supplementary materials (if applicable)
- [ ] Updated figures/tables (if applicable)
- [ ] Completed revision checklist (if journal provides one)
### Final Verification
- [ ] All co-authors have reviewed the revision package
- [ ] Page/line numbers in the response match the revised manuscript
- [ ] No tracked changes remain in the "clean" version
- [ ] All new references are properly formatted
- [ ] Word count is within journal limits
- [ ] Figures meet journal resolution/format requirements
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |