菜单
Check that an Open Knowledge Format (OKF) bundle is conformant with the v0.1 spec (§9). Use when asked to validate, lint, or check an OKF bundle, or before committing changes to one. Runs a deterministic Python checker — not an eyeball pass.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Render an Open Knowledge Format (OKF) bundle as a single self-contained, interactive HTML graph (viz.html) — concepts as nodes coloured/sized by type, markdown links as edges, a wiki-style detail panel with rendered markdown plus "Links to" / "Cited by" backlinks, layout switching, per-type filter and search. Use when asked to visualize, graph, preview, or explore an OKF bundle.
| name | validate |
| description | Check that an Open Knowledge Format (OKF) bundle is conformant with the v0.1 spec (§9). Use when asked to validate, lint, or check an OKF bundle, or before committing changes to one. Runs a deterministic Python checker — not an eyeball pass. |
| user-invocable | true |
| argument-hint | [bundle-dir] [--strict] |
| allowed-tools | Bash |
Run the deterministic conformance checker against the target bundle. Default to
the project's .okf/ directory when no path is given.
uv run "${CLAUDE_SKILL_DIR}/scripts/okf_validate.py" $ARGUMENTS
If uv is unavailable, fall back to:
python3 -m pip install --quiet pyyaml && \
python3 "${CLAUDE_SKILL_DIR}/scripts/okf_validate.py" $ARGUMENTS
${CLAUDE_SKILL_DIR} resolves whether this skill runs as part of the okf
plugin or is installed standalone (e.g. via npx skills add), so the checker is
always found alongside the skill.
Interpret the result:
type). The bundle is non-conformant. Fix every one.Exit code is non-zero if any error is present (or any warning, when --strict).
Add --json for machine-readable output (useful in CI).