Knowledge Health

Give the user a fast, grounded structural health verdict for a cogni-knowledge base — the page/link/schema integrity of the bound wiki, plus entries-count drift and claim drift. This is the standalone analog of cogni-wiki:wiki-health, computed natively on the vendored health.py engine (resolved vendored-first via resolve_wiki_scripts()), so a Karpathy base is health-checkable with no cogni-wiki plugin installed.

This skill is fully read-only — health.py writes nothing (it emits JSON to stdout only). The health-check log line the retired cogni-wiki:wiki-health dispatch used to append was a workflow step of that skill, not of the engine; the native path has no append step.

Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once at the start of a session so you remember the wiki-engine boundary — cogni-knowledge computes the health verdict on the vendored wiki-health engine, it does not dispatch cogni-wiki:wiki-health.

When to run

• User asks for a health check, integrity check, or structural verdict on a knowledge base
• Right after a bulk knowledge-ingest or a knowledge-finalize run, to confirm the base is still structurally sound
• Before sharing or publishing a base, as a pre-flight gate
• Proactively when a session opens in a directory containing .cogni-knowledge/binding.json and the user asks "is everything OK?"

Never run when

• The target directory has no .cogni-knowledge/binding.json — offer knowledge-setup instead.