okf-create-bundle

Create an OKF bundle

Scaffold a new Open Knowledge Format (OKF) bundle: a directory of interlinked markdown files that form a portable, vendor-neutral "brain." This skill covers the folder layout, the build process, and the definition of done. It is domain-agnostic — the same structure serves a gardening brain, an academic brain, or a company wiki.

If the repo already contains an okf-gold-standard.md, treat it as the fuller source of truth and follow any project-specific extensions it records. This skill is the self-contained version.

What an OKF bundle is (the mental model)

• Just files, just markdown, just YAML frontmatter. No database, no runtime, no proprietary SDK.
• Each file is one concept / unit of knowledge. The file path is the identity of that node.
• Nodes interlink with ordinary markdown links, forming a knowledge graph an agent can traverse.
• Read index.md first. An agent opens the index (progressive disclosure), finds the few files relevant to its task, and opens only those — it never loads the whole bundle. This is why nodes can and should carry MAXIMUM detail: findability is the index's job, not the reader's.
• The index replaces RAG / embeddings as the retrieval layer. Retrieval is by curated navigation, not vector search — transparent, deterministic, auditable, and needs no embedding store. Index-first navigation works well up to roughly a few hundred nodes; beyond that, keep the index but add an on-device search pass (BM25 + optional local vectors, with LLM re-ranking) — still local, still no cloud embedding infrastructure.
• A brain is a compounding artifact, not a one-shot export. The tedious part of a knowledge base is the bookkeeping — updating cross-references, spotting contradictions, keeping the index current — which is exactly what an agent does tirelessly. Humans curate sources and direct the work; the agent maintains the graph. Value accrues every time a source is ingested or a good answer is filed back.