agentsclimarketplace

Okf validate

Skill shreytam/okf-toolkit/skills/okf-validate

Claude Code plugin: author, explore, validate, and visualize Google's Open Knowledge Format (OKF) v0.1 bundles.

Install
npx -y skills add shreytam/okf-toolkit --skill okf-validate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Validate a directory against the Open Knowledge Format (OKF) v0.1 conformance rules using a bundled checker script. Use this skill whenever the user asks to validate, lint, check, or verify an OKF bundle, asks "is this bundle conformant/valid", wants a conformance report before publishing or sharing a knowledge bundle, or asks why an OKF bundle isn't being consumed correctly by an agent.

SKILL.md

2.1 KB, 415 tokens by cl100k_base, as published. Nobody here has run it

Validating OKF Bundles

Run the bundled conformance checker:

(scripts/validate_okf.py lives under this skill's base directory — use its absolute path, since the shell's working directory is elsewhere.)

python3 <skill-base-dir>/scripts/validate_okf.py <bundle-dir>

Exit 0 = conformant, 1 = errors. It checks the three hard rules from spec §9 and emits soft warnings.

Interpreting results

Errors (must fix — bundle is not conformant):

  • A non-reserved .md file with no parseable YAML frontmatter.
  • Frontmatter missing a non-empty type field (the only required field).
  • Reserved-file misuse: frontmatter in log.md, or frontmatter in an index.md outside the bundle root (the root index may carry only okf_version).

Warnings (judgment calls — report, don't auto-fix without asking):

  • Broken internal links: legal per spec §5.3 (they can mark not-yet-written knowledge). Flag them; fix only typos, e.g. a link that almost matches an existing file.
  • Missing title/description: recommended, not required. Offer to fill them in — descriptions feed index generation and search snippets.
  • log.md without ISO ## YYYY-MM-DD headings; index files without links.

Reporting

Give the user: conformant or not, concept/file counts, each error with the file path and the concrete fix, and warnings grouped by kind with a recommendation. If the user wants fixes applied, make the minimal edits (preserving unknown frontmatter keys) and re-run the checker to confirm it passes.

For spec details behind any rule, see references/okf-spec.md. For authoring new bundles use okf-author; for navigating/querying use okf-explore.

What ships with it: 2 files

20.1 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.