Claude Skills by Kemetra

Package a raised judgment call into a reviewable decision package, then record a named human's answer into the committed readiness artifacts. Use for sign-off packaging or recording a decision. It only transcribes a decision a human supplied.

Assemble a reviewable evidence pack behind a readiness approval in the Seshat BI repo. Use when someone asks to package the evidence for a stage sign-off. Read-only: it collects committed evidence and never grants the approval.

After a database is discovered and profiled, interview the business owner to capture the meaning-critical decisions the rest of the Database-to-PBIP flow depends on -- KPI meaning, PII handling, table grain, primary keys, relationships, missing-value rules, and ambiguous financial/quantity/date columns -- and record every outcome in the project Decision Store. Use when someone asks to run the interview, capture business knowledge, or resolve the business questions behind a model in the Seshat...

Show the read-only capability inventory for this kit -- each capability by lifecycle state, authority, requirements and provenance. Use when someone asks what the kit can do or what works without a database. Writes nothing and emits no score.

Generate a consumer-facing data dictionary from committed gold-layer artifacts and approved metric contracts. Use when someone asks for a data dictionary or column glossary for report users. Authors documentation only and invents no business meaning.

Trace column- and table-level lineage across bronze/silver/gold in the Seshat BI repo and report the downstream impact of a change. Read-only: it reads committed SQL and mappings, opens no database, and edits nothing.

Run the medallion sequence UNATTENDED / in CI as a Dagster asset graph -- the scheduler sibling of the retail-orchestrate conductor -- running ONLY already-approved steps behind every gate, and recording what each asset DID as DERIVED run-evidence. Use when someone asks to schedule the pipeline, run the medallion in CI, "orchestrate unattended", or wire Dagster in the Seshat BI repo. Dagster RUNS approved steps; Tower BI (the gate exit code + the named human) decides whether a stage passed. T...

Design a Power BI dashboard FROM approved metric contracts in the Seshat BI repo. Use when someone asks to design a report/page, bind visuals to metrics, or produce a dashboard layout for a subject area whose semantic model is ready. This skill is HARD-GATED on semantic_model_ready: pass (no approved metric contracts -> no design); it authors reviewable design guidance only -- a layout plan, a visual list, and a visual->contract binding map where every visual binds to exactly one approved con...

Coordinate the SHIPPED Seshat dashboard capabilities into one governed journey (spec 123, US2) -- from an APPROVED Report Intent through gap/duplication checks, contract-bound design, report composition, and dashboard QA, STOPPING at the human blueprint review. Use when someone asks to "build/design the dashboard end to end", "coordinate the dashboard work", or drive a subject area from an approved intent to a reviewable design in the Seshat BI repo. The AGENT is the runtime: this skill inspe...

Run dbt as the build ENGINE for silver/gold ONLY behind the Mapping Ready gate, and record its run/test/parity output as DERIVED evidence -- never as an approval. Use when someone asks to build silver/gold for a mapped table with dbt, run dbt tests, or check dbt parity against the existing gold tables in the Seshat BI repo. dbt is the engine; Seshat BI is the brain. This skill READS the approved map, EXECUTES approved dbt steps behind the gate, and WRITES evidence; it never defines meaning, n...

Compose a single readable 10-section evidence pack for a table/report at the late readiness stages (Semantic Model Ready -> Dashboard Ready -> Publish Ready) in the Seshat BI repo. Use when someone asks to "assemble the evidence pack", "gather everything for the data-owner sign-off", or "show the full late-stage evidence for this table". This is a Product Module, artifact-writing: it READS the already-committed upstream artifacts, renders the ordered 10-section pack index + one-page summary, ...

Show a NEW-table author the stateful "you are here / next artifact / authoring skill" orientation card for ONE table in the Seshat BI repo. Use when someone asks "where is this table in the readiness journey", "what do I do next for <table>", or "orient me on a new table". READ-ONLY and invoke-and-present only: it parses that table's mappings/<table>/readiness-status.yaml and RENDERS a single-table orientation card (current stage, the next non-pass stage + the artifact it needs + the authorin...

