القائمة
Health-check a knowledge bundle for conformance and drift; optionally auto-fix safe issues.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Portable OKF knowledge bundle for coding-agent memory and LLM wikis. Use when the user wants to start a wiki, ingest a source, query project knowledge with citations, lint for drift, or visualize connections; whenever a repo has a knowledge/ bundle that should inform the task; and when another kb-* skill needs the shared spec, glossary, templates, or trust model.
Ingest a source into the knowledge bundle. Use when the user wants to capture, ingest, file, process, or "add this" — a note, transcript, email, PDF, image, web page, or any raw source — into a knowledge/ bundle, or drops content for processing. Reads the source once, extracts its signal, and integrates it across the bundle under the trust model so knowledge compounds instead of being re-derived per query.
Scaffold a new OKF knowledge bundle in this project — run when starting a wiki or adding a bundle under knowledge/.
Answer from the knowledge bundle. Use when the user asks what they/the project know about something, wants to look something up, explore connections, or compare things that live in a knowledge/ bundle — and when any task would be informed by an existing bundle, consult it here before answering from scratch. Navigates by progressive disclosure and files valuable answers back so the bundle compounds.
Render a knowledge bundle as an interactive graph — native UI where the host supports it, otherwise a self-contained HTML artifact.
| name | kb-lint |
| description | Health-check a knowledge bundle for conformance and drift; optionally auto-fix safe issues. |
| disable-model-invocation | true |
Keep a bundle trustworthy as it compounds by catching drift — the decay a
growing knowledge base accumulates. Two passes: a deterministic conformance check (mechanical,
scripted) and a drift audit (fuzzy, judgment). Run both; report findings by severity. With
fix, repair what is safe.
Run the bundled checker against the target bundle (default knowledge/):
python3 "${CLAUDE_SKILL_DIR}/scripts/conformance.py" <bundle-dir>
It reports ERROR (a hard SPEC §9 failure — no parseable frontmatter,
or a missing/empty type) and warn (soft: broken links, non-ISO log dates). Broken links are
explicitly tolerated by the spec (§5.3) — never a conformance failure.
Completion criterion: the checker has run and every ERROR it reported is listed for the report
(and fixed, if in fix mode).
The checker can't see meaning. Audit the bundle for the ways a compounding artifact rots — this is the legwork that makes lint worth running. Cover every check:
conflicts_with.superseded_by; overviews behind their children.# Citations / Reference.Completion criterion: every check above has been run across the whole bundle and its findings recorded — not a sample.
Present findings grouped by check, each tagged:
Turn coverage gaps into concrete next moves: questions to investigate, sources to
ingest. Append a dated summary (counts + notable findings) to the bundle's
log.md — append-only.
Completion criterion: a severity-grouped report is delivered and a log.md summary appended.
If invoked with fix, repair only what is safe and unambiguous, then re-report what was fixed
vs. what needs a human:
Completion criterion: every safe issue is fixed and every meaning-level issue is flagged (not touched); the re-report distinguishes the two.