okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a repository contains an `.okf/` (or other OKF) bundle that should inform the task. Triggers on: "document this in OKF", "update the knowledge bundle", "capture this as a concept", or any work in a repo that has an OKF bundle.
npx skills add scaccogatto/okf-skills --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) 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.2 specification and the source of truth for every rule below. ## The one hard rule A bundle is conformant (§11) 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` 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). Co
- The one hard rule
- Conventions to apply
- The v0.2 families (all optional, all worth filling)
- Default bundle location
- Modes
- produce — create or extend a bundle
- maintain — keep a bundle in sync with reality
- consume — use a bundle as context
- Validation (do this before declaring done)
uv run "${CLAUDE_SKILL_DIR}/scripts/okf_init.py" <target-dir> [--title "..."]
uv run "${CLAUDE_SKILL_DIR}/../validate/scripts/okf_validate.py" <bundle-dir> --strictWhat does the okf skill do?
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a repository contains an `.okf/` (or other OKF) bundle that should inform the task. Triggers on: "document this in OKF", "update the knowledge bundle", "capture this as a concept", or any work in a repo that has an OKF bundle.
How do I install it?
Run `npx skills add scaccogatto/okf-skills --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 scaccogatto/okf-skills, a repository with 229 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.