Validate
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.From its SKILL.md
npx -y skills add scaccogatto/okf-skills --skill validateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- runs commandsInstructs the agent to run 2 commands, including `uv run "${CLAUDE_SKILL_DIR}/scripts/okf_validate.py" $ARGUMENTS` and 1 more.
SKILL.md
1.4 KB, 294 tokens by cl100k_base, as published. Nobody here has run it
Validate an OKF bundle
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:
- ERROR → a hard §9 conformance failure (no parseable frontmatter, or a
missing/empty
type). The bundle is non-conformant. Fix every one. - warn → soft guidance (missing recommended field, non-ISO log date, broken cross-link). Never blocks; broken links in particular are explicitly tolerated by the spec (§5.3). Fix when cheap.
Exit code is non-zero if any error is present (or any warning, when --strict).
Add --json for machine-readable output (useful in CI).
What ships with it: 1 file
24.7 KB alongside SKILL.md, 1 of them executable
scripts/
- okf_validate.pyruns24.7 KB