Render a PLAIN-LANGUAGE narrative summary of one PR's already-produced governance review -- what changed, which readiness stages are pass/warning/blocked (verbatim), which findings are NEW/RESOLVED/pre-existing (when a base identity set is supplied), who must approve, and exactly one next action. Use when someone asks "explain this PR in plain language", "what does this review envelope actually mean", or wants a non-technical summary of a PR's governance findings WITHOUT opening JSON/YAML. It...

Surface grain-uniqueness CONFIDENCE as evidence and DIFF two source-map.yaml versions for a Mapping Ready reviewer in the Seshat BI repo. Use when someone asks "is the grain confident?", "what changed in this map?", or is about to review/approve a table's mapping. It READS the already-measured PK-uniqueness signal (PkProof from profile.py / the committed source-profile.md) and reads two map versions from git, then RENDERS a grain-confidence card + a semantic diff and STOPS for the human. "Con...

Help a human turn a named-but-planned retail KPI into a governed, owner-ready project metric-contract by driving the shipped kpi_contracts engine (spec 124). On first contact, when no approved decisions exist yet, it assesses source answerability, lists the exact Decision Store decisions to get approved via business-knowledge-interview, and renders a preview with per-field provenance -- writing no YAML. Once the approved kpi_definition / policy_ruling decisions, a named eligible owner, and co...

APPLY an already-approved Power BI semantic-model change through Microsoft's official Power BI Modeling MCP, behind Seshat's recorded named-human approval -- closing the governed last mile so the change is not applied by hand in Desktop with nothing recorded. Use when someone asks to apply, push, or publish an approved model edit, to run `seshat pbi-mcp apply` / `plan-write`, or asks why a write was refused. This adapter EXECUTES a decision Core Authority already made: it reads COMMITTED appr...

