OKF – the Markdown spec for humans and AI

A new open specification called the Open Knowledge Format (OKF) has been published under the MIT license, representing knowledge as directories of markdown files with YAML frontmatter and an index.md entry point. OKF's creators say the format rests on three rules — one index per bundle, typed frontmatter (concept, howto, reference, decision, metric), and git-native history — so AI agents can parse bundles without adapters, and they cite the Google Cloud Markdown spec as its basis. The spec ships with a validate.sh script and an installable skill for Claude, Codex, and Cursor, with a zero-backend browser validator described as coming soon.

The open spec for knowledge that ships. A directory of markdown files. YAML frontmatter. Three rules. That's the entire format. Your AI agents parse it without adapters, your team reviews it in git, and your docs never rot outside context again. Based on the Google Cloud Markdown spec · MIT licensed ├── index.md ├── what-is-okf.md └── validation-rules.md --- type: concept title: What is OKF --- What is OKF The Open Knowledge Format is a spec for representing knowledge as markdown files. Why this exists Most knowledge formats ask you to learn a schema, install an SDK, and migrate your content into a proprietary store. OKF asks you to keep writing markdown. The spec exists to make three guarantees: - One index, one truth. - Every bundle has an index.md that lists what's inside. Agents don't guess at structure — they read it. - Typed frontmatter. - Each file declares its type concept, howto, reference, decision, metric . Agents route to the right handler without heuristics. - Git-native history. - Diff, branch, review knowledge like code. No proprietary format holds your content hostage. Semver protects your investment. A bundle looks like this index.md — the entry point --- title: My Knowledge Bundle version: 0.1.0 entries: - what-is-okf.md - validation-rules.md --- My Knowledge Bundle Everything an AI agent needs to know about… Validate before you ship Conformance is three rules, so checking it is cheap: run a shell one-liner or the OKF skill’s validate.sh today. A zero-backend browser validator is coming soon. Know your bundle is correct before your agent reads it. How to validate → https://okf.md/validator/ Teach your agent the spec Install a skill that makes Claude, Codex, or Cursor produce conformant bundles. No system prompts, no fragile instructions. The agent ships correct output because it knows the format. Install Skill → https://okf.md/skill/ Ship your first bundle in two minutes. Three files. One command to validate. Zero dependencies.