Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fradser/storm-research
Run STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discovers personas, runs simulated Q&A per persona in parallel, and produces an information table + deduplicated sources.
Passed 5 of 12 test cases with the skill, and 4 of 12 without it.
and 3 more in the full report
6 fixed3 passed either way9 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Once research interviews for 'perovskite solar cells' finish and sources are verified, what state updates must be written to run-config.json?
| Checked | Without skill | With skill |
|---|---|---|
| Sets phases.research to completed in run-config.json | Missed | Passed |
The instructions your model reads when the skill loads.
Phase 1 of the STORM pipeline. Discovers research personas, runs a simulated multi-turn conversation per persona (each grounded in retrieval), and produces the information table that downstream phases consume.
Load storm-engine via the Skill tool. Its "Persona Discovery", "Simulated Conversation", "Retrieval", and "Citation Hygiene" sections govern this phase.
This phase is complete iff research/sources.json exists and has ≥1 entry. If --force is not set and the artifact exists, skip and exit early.
research/ subdir exists.--max-perspective personas (default 3), each with a distinct question category, plus one "Basic fact writer". Write research/personas.json.ToolSearch, look for exa-mcp-server search tools (code-search, research-paper-search, company-search, personal-site-search, financial-report-search, x-search). Record which are available in run-config.json as retriever. If none and not --docs, fall back to WebSearch/WebFetch.storm-researcher subagent per persona in a single message (parallel). Each subagent:
max_turns.question_to_query, retrieves, answers with source attribution.max_turns reached.{question, queries, snippets, answer, cited_sources}.research/conversations.jsonl (one JSON object per line). Deduplicate cited sources by URL into research/sources.json, assigning sequential ids. Strip any inline [n] from snippets before storing (citation hygiene).sources.json has ≥1 entry and every persona produced ≥1 turn. If a persona produced nothing, note it but do not fail the whole phase.run-config.json: phases.research = "completed", retriever, source count.If the user reports rate-limit errors during this phase, reduce concurrency by running personas in smaller batches (e.g. 2 at a time) rather than lowering max_turns — mirroring upstream's max_thread_num guidance.
Report: number of personas, total conversation turns, number of deduplicated sources, and the path to research/sources.json.
test cases passed, vs 4 / 12 without
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.