okf-gem · docs
Reference

Claude Code plugin

The Claude-native door into the pack.

Install

The okf-gem repository doubles as a Claude Code plugin marketplace, so the whole toolchain installs in two commands inside Claude Code:

/plugin marketplace add serradura/okf-gem
/plugin install okf@okfgem

The plugin has its own landing page at claude.okfgem.com.

The three pieces

PieceWhat it does
okf skillThe companion skill, bundled with the plugin. It is a generated copy of the canonical skill in the gem; a rake task keeps them identical and a test fails on drift, so the plugin can never teach something the gem does not do.
/okf:gemThe front door, and deliberately a thin one: it hands its arguments to the skill unchanged, so the skill's own routing is the whole story and there is no second copy to drift out of step. No arguments: orients on the CLI and the bundle and recommends the highest-value next move without running one. search <query> retrieves an answer the progressive-disclosure way: map, finder, only the winning bodies. doctor installs and verifies the CLI, then doctors the bundle. curate runs the full cycle. produce, migrate, maintain, consume, a CLI verb, or a free-form task each do what they say, and a question-shaped ask ("how do we...", "where is...") is treated as a search first, so the answer comes from retrieved concepts instead of guesswork. Point it at a directory that is not a bundle yet and it offers migrate instead of working through the conformance errors.
Curation hookAfter every Write or Edit inside a bundle, runs okf validate and okf lint and returns the relevant findings as context: every conformance error, plus the warnings and lint findings that concern the edited file.

Why the hook matters

The checks are the CLI's own, so the feedback is deterministic: no LLM decides whether your bundle is legal. The agent edits, the tool judges, the agent sees the findings while the edit is still in its head. That loop is the three-lenses model running automatically.

Staying out of the way

The hook is silent outside bundles, and when the CLI is missing it suggests /okf:gem once per session instead of erroring on every edit. Switching it off needs no config file:

  • OKF_CURATE_DISABLED=1 turns the hook off entirely;
  • OKF_CURATE_QUIET=1 keeps the findings but drops the install suggestion;
  • an <!-- okf-disable --> comment in a file skips curation for that one file.

Versioning

The plugin versions with the gem: the release process stamps the plugin manifest and refuses to ship if it lags. Prefer no plugin? gem install okf && okf skill .claude installs the same canonical skill without the hook, and the skill itself tells the agent to run the same checks after editing. See the changelog for what each release added.

esc
navigate open