okf
Be the expert on Open Knowledge Format (OKF) — portable project knowledge as a directory of markdown files with YAML frontmatter that humans and agents read from one source. Use when capturing knowledge into a bundle (a service, schema, metric, decision, runbook: "document this in OKF", "capture this as a concept"), converting existing docs into one ("migrate/OKFy our docs into a bundle"), retrieving from one without reading it whole ("what do we know about X?", "where is X documented?", "search the bundle"), updating one after code or docs change ("update the knowledge bundle"), checking its
npx skills add serradura/okf-gem --skill okf --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Open Knowledge Format (OKF) You are the OKF expert in this repository. OKF is **knowledge as code**: a directory of markdown files, each with YAML frontmatter, that both humans and agents read from the same source. It is minimal on purpose — no schema registry, no runtime, no SDK. All the power lives in *conventions* and *judgment*, not in enforcement. This skill is where that judgment lives; the `okf` CLI handles the mechanics. Two ideas govern everything: - **Dual audience.** Every file must serve a human skimming it *and* an agent extracting from it. That is why bodies are structural markdown and links are plain markdown links — both readers already understand them. - **The graph is emergent.** Files are nodes, markdown links are edges. You never declare a graph; it arises from how you link concepts. Good linking *is* good knowledge modelling. ## The hard rules (§9 conformance) Three conditions, all hard — `validate` fails a bundle on any of them: 1. **§9.1** every non-reserved `.md` file has a parseable YAML frontmatter block; 2. **§9.2** every such block has a **non-empty `type`**; 3. **§9.3** every reserved file present is well-formed — a nested `index.md` has no frontmatte
- The hard rules (§9 conformance)
- Three lenses — hold them separate
- The CLI is your eyes — you are the judgment
- Orient before you touch anything
- The authoring verbs — the craft
- Commands
- The lifecycle is a flywheel, not phases
What does the okf skill do?
Be the expert on Open Knowledge Format (OKF) — portable project knowledge as a directory of markdown files with YAML frontmatter that humans and agents read from one source. Use when capturing knowledge into a bundle (a service, schema, metric, decision, runbook: "document this in OKF", "capture this as a concept"), converting existing docs into one ("migrate/OKFy our docs into a bundle"), retrieving from one without reading it whole ("what do we know about X?", "where is X documented?", "search the bundle"), updating one after code or docs change ("update the knowledge bundle"), checking its
How do I install it?
Run `npx skills add serradura/okf-gem --skill okf --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From serradura/okf-gem, a repository with 118 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.