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/introduction.md
View on GitHub# Introduction Section Writing Guide
## Structure: 3 Paragraphs (Funnel Shape)
### Paragraph 1: General Background
- Start broad: a fact everyone in the field agrees with
- Establish the importance of the topic
- Cite 2-4 key background references
Example pattern:
> "{Disease/Topic} is a significant {clinical problem / public health concern} affecting {population}. {Treatment/Approach} has been established as {standard/effective/common}..."
### Paragraph 2: Knowledge Gap (Clinical Question)
- Narrow the focus: what is NOT known
- Review what prior studies have shown
- Identify the specific gap your study addresses
- Use transition words: "However,", "Nevertheless,", "Although... it remains unclear..."
Example pattern:
> "However, the relationship between {Factor X} and {Outcome Y} remains unclear. Previous studies have reported {conflicting results / limited evidence}..."
### Paragraph 3: Study Objective
- State the purpose of YOUR study clearly
- Use standard phrasing: "The aim/purpose/objective of this study was to..."
- This paragraph MUST mirror the Conclusion
Example pattern:
> "The purpose of this study was to investigate whether {Factor X} is an independent predictor of {Outcome Y} in patients undergoing {Treatment Z}."
## Rules
- Write Paragraph 3 FIRST (with Conclusion), then Paragraphs 1-2 later
- Keep it concise: 3 paragraphs, rarely more
- Every statement should be supported by a reference (except for universally accepted facts)
- Do not include your own results
- Do not over-review the literature (save detailed comparison for Discussion)
- Use present tense for established knowledge, past tense for specific studies
## Common Mistakes
- Too long (reviewing everything ever written on the topic)
- Missing clear statement of study objective
- Objective does not match Conclusion
- No clear gap identified (why is this study needed?)
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: 322k | 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 |