Install any skill in seconds. Free to start, no credit card required.
Get Started Free →open-gitagent/wiki-query
Query the wiki to answer questions. Searches wiki pages, synthesizes answers with citations, and optionally files valuable answers back as new wiki pages.
Passed 7 of 13 test cases with the skill, and 5 of 13 without it.
and 3 more in the full report
6 fixed6 passed either way8 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.
We want to check what our internal notes say about our SOC2 audit status. Should we start by scanning raw logs, or check `memory/wiki/index.md` first to find relevant wiki pages?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies reading memory/wiki/index.md before reading individual pages. | Missed | Passed |
The instructions your model reads when the skill loads.
Answer questions by searching and synthesizing from the wiki.
memory/wiki/index.md to find relevant pagesmemory/wiki/Format depends on the question:
If the answer represents a useful synthesis that doesn't exist as a wiki page:
memory/wiki/memory/wiki/index.mdmemory/log.md:
## [YYYY-MM-DD] query-filed | Page Title
- Question: [original question]
- Pages referenced: [list]
- New page: memory/wiki/page-name.md
Good answers should not disappear into chat history. A comparison you asked for, an analysis, a connection you discovered — these are valuable wiki content. Filing them back means your explorations compound in the knowledge base just like ingested sources do.
test cases passed, vs 5 / 13 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.