okflisted

# Open Knowledge Format (OKF) skill OKF represents knowledge as a directory of markdown files with YAML frontmatter. It is minimal by design: no schema registry, no runtime, no SDK. Your job is to produce, maintain, and consume OKF bundles **conformant with the spec**, not your memory of it. **Always read the canonical spec before non-trivial work:** [reference/SPEC.md](reference/SPEC.md). It is the verbatim OKF v0.1 specification and the source of truth for every rule below. ## The one hard rule A bundle is conformant (§9) iff: every non-reserved `.md` file has a parseable YAML frontmatter block, and every such block has a **non-empty `type`** field. Everything else is soft guidance. Consumers MUST tolerate missing optional fields, unknown types, and broken links — never reject a bundle over them. ## Conventions to apply - **One concept = one file.** The file path (minus `.md`) is the concept ID. - **Frontmatter:** `type` is required. Add `title`, `description`, `tags`, `timestamp` (ISO 8601) when they aid consumption; add `resource` (a canonical URI) only for concepts bound to a real asset — omit it for abstract concepts. - **Body:** prefer structural markdown (headings, tables, lists, fenced code). Conventional headings: `# Schema`, `# Examples`, `# Citations`. - **Cross-links:** standard markdown links; prefer absolute bundle-relative form (`/services/auth-api.md`). A link asserts a relationship; its *kind* lives in the surrounding prose, not the link. - *