Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/storm-generate
Run the full STORM pipeline end-to-end. This skill should be used when the user asks to "generate a storm article", "write a wikipedia-style article about X", "research and write a long-form piece on X", or invokes /storm:generate. Orchestrates research -> outline -> write -> polish, skipping already-completed phases.
7 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
After the `/storm:research` skill finishes running during an automated article build on 'Microplastics Remediation', what step must occur before updating the config file?
| Checked | Without skill | With skill |
|---|---|---|
| Verifies the existence and validity of the research completion artifact before marking status as completed | Missed | Passed |
The instructions your model reads when the skill loads.
End-to-end STORM article generation. Runs all four phases in sequence, skipping any phase whose artifact already exists (unless --force).
Load the storm-engine skill via the Skill tool before doing anything else. It defines the artifact layout, stage-gating contract, citation hygiene, and retrieval fallback that this orchestration depends on. Do not improvise these.
<topic> (required) — the subject of the article.--max-perspective N (default 3) — number of personas to discover.--max-turns N (default 3) — max Q&A turns per persona.--output-dir PATH — explicit output location. Mutually exclusive with --save.--save — persist to docs/storm/<slug>/ instead of a temp dir.--docs DIR — ground on local documents in addition to (or, with --docs-only, instead of) the web.--force — re-run all phases even if artifacts exist.--retriever mcp|web|local — override retrieval source (default: mcp with fallback).AskUserQuestion to request one.<slug> and resolve <output_dir> per the engine contract. Create the directory.run-config.json with a snapshot of all parameters. Stamp started_at using date -u +%Y-%m-%dT%H:%M:%SZ (the only place a timestamp is generated).research, outline, write, polish:
a. Check the phase's completion artifact (per engine contract).
b. If complete and not --force: mark phases.<name>: "skipped" in run-config.json, log "Skipping (artifact present)".
c. Otherwise: invoke the corresponding /storm:<phase> skill via the Skill tool, passing the resolved output dir and run parameters. After it returns, verify its artifact and mark phases.<name>: "completed" (or "failed" with the error).article-polished.md and print a summary: topic, word count, number of sources cited, number of sections, and the absolute path to the final article.research and write phases use Task subagents internally (see their own SKILL.md files). This orchestration skill runs phases strictly sequentially — never parallelize across phases, because each phase depends on the previous phase's artifacts.
If a phase fails, stop and report. Do not proceed to the next phase. Update run-config.json with the failure reason. A re-invocation (without --force) will resume from the failed phase since completed prior phases will be skipped.
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.