Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/survey-generator
Compile a structured literature survey on any AI/ML topic. Agent curates a research bundle (taxonomy + sections + bibliography of real papers) from a public anchor resource, then a chosen LLM generates the survey artifact. Output target is a wiki page (markdown), not a one-off HTML — survey lands in `<wiki>/derived/surveys/<slug>.md` with full bibliography rows in `sources.md`. Provider-agnostic (Anthropic/OpenAI/OpenRouter/Fireworks/custom OpenAI-compat).
Passed 15 of 20 test cases with the skill, and 5 of 20 without it.
and 9 more in the full report
12 fixed5 passed either way5 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 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should generated markdown survey documents be written when executing the survey artifact generator on `agent-memory` wiki for topic 'planner-agents'?
| Checked | Without skill | With skill |
|---|---|---|
| Places output files in agent-memory/derived/surveys/ path. | Missed | Passed |
The instructions your model reads when the skill loads.
Provider-agnostic literature-survey artifact generator. Output flows into a pro-workflow wiki, not a standalone HTML file — survives sessions and indexes for FTS5 retrieval.
| dair | pro-workflow |
|---|---|
| Hardcoded Kimi K2.6 on Fireworks | Provider-agnostic (Anthropic/OpenAI/OpenRouter/Fireworks/custom) |
| Output = single-file HTML with inline SVG | Output = wiki markdown page + bibliography rows in sources.md |
| One-off artifact, no follow-up | Persists in FTS5 index; reused by wiki-research-loop |
| Manual run only | Composable with /wiki research for auto-bibliography expansion |
/wiki research runs: gives the loop a high-quality seed bundle| Input | Required | Description |
|---|---|---|
topic | yes | "Reasoning Models", "Agentic Engineering" |
source_url | yes | Public anchor: arXiv survey, GitHub awesome-list, canonical blog post |
--wiki <slug> | yes | Target wiki for the artifact |
--bibliography-size N | no | Default 20. 40-50 comprehensive, 80-100 exhaustive |
--section-count N | no | Default 6-10 numbered sections |
--provider name | no | Override provider (default: first explicitly configured provider) |
--model id | no | Override model |
WebFetch source_url. Extract subtopics + cited papers. For GitHub awesome-lists, walk README + linked papers files. For arXiv survey PDFs, use abstract + ToC.
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.