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
vector-corpusGround STORM article runs on a user CSV or local corpus with VectorRM and Qdrant, including schema validation, offline/online vector stores, device choices, and STORMWikiRunner integration.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task asks to run or prepare STORM over a user-owned CSV/local corpus rather than Internet search. It covers VectorRM, Qdrant offline/online stores, CSV validation, corpus chunking, embedding device choices, and the handoff into STORMWikiRunner.
content and url columns and wants STORM grounded on those rows.VectorRM from CSV documents.VectorRM to retrieve from it.VectorRM.__init__, init_offline_vector_db, init_online_vector_db, get_vector_count, forward, or QdrantVectorStoreManager.create_or_update_vector_store.../storm-wiki/.../co-storm/.VectorRM into STORM.VectorRM and QdrantVectorStoreManager.scripts/validate_vector_corpus_csv.py: standard-library CSV schema checker. Use --strict-unique-url before indexing.scripts/process_kaggle_arxiv_abstract_dataset.py: converts Kaggle arXiv abstracts CSVs into the VectorRM CSV schema.scripts/run_storm_wiki_with_vector_rm.py: safe helper for corpus-grounded STORM with current LitellmModel; supports --dry-run and --validate-only without embedding, Qdrant, LLM, or network calls.python scripts/validate_vector_corpus_csv.py --input-path corpus.csv --strict-unique-url.--vector-db-mode offline --offline-vector-db-dir ./vector_store;QDRANT_API_KEY with --vector-db-mode online --online-vector-db-url https://....--device cpu; use cuda or mps only for embedding acceleration when available.--dry-run or --validate-only first, then run the full helper with explicit STORM stage flags.The runtime scripts assume the public knowledge-storm package is installed for full runs. Help, dry-run, and validate-only paths avoid package imports where possible.