About kb
A routing and reference hub for the `kb-*` skill family, defining shared vocabulary and bundle rules. It directs tasks to the appropriate skill and does not modify bundles itself.
Key features
- 01Routes tasks to `kb-*` skills
- 02Defines shared bundle vocabulary
- 03States bundle conformance requirements
- 04Provides shared specifications and templates
Use cases
- 01Choosing a skill for a knowledge-bundle task
- 02Checking bundle conformance expectations
- 03Finding shared terms and reference materials
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/kbin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
example-bundle/index.mdlog.mdexample-bundle/concepts/customers.mdorders.mdexample-bundle/references/sample_sales_data.mdexample-bundle/spec/conventions.mdtypes.mdreferences/glossary.mdSPEC.mdtrust-model.mdversion-profile.mdtemplates/concept.mdindex.mdlog.mdDetails
From the project READMEkb — 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
references/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:
references/SPEC.md §11.
The domain portion of spec/types.md is a living, producer-chosen vocabulary, not a validation
enum. Keep the workflow conventions Reference and Spec Section; start the domain types small
and evolve them through kb-ingest or
kb-document when the domain reveals a durable new kind of entity. Use
kb-lint to detect schema drift.
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 |
| Document a repository, explain its architecture/workflows, or refresh knowledge after code changes | kb-document |
| 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:
- references/SPEC.md — OKF v0.2, vendored verbatim.
- references/version-profile.md — v0.2 production and v0.1 compatibility rules; every writing skill reads it before changing a bundle.
- references/glossary.md — leading words and definitions.
- references/trust-model.md — the maintenance rules.
- templates/ —
concept.md,index.md,log.mdstarters. - example-bundle/ — a tiny conformant bundle: a worked example, and the seed
kb-initcopies from.