Renders the read-only capability inventory from the committed capabilities.yaml manifest.
npx skills add https://github.com/Kemetra/Seshat-BI --skill capabilities-kemetra
Please help me install this Agent Skill. Skill: capabilities Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/capabilities Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill capabilities-kemetra
docs/capabilities/capabilities.yaml and reconciles it against the _DISPATCH command table, skill frontmatter, kit-source verbs, roadmap ship status, and status-claims records. - Two output formats: Produces a grouped human-readable read by default, or a stable deterministic JSON form via --format json for machine consumption. - Strictly read-only: Writes nothing, connects to no database, emits no scores, and never acts as a gate or readiness surface. - Use Case: A new contributor asks which parts of the retail-to-Power-BI pipeline work without a database; run the module and relay its grouped output showing each capability by lifecycle state, authority, requirements, and provenance. ## Quick Start Ask the assistant to run the capability inventory by executing python -m seshat.capability_inventory from the repository root and show the grouped output.High-intent search queries and answers about installing and using this skill.
Run python -m seshat.capability_inventory from the repository root to get a grouped human-readable inventory of every capability. Add --format json for a stable, deterministic machine-readable form.
The capability inventory shows each capability's requirements and lifecycle state, so you can see which ones need no database connection. The skill itself is read-only and never connects to a database or runs Power BI.
No, and none should be added. A ratified decision (docs/roadmap/decisions/cli-verbs-vs-skill-driven.md, Option B) keeps this as a module invocation only; do not modify the CLI parser or _DISPATCH table to wire it up.
No. It is not a gate, adds no seshat check rule, and never blocks anything. For per-table readiness use seshat status, for the next action use seshat next, and for the governance gate use seshat check.
It reads the committed manifest docs/capabilities/capabilities.yaml and reconciles it against the _DISPATCH command table, SKILL.md frontmatter, kit-source verbs, roadmap ship status, and status-claims records, never inferring truth from a file's mere existence.
ByeongminLeeAlign investor-facing materials around a single source of truth.
phj128Read subtask.md state and route execution to the next autoworker skill.
reopt-aiManages Brandapp CLI workflows for linking, health checks, and sandbox environments.
diegosanchespereira1Summarize sprint status and recommend the next BMad workflow action.