llm-wiki-loop: Skill for Claude Code

wiki-query

Read in this order, stop early

Cost discipline is the feature. A vault that has to be read in full to be queried is a folder of files with extra steps.

1. wiki/index.md — the catalogue. Often enough on its own
2. Frontmatter grep — ^(claim|status|n|tags|summary): across the vault. Rank by exact title match, then tag match, then summary match
3. Windowed grep — grep -A 10 -B 2 on the candidates. Fifteen to thirty lines each. Most factual questions die here without a single page being opened
4. Full read — at most 3 pages, at most one hop of links from them

If step 4 does not answer it, the answer is not in the wiki. Say that instead of assembling something plausible from fragments.

Answer

Cite pages with wikilinks. An uncited sentence in an answer is the model talking, and it should be marked as such.

When the answer rests on a claim, state its state and its n. Not as a footnote — in the sentence:

Bullets tracked with higher reach on artifact-anchored posts, rule, n=4. Opening length showed no effect, candidate, n=1 — one run, treat it as nothing.

A user cannot calibrate on an answer that hides how thin the evidence is. This is the single most important line in this skill.

If a relevant claim is retired, say so and give the reason. That is what retired claims are kept for.

File it back

A good answer is a page. Comparisons, syntheses, and connections discovered while answering are worth as much as ingested sources and disappear into chat history by default.

Ask before filing. Then write it, link it, and log:

## [YYYY-MM-DD] query | question -> page created