| name | kb |
| description | Portable OKF knowledge bundle for coding-agent memory and LLM wikis. Use when the user wants to start a wiki, ingest a source, query project knowledge with citations, lint for drift, or visualize connections; whenever a repo has a knowledge/ bundle that should inform the task; and when another kb-* skill needs the shared spec, glossary, templates, or trust model. |
kb — bundles
Hub for the kb-* family: vocabulary, shared reference, routing. Knowledge compounds —
compiled once, kept current, not re-derived per query. Does not modify a bundle — routes to the
skill that does.
Key terms
reference/glossary.md defines the vocabulary. Minimum before routing:
Bundle, Ingest, Progressive disclosure, Trust model (see
trust-model.md).
The one hard rule
A bundle is conformant iff every non-reserved .md file has parseable YAML frontmatter with a
non-empty type. Everything else is soft guidance — consumers MUST tolerate missing optional fields,
unknown types, and broken links. Never reject a bundle over them. Full rules:
reference/SPEC.md §9.
Route to the right skill
| The user wants to… | Use |
|---|
| Start a new bundle | kb-init |
| Capture, ingest, file, or process a source (note, transcript, PDF, image, URL) | kb-ingest |
| Ask what the bundle knows; look something up; explore connections | kb-query |
| Health-check the bundle (drift, orphans, contradictions, conformance) | kb-lint |
| See the bundle as a graph | kb-visualize |
If a knowledge/ bundle exists and would inform the current task, consult it via
kb-query before answering from scratch — even when the user didn't ask an
explicit knowledge question.
Shared reference (single source of truth)
Every kb-* skill reads these rather than restating them, so the family stays consistent:
