synthesis-okf

Google's Open Knowledge Format (OKF v0.1, announced 2026-06-12) formalizes a pattern many "LLM wiki" knowledge bases already use: a directory tree of markdown files with YAML frontmatter, readable by any agent that can cat a file, shippable by anyone who can git clone a repo. Per the spec's own §10, this is exactly the pattern OKF names as one of its target use cases — the differentiator is only that it's now specified.

Google's reference repo (github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf) ships an enrichment agent and an HTML visualizer, but no conformance validator or converter. This skill fills that gap: a conformance validator, a converter, a house-consistency checker, and a procedure proven across several real-world repo conversions.

The spec, in brief

A bundle is a directory (conventionally a repo's source/ directory, or the whole repo for a dedicated knowledge repo). A concept is one markdown file: one unit of knowledge. Conformance (§9) has exactly three hard rules: