Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/wiki-research-loop
Auto-grow a pro-workflow wiki by running a budget-capped BFS research loop over pluggable source fetchers (web, arXiv, GitHub). Each iteration pops a seed from the queue, fetches sources, drafts a wiki page, dedupes claims against existing pages, enqueues follow-up seeds. Halts on budget cap, depth cap, or convergence.
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
and 11 more in the full report
14 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
What event hook name is dispatched when 'scripts/research-tick.js' is executed by a cron runner?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the event hook pro-workflow:research-tick | Missed | Passed |
The instructions your model reads when the skill loads.
Driver that turns a wiki into an auto-grown knowledge base. Layers on top of wiki-builder and wiki-query.
seed-queue (pending) → next-seed
→ fetch sources via plugins (web | arxiv | github)
→ extract claims
→ dedupe vs index (FTS5; later vector via 3.3.2)
→ compile new page or amend existing
→ upsert page (auto-FTS-index)
→ enqueue follow-up seeds (max-depth gate)
→ mark seed done
→ if budget OR convergence OR kill-switch → halt
budget_usd exceeded (loop tracks per-fetcher cost estimate)max_pages_per_run writtenmax_depth reached on every active branch~/.pro-workflow/STOP exists (operator kill-switch)wiki.config.md auto_research.enabled: falseprivate: true AND any non-local fetcher selectedIn a plugin session, call the providers MCP server's run_provider_task tool with task: "research" and the runner arguments below, for example args: ["run", "agent-memory", "--fetchers", "github"]. Its optional GitHub token comes from the plugin configuration dialog. The direct CLI uses PRO_WORKFLOW_GITHUB_TOKEN when explicitly supplied. Never retrieve tokens from existing machine credentials.
node $SKILL_ROOT/scripts/research-loop.js run <slug> [--max-pages N] [--max-depth N] [--budget-usd 0.50] [--fetchers web,arxiv,github]
node $SKILL_ROOT/scripts/research-loop.js seed <slug> "<query>" [--depth 0] [--parent-id N]
node $SKILL_ROOT/scripts/research-loop.js seeds <slug> [--status pending|active|done|failed]
node $SKILL_ROOT/scripts/research-loop.js cancel <slug>
node $SKILL_ROOT/scripts/research-loop.js status
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.