executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
storm-wikiGenerate STORM Wikipedia-like articles with STORMWikiRunner, LiteLLM model configs, internet retrievers, staged execution, output inspection, callbacks, and demo-light setup guidance.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to generate, resume, inspect, or troubleshoot a STORM Wikipedia-like article with the installed knowledge-storm Python package.
STORMWikiLMConfigs, STORMWikiRunnerArguments, and a search retriever.STORMWikiRunner.run(...) through research, outline, article, and polish stages.conversation_log.json, storm_gen_outline.txt, storm_gen_article.txt, storm_gen_article_polished.txt, run_config.json, and llm_call_history.jsonl.BaseCallbackHandler callbacks for progress reporting.VectorRM, and user-corpus grounding belong to the vector-corpus sub-skill.warm_start, step, generate_report, mind map behavior, and Co-STORM logging belong to the co-storm sub-skill.--help and --dry-run before any network or LLM call.pip install knowledge-storm
python scripts/run_storm_wiki.py --help
python scripts/run_storm_wiki.py \
--dry-run \
--topic "Example topic" \
--output-dir ./storm-results \
--retriever bing
If the dry-run reports missing model or retriever credentials, set environment variables or pass a --secrets-file TOML before running without --dry-run.