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/discussion.md
View on GitHub# Discussion Section Writing Guide
## Structure
### Paragraph 1: Summary of Main Findings
- Restate the key results (briefly, not repeating all numbers)
- Connect to the study objective
- "In this study, we found that..."
### Paragraphs 2 to N-1: Comparison with Literature
- Compare your findings with previous studies
- Use the literature matrix to structure comparisons
- For each key finding:
1. State your result
2. Compare with prior studies (agree or disagree?)
3. Offer possible explanations for differences
4. Support with references
Pattern:
> "Our finding that {X} is consistent with {Author et al.}, who reported {Y}. However, {Other Author et al.} found {Z}, which may be explained by differences in {population / methodology / definitions}..."
### Paragraph N: Limitations
- Be honest and specific
- Common limitations to address:
- Study design (retrospective, single-center)
- Sample size
- Selection bias
- Confounders not measured
- Generalizability
- Do NOT apologize; state limitations factually
### Final Paragraph: Implications and Future Directions
- Clinical implications of your findings
- What should clinicians consider?
- What future studies are needed?
- Keep speculation minimal and clearly labeled
## Rules
- No new results (all results belong in Results section)
- No excessive speculation or "leap of logic"
- Every claim must be supported by data or references
- Keep it focused (Discussion is often too long)
- Do not repeat the Introduction background
- Do not overstate the significance of your findings
## Common Mistakes
- Too long (readers lose interest)
- Speculating beyond what the data supports
- Hiding or minimizing limitations (reviewers will catch this)
- Repeating Results section verbatim
- Not comparing with existing literature
- Making therapeutic recommendations not supported by the study design
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 |