okf-knowledge — скилл

---
name: okf
description: Create, read, maintain, and visualize Open Knowledge Format (OKF) bundles — directory trees of Markdown "concept" files with YAML frontmatter that link into a knowledge graph. Triggers on `/okf` (and `/okf init|update|query|validate|viz`). Use when asked to capture a project's knowledge as OKF, keep an okf/ bundle in sync after changes, navigate a bundle to answer a question, or when a folder of .md files carries a `type:` frontmatter field (the Google Cloud Open Knowledge Format).
---

# /okf — OKF Knowledge

Open Knowledge Format (OKF) is a vendor-neutral spec ([Google Cloud](https://github.com/GoogleCloudPlatform/open-knowledge-format),
v0.2) for sharing knowledge as plain Markdown. A **bundle** is a directory tree of files where
each non-reserved file is **one concept** (a table, a module, an endpoint, a metric, a
runbook…) with YAML frontmatter, and concepts link to each other to form a knowledge graph. No
SDK, no runtime — just git-versionable text.

v0.2 keeps the v0.1 core (below) and adds optional **provenance, trust, lifecycle, and
attestation** families — see "OKF v0.2 additions" further down. A v0.1 bundle (using
`timestamp` and a body `# Citations` list) stays fully conformant; those are legacy fallbacks
consumers must still accept.

This skill is **command-driven**: the user runs `/okf <subcommand>` and you follow the matching
flow below to build, sync, read, validate, or visualize a bundle.

## Usage

```
/okf                      # smart default: sync the okf/ bundle if it exists, else offer to init
/okf init [path]          # build a new OKF bundle from this project's code + docs
/okf update [path]        # sync the bundle with what changed; fix links, append log.md, validate
/okf query "<question>"   # answer by navigating the bundle, index-first (no full-file dumps)
/okf validate [path]      # run conformance + lint checks
/okf viz [path]           # (re)generate viz.html + graph.mmd
/okf add "<thing>"        # add one new concept and wire its links
```

Default bundle directory: **`okf/`** in the current project (override with `[path]`).

## What to do when invoked

1. Parse the subcommand (no subcommand → **smart default**: if `<project>/okf/` exists run
   `update`, otherwise propose `init`).
2. Resolve the bundle directory (arg, else `okf/`).
3. Run the matching flow below.
4. **Always finish by validating** and fixing every error:
   `python <skill-dir>/scripts/validate.py <bundle> --strict`
   (`<skill-dir>` = this SKILL.md's directory; `scripts/` and `resources/` are its siblings.
   Both `validate.py` and `visualize.py` need PyYAML — `pip install pyyaml`.)