The git-based workflow for Power BI Project (PBIP) files — saving reports as plain-text TMDL/PBIR, what to commit vs ignore, and the Windows gotchas. Use this whenever someone is putting Power BI under version control: saving a report to git, choosing PBIP vs .pbix, editing TMDL or DAX as text, reviewing a semantic-model change in a PR, or troubleshooting why a .pbi folder, cache, or localSettings is (or isn't) showing up in git. Also use when "Save as PBIP" is missing, when PBIP diffs look n...

Audit a committed PBIP semantic model as text (unused fields, relationship risks, measure-graph findings) and explain a TMDL change in business terms for PR review. Read-only: it parses committed TMDL/PBIR and git history, opens no database, never launches Power BI, and edits nothing.

The Power BI report-AUTHORING adapter (F034 completion). Use when someone asks to apply a generated theme to a committed PBIR report, or (later increments) to set visual formatting or a page background by writing the report's PBIR JSON directly -- the settings a human sets by hand in the Power BI UI. This is a COMPANION execution/authoring adapter (the F029-dbt / F030-Dagster pattern), NOT part of the static DEFINE/CHECK core. It writes committed PBIR JSON within a tight allow-list, determini...

Show the recurring, read-only portfolio summary for the Seshat BI repo -- every governed scope's covered-dimension findings (source drift, contract/metric drift, dashboard-intent divergence, readiness, approvals, review), open blockers, human-attention flag, and ONE prioritized next action, plus a baseline diff against the last run (new/resolved/unchanged). Use when someone asks "run portfolio watch", "what changed since last week", "show me the recurring summary", or "which scopes need a hum...

The Power BI VISUAL/DESIGN layer of the Tower BI Readiness System. Use when someone asks about dashboard design, page layout, a background/canvas asset, a theme/colors choice, a screenshot critique, a mobile layout, or a Power BI handoff in the Seshat BI repo. This skill ROUTES a design request into exactly ONE of four surfaces (report visuals, external background/canvas, theme JSON, implementation handoff) and opens the matching workflow. It is a router and a vocabulary, not a builder: it ne...

Render ONE structured "is this PR safe to merge" verdict for a single pull request in the Seshat_BI repo -- merge_ready (yes/no) + blockers[] + warnings[] + required_human_decisions[] + evidence[] + one next_action. Use when someone asks "is this PR ready to merge?", "what blocks this PR?", or "review this PR for promotion". It OBSERVES the PR's state (open/draft, mergeable, CI/workflow conclusions, open review threads, unresolved Codex/GitHub review comments) and READS the committed readines...

Show the stage-centric readiness lens across the kit's sources / tables / reports -- one per-stage status MATRIX over the seven readiness stages, each stage's evidence rendered as NAVIGABLE REFERENCES, and an approvals TIMELINE, read from each item's readiness-status.yaml. Use when someone asks "show the readiness viewer", "which stage is each table at", "what evidence backs Gold Ready", or "who approved this gate, and when". READ-ONLY and invoke-and-present only: it RENDERS the recorded stat...

Draft an evidence-backed per-release note and assess the kit's honest maturity ladder for a shipped roadmap slice in the Seshat BI repo. Use when someone asks to "generate the release notes", "what maturity level is the kit at", "assess the kit's maturity", or "record what became possible in this release". This is Maintenance Automation (F024): it runs as the conductor's post-milestone read, not per a per-run human trigger. It READS the F028 evidence pack + the F032 compatibility matrix + the...

Given approved metric contracts and a ready semantic model, interview the report requester to capture what a dashboard report is FOR -- audience, purpose, supported decision, review cadence, primary business questions, outcome/driver/guardrail metrics (referenced by name only, never defined), comparisons, dimensions/filters, expected actions/exceptions, pages/drill paths, and mobile/accessibility/language/RTL needs -- and record the result as a committed Report Intent artifact plus a named-hu...

Author the silver + gold migration SQL for a mapped retail table from its APPROVED source-map, then STOP before executing. Use after a table's mapping gate is CLEARED in the Seshat BI repo and someone asks to build the silver/gold SQL, write the migration, or fill the retail-orchestrate build seam. Author-and-stop: it writes warehouse/migrations/*.sql FILES only, never connects to a database, never applies the SQL, and HARD-STOPS at any judgment call the map does not already answer.

Show the consolidated, cross-table data-quality control room for the Seshat BI repo -- one worst-first roll-up of every table's stage, status, static WARNs, live findings, open blockers, and next action, plus a portfolio-wide open-blockers list. Use when someone asks "show the control room", "what is broken across all tables", or "which table do I fix next". READ-ONLY and invoke-and-present only: it AGGREGATES evidence that already exists (per-table readiness-status.yaml / data-issues.md / bl...

Discover an unfamiliar retail data portfolio before per-table onboarding. Produces one metadata-only Layer-A survey across every reachable table, proposes non-critical domain and first-delivery scope decisions, delegates selected tables to retail-onboard-table for Layer-B profiling, and hands off to the existing business-knowledge-interview. Never samples source values, self-confirms a decision, or advances beyond the interview handoff.

Run the Seshat BI governance checker and interpret its findings. Use when someone asks to check, validate, or gate Power BI / DAX / TMDL / PBIR / SQL work in the Seshat BI repo, when `seshat check` reports a rule violation, or when you need to know what a rule id (D8, C2, S2, G1, …) means and where to fix it. Invoke-and-interpret only: this skill does NOT build models, run pbi-cli, or auto-fix — it runs the checker and maps ids to fixes.

Bootstrap the Compass-Driven kit and lead a NEW user to a first visible result on THEIR own table in the Seshat BI repo. Use when someone asks to "set up the kit", "initialize seshat", "onboard me / get me started", or runs `retail init`. The AGENT performs this: it writes the backstage substrate (compass router + fenced AGENTS.md/CLAUDE.md regions + manifests) via the substrate-only `retail init` CLI, DELEGATES the worked-example offer + human-seam list to `first-hour-compass`, and ROUTES in...

Walk a NEW raw retail table across the FIRST readiness transition -- Source Ready (Stage 1) through Mapping Ready (Stage 2) -- and seed its per-table readiness-status, in the Seshat BI repo. Use when someone says "onboard <schema>.<table>", "take this new table from nothing to a reviewed map", or "start the readiness journey for a table". This is the stage-transition FRONT DOOR: it sequences profile -> map -> gate, writes the readiness-status record, and STOPS at Mapping Ready. It DELEGATES t...

Drive a retail table through the medallion sequence (profile -> map -> gate -> build -> validate -> Power BI) by composing the existing verb-skills, and self-heal against the governance gate's exit code. Use when someone asks to take a table end-to-end, "orchestrate", "run the whole pipeline", or drive the medallion playbook in the Seshat BI repo. The AGENT is the runtime: this skill sequences and instructs; it never spawns a loop runtime, never self-grants the mapping approval, and HARD-STOP...

Scaffold the per-table artifact skeletons a retail table needs in the Seshat BI repo. Use when someone asks to create the mapping or readiness files for a new table. It writes empty templates only and answers no judgment call.

Compute the Semantic Model Ready (Stage 5) readiness verdict for a committed Power BI PBIP model in the Seshat BI repo. Use after Gold Ready is `pass`, when someone asks whether the semantic model is ready, to check that every measure binds to an approved metric contract, or before any dashboard/PBIP work. READ-ONLY and invoke-and-interpret only: it runs the existing `seshat check` gate, reads the committed TMDL and the filled metric-contract store (F009), and emits ONE status (not_started | ...

Run the LIVE data checks against a materialized retail table and interpret the findings. Use after silver + gold exist for a mapped table in the Seshat BI repo, when someone asks to validate or reconcile a table, or when a V-RC2 / V-RC15 / V-RC16 finding appears. Invoke-and-interpret only: this skill runs `retail validate` against a live Postgres DB and maps each finding id to its fix. It does NOT build models, write SQL, or auto-fix.

Advance one table by one readiness stage in the Seshat BI repo: run the next required step, then stop. Use when someone asks what is next for a table and to do it. Never self-grants an approval and never marks a stage pass without its evidence.

Open Seshat Studio, the local analyst console for ONE Seshat workspace, when someone asks to "open Studio", "show me the workspace", "launch the console", or wants to see readiness, tables, and approvals in a browser instead of a terminal. Studio serves a single pinned workspace on loopback only, reads recorded state, and stops at the same human approval gates as every other Seshat verb. It NEVER grants an approval, advances a stage, writes a pass, invents evidence, or emits a numeric readine...

Compose a shareable, disclosure-safe, OFFLINE proof bundle of Seshat BI's committed readiness truth -- stages, evidence, blockers, approvals, next actions, metric lineage, a truthful badge/project card, and a four-category disclosure manifest -- for a maintainer or analyst to hand to a reviewer, stakeholder, or prospective contributor. Use when someone asks for a "shareable proof", a "showcase bundle", a "project card", or "something I can send to show what Seshat has governed here". This is ...

Drive a raw retail source table through the source-mapping gate before any silver SQL exists. Use when someone asks to map, model, profile, or onboard a new bronze table toward Power BI in the Seshat BI repo -- profile the source, decide grain/PK, fill the five mapping artifacts into mappings/<table>/, and stop at the gate. This skill ENFORCES the rule that no silver.* SQL is written until the map is reviewed and approved. It profiles and authors and stops; it does NOT write silver/gold SQL a...

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Create or update the feature specification from a natural language feature description.

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Use Seshat's public analyst-judgment knowledge to derive decision-questions, choose an analytical framing, and order a story from approved metric contracts and a committed source-profile.

Use Seshat's public big-data knowledge for distributed aggregation, partitioning, joins, skew, idempotency, reconciliation, performance, and cost reasoning.

Use Seshat's public DAX knowledge for metric contracts, evaluation context, measure review, performance reasoning, and semantic-model prerequisites.

Use Seshat's public Python knowledge for governed single-node source preparation, cleaning, grain, and aggregation reasoning.

Use Seshat's public SQL knowledge for source grain, joins, aggregation, validation, reconciliation, and transformation reasoning without executing a database.

Route Dagster intent to Seshat's governed medallion workflow or the official Dagster competence owner without bypassing readiness, approvals, or evidence.

Route dbt intent to Seshat's governed shadow workflow or the official dbt Labs competence and execution owner, without bypassing readiness or evidence.

Use when a user asks whether or how to wire Microsoft's official Power BI MCP servers into a Seshat BI workspace: run the read-only environment doctor, map a task to the governed Power BI surface (including the official report-authoring skill), generate a safe read-only config template, or run the mocked read-only preflight.