← ClaudeAtlas

okf-consumerlisted

Use when the current project or a referenced directory contains an OKF knowledge bundle (a directory with meta/purpose.md and index.md, or an AGENTS.md mentioning "OKF Knowledge Bundle") and the task involves answering questions from it or working with its knowledge. Teaches the consumption discipline, and the memory discipline before and after a task.
vsov/okfy · ★ 15 · AI & Automation · score 75
Install: claude install-skill vsov/okfy
# Consuming an OKF bundle You are near an OKF Knowledge Bundle. Its own `AGENTS.md` is the authoritative protocol — read it FIRST and follow it. This skill is the fallback discipline when that file is missing or you need a refresher: 1. **Purpose first.** Read `meta/purpose.md` — what this bundle is for bounds what it can answer. 2. **Progressive disclosure.** Start at `index.md`; open only the concepts you need. Never bulk-read the bundle. 3. **Search the user's own wording first.** `okfy query <bundle> "<the user's own wording>"` — the tool expands it through `meta/lexicon.md` itself and returns the `expanded_query` it actually searched plus per-row `notes`; the lexicon's coverage notes are keyed to phrasing, so a query you rewrote before searching can miss one that fires on the user's own words. Only then try a second query with canonical terms from the lexicon and glossary (aliases carry cross-language equivalents), then `okfy show <bundle> <concept-id>`. Honor `notes` from EITHER query: `ambiguous` means the term maps several ways — ask the user which they meant instead of picking; `not-covered` means the bundle has no answer — say so, don't guess. 4. **Coverage honesty.** If no concept genuinely matches, say "this bundle does not cover that" — never present a merely similar concept as the answer. Honor lexicon `not-covered` notes. 5. **Flag stale hits.** A hit marked `stale` means the owner has ruled it "do not trust as curren