How do I install the Storm Write skill?

Run npx skillmds@latest add fradser/storm-write in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Storm Write safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Storm Write?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Storm Write free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Storm Write?

FradSer (@fradser) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Storm Write by fradser — Agent Skill

Name: Storm Write
Rating: 4.5 (4 reviews)
Author: FradSer

Storm Write

Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.

FradSer Updated Aug 19, 2026 580 repo stars

File contents

/storm:write

Phase 3 of the STORM pipeline. Writes each outline section in parallel (one Task subagent per section), each grounded in top-k relevant sources from the research information table, with inline [n] citations.

CRITICAL: Prerequisites

Load storm-engine via the Skill tool.
outline.md MUST exist (phase 2 complete). If absent, stop and instruct the user to run /storm:outline first.

Completion Contract

This phase is complete iff article.md exists and every outline section (except Introduction/Conclusion/Summary placeholders) has body text. If --force is not set and it exists, skip and exit early.

Procedure

Resolve output dir.
Read outline.md and research/sources.json. Index sources for retrieval (simple: rank by keyword/heading overlap with the section title).
Identify sections to write — skip any whose heading is exactly "Introduction", "Conclusion", or "Summary" (these are filled in polish).
Parallel writing — for each section, launch ONE Task subagent (single message, parallel). Each subagent:
- Receives: topic, section heading, top-k relevant sources (default --retrieve-top-k 3), the full outline for context.
- Writes the section body with inline [n] citations mapping to sources.json ids.
- If no relevant sources, writes uncited and marks .
- Returns the section markdown.
Assemble — concatenate sections in outline order under their headings into article.md. Preserve the heading hierarchy from outline.md.
Verify every non-placeholder section has body. Update run-config.json: phases.write = "completed", section count, any TODO-flagged sections.

Citation Rules

Only cite [n] where n is an existing id in sources.json. Never mint a new id here.
Place [n] immediately after the claim it supports. Multi-source claims use [1][2].
Do not cite in placeholder sections.

Output

Report: number of sections written, number of citations used, list of sections flagged as TODO (no source), and the path to article.md.

---name: storm-writedescription: Run STORM phase 3 — per-section article writing. This skill should be used when the user asks to "write the article sections", "draft the storm article", or invokes /storm:write. Writes each outline section in parallel with inline citations grounded in the research sources.---# /storm:writePhase 3 of the STORM pipeline. Writes each outline section in parallel (one Task subagent per section), each grounded in top-k relevant sources from the research information table, with inline `[n]` citations.## CRITICAL: Prerequisites- Load `storm-engine` via the Skill tool.- `outline.md` MUST exist (phase 2 complete). If absent, stop and instruct the user to run `/storm:outline` first.## Completion ContractThis phase is complete iff `article.md` exists and every outline section (except Introduction/Conclusion/Summary placeholders) has body text. If `--force` is not set and it exists, skip and exit early.## Procedure1. Resolve output dir.2. Read `outline.md` and `research/sources.json`. Index sources for retrieval (simple: rank by keyword/heading overlap with the section title).3. **Identify sections** to write — skip any whose heading is exactly "Introduction", "Conclusion", or "Summary" (these are filled in `polish`).4. **Parallel writing** — for each section, launch ONE Task subagent (single message, parallel). Each subagent: - Receives: topic, section heading, top-k relevant sources (default `--retrieve-top-k` 3), the full outline for context. - Writes the section body with inline `[n]` citations mapping to `sources.json` ids. - If no relevant sources, writes uncited and marks ``. - Returns the section markdown.5. **Assemble** — concatenate sections in outline order under their headings into `article.md`. Preserve the heading hierarchy from `outline.md`.6. Verify every non-placeholder section has body. Update `run-config.json`: `phases.write = "completed"`, section count, any TODO-flagged sections.## Citation Rules- Only cite `[n]` where `n` is an existing `id` in `sources.json`. Never mint a new id here.- Place `[n]` immediately after the claim it supports. Multi-source claims use `[1][2]`.- Do not cite in placeholder sections.## OutputReport: number of sections written, number of citations used, list of sections flagged as TODO (no source), and the path to `article.md`.

Frequently asked questions