paper-writing-section
Write a specific section of an academic paper (Abstract, Introduction, Background, Related Work, Methods, Experiments, Results, Discussion/Conclusion) with section-specific guidance and two-pass refinement. Use when the user wants to write, draft, or improve a paper section.
What this skill does
# Paper Section Writer
Write a publication-quality section for an academic paper.
## Input
- `$0` — Section name: `abstract`, `introduction`, `background`, `related-work`, `methods`, `experimental-setup`, `results`, `discussion`, `conclusion`
- `$1` — (Optional) Path to context file (research plan, results, prior sections)
## Workflow
### Step 1: Gather Context
Read the paper's existing `.tex` files, experiment logs, result files, and any provided context. Understand: title, contributions, methodology, key results, figures, tables.
### Step 2: Write the Section
Load section-specific tips from `references/section-tips.md`. Before every paragraph, include a brief plan as a LaTeX comment (`% Plan: ...`).
### Step 3: Two-Pass Refinement
Apply both refinement passes from `references/refinement-prompts.md`:
- **Pass 1**: Fix errors (unenclosed math, broken refs, hallucinated numbers, duplicate labels)
- **Pass 2**: Remove redundancies, compress, ensure smooth transitions
## References
- Section writing tips: `~/.claude/skills/paper-writing-section/references/section-tips.md`
- Refinement prompts and error checklist: `~/.claude/skills/paper-writing-section/references/refinement-prompts.md`
## Output
LaTeX fragment (no `\documentclass`, no preamble). All math enclosed in `$...$` or `\begin{equation}`, all figures referenced with `\ref{}`, all cited works use `\cite{}`, no placeholder text.
## Quality Checklist
- All math enclosed properly
- All `\ref{}` and `\cite{}` valid
- No TODO/TBD/FIXME markers
- Numbers match experimental logs exactly
- Writing style is objective — no hype words
- Section length appropriate for venue
## Related Skills
- Upstream: [data-analysis](../data-analysis/), [figure-generation](../figure-generation/), [table-generation](../table-generation/), [related-work-writing](../related-work-writing/)
- Downstream: [latex-formatting](../latex-formatting/), [citation-management](../citation-management/)
- See also: [paper-assembly](../paper-assembly/)
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.