research-paper-writing
Improve academic paper writing quality for ML/CV/NLP-style papers with clear section structure, paragraph flow, and reviewer-facing presentation. Use when drafting or revising Abstract, Introduction, Related Work, Method, Experiments, or Conclusion; polishing figures/tables; checking claim-support alignment; or performing self-review before submission.
What this skill does
# Research Paper Writing ## Overview Use this skill to rewrite a research paper into a reviewer-friendly, high-clarity draft. Prioritize first-impression quality (figures/tables/layout), logical flow, and evidence-backed claims. ## Core Workflow 1. Clarify the paper story before sentence-level edits. 2. Use section-specific guidance in `references/`. 3. Rewrite paragraph-by-paragraph with one message per paragraph. 4. Run reverse outlining after writing each section. 5. Check every major claim in Abstract/Introduction against experimental evidence. 6. Run final-paper adversarial review with `references/paper-review.md`. ## Global Principles 1. Keep one paragraph for one message only. 2. State the paragraph message in the first sentence. 3. Make nouns self-contained; define new terms before reusing them. 4. Maintain sentence-to-sentence flow (cause, contrast, consequence, or refinement). 5. Iterate with adversarial self-review: read as a skeptical reviewer. 6. Treat visual quality as core content, not decoration. 7. Use a clean teaser and pipeline figure. 8. Use readable, minimal-ink tables. 9. Keep formatting consistent and tidy. ## Paragraph Clarity Check (Important) Use this quick test whenever the user asks whether a paragraph "flows" or is clear. 1. Read as an external reader: - Does this paragraph have one explicit message? - Does the first sentence state what this paragraph will do? - Are all key nouns/terms readable without hidden context? - Does each sentence connect to the previous one with a clear relation (cause, contrast, consequence, refinement, example)? 2. Run reverse outlining for the current section: - Write down thesis/main claim. - Write down each paragraph topic sentence. - Write down the evidence/explanation points under each paragraph. - Check mapping: topic sentence -> thesis, and evidence -> topic sentence. - Revise or remove any paragraph that cannot be mapped cleanly. 3. If flow is still weak, add temporary section headers and explicit transition phrases during revision, then remove unnecessary headers before finalizing. Source reference for this check: - `references/does-my-writing-flow-source.md` ## Section Guides Load only the needed section file: - Introduction: `references/introduction.md` - Abstract: `references/abstract.md` - Related Work: `references/related-work.md` - Method: `references/method.md` - Experiments: `references/experiments.md` - Conclusion: `references/conclusion.md` - Paper review (Paper Rview): `references/paper-review.md` - Paragraph clarity source: `references/does-my-writing-flow-source.md` - Example bank index: `references/examples/index.md` ## Paper Review Core Points Use `references/paper-review.md` for the full checklist and workflow. 1. Add an end-of-draft self-review question list in five dimensions: - contribution, - writing clarity, - experimental strength, - evaluation completeness, - method design soundness. 2. Treat claim-evidence alignment as a hard constraint, especially for Abstract and Introduction. 3. Perform adversarial writing: review as a skeptical reviewer and resolve every high-risk question. 4. Revise until major rejection risks are explicitly addressed. ## Execution Rules 1. Build a mini-outline before drafting prose. 2. For each subsection, explicitly include motivation, design, and technical advantage when applicable. 3. Avoid writing style that looks like incremental patching of a naive baseline. 4. Keep terminology stable across the full paper. 5. If a claim cannot be supported by results, weaken or remove the claim. 6. Before finalizing, append and answer a five-dimension self-review question list, then revise the paper based on unresolved items. 7. Do not load all section references (Introduction/Abstract/Related Work/Method/Experiments/Conclusion) at once; load only the specific section guide needed for the current edit target. ## Output Contract When asked to rewrite or draft sections, return: 1. A compact section outline (3-7 bullets). 2. Revised paragraphs with explicit paragraph roles (opening/challenge/method/advantage/evidence/limitation). 3. A short self-review checklist covering clarity, flow, terminology consistency, unsupported claims, and missing evidence. 4. A claim-evidence map for each major claim in the revised text using `Claim: ... | Evidence: ... | Status: supported/needs evidence`.
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.