kb-bootstrap
Installation
SKILL.md
kb-bootstrap
A bootstrap produces one thing: the wiki's initial state plus its pointer. Lifetime management belongs to the owning skill — bootstrap never curates, diagnoses, or maintains; it hands over.
1. Pick the type
| Knowledge | Wiki | Owning skill | Reference |
|---|---|---|---|
| Cross-repo engineering contracts for a multi-session effort (ADRs, decisions, component maps scattered across repos) | effort wiki (okb tree + CONTEXT-MAP) | okb |
okb-effort-wiki.md |
| Bug-diagnosis history worth re-consulting | ops diagnosis vault | diag-write / diag-search |
ops-vault.md |
| Skill-execution knowledge (patterns, impact, run logs) | skills wiki | skill-call-diagnose |
skills-wiki.md |
| Teaching knowledge for courses | teaching OKB | academy |
teaching-okb.md |
| Single-repo code terrain (module maps, file tables) | no wiki — use CodeGraph (codegraph_* tools, always current) plus a CONTEXT.md for hand-curated glossary |
— | — |
The last row is a decision, not a gap: a terrain wiki was tried (one device-plugin repo, 2026-07) and an audit found agents read it only when a gate forced them — CodeGraph serves the same need live. Do not bootstrap one; route the glossary content into the repo's CONTEXT.md.