Knowledge Dashboard

Render a self-contained HTML dashboard for a bound cogni-knowledge base. This skill runs the vendored render_dashboard.py (and, for --graph, build_graph.py) from scripts/vendor/cogni-wiki/skills/wiki-dashboard/scripts/ natively against the bound wiki — resolved vendored-first via resolve_wiki_scripts(), the same posture knowledge-ingest uses for its engine helpers — then writes one extra markdown file (knowledge-overlay.md) that surfaces what binding.json knows but the bare wiki dashboard does not: which research projects have contributed, and what the latest lint audit said about claim drift. A standalone Karpathy base renders its dashboard with no cogni-wiki plugin installed.

The cogni-knowledge value-add over a raw wiki-dashboard render is:

1. Binding-aware wiki path resolution — no --wiki-root from the user.
2. Knowledge overlay sidecar — a markdown file co-located with wiki-dashboard.html that captures the binding view: a deposited-projects table with per-project inverted-pipeline depth (sub-questions, fetched/unavailable, distilled concepts + claim-dedup ratio, verifier verdicts), a knowledge-base-global fetch-cache health block, and the latest lint-audit summary.

Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once per session to remember the boundary — this skill writes only one file (knowledge-overlay.md); the HTML render (wiki-dashboard.html / wiki-graph.html) is the vendored dashboard scripts' responsibility.

When to run

• User asks for a dashboard or HTML view of a bound knowledge base
• After several pipeline deposits, to see the shape of the accumulated wiki
• Before sharing a knowledge base with a colleague — the dashboard + overlay are both single files

Never run when