--- name: kdb-table description: Show a repository's knowledge base (its KnowledgeBase entrypoint) to a human as a compact Markdown table of topics, intents and documents. Use when asked what is in the kdb, which topics or intents exist, where a topic routes, what can be passed to `repoctl context`, or for an overview of the knowledge base. Read-only. --- # kdb-table Thin wrapper. The knowledge base is machine-readable and long: reading the whole file to answer "what is in there" is the thing this skill exists to avoid. ```bash python -m stewardship.kdb_table --repo ``` The entrypoint is read from the repository's own `ops/contract.yaml` (`spec.knowledge.entrypoint`), falling back to `kdb/kdb.yaml`, so no path needs to be guessed and the same command works on any adopted repository. If the repository has no knowledge base, it says so and exits cleanly. Print the Markdown it emits as-is; do not paraphrase it. Two tables: - **topics**, by descending `priority`: id, declared intents, the documents the topic routes to, and the top-level keys of its `data` (what facts sit inside); - **documents**: id, path, role, status. `stale` is marked `(!)` - such a document is out of date, and `repoctl context` warns about it when it hands it over. ## When an overview is not what is wanted This answers "what exists". To get only what a specific task needs, take an intent from the Intents column and ask the tool instead: ```bash repoctl context --repo --intent ``` An unknown intent is answered with the closest known ones, so the table is mainly for the human - an agent can afford to guess once. ## Out of scope It neither edits nor validates the knowledge base. Schema conformance is `repoctl validate --repo `; run that after editing the entrypoint.