kpi-contract-builder

Drafts governed retail KPI metric contracts by driving the kpi_contracts engine with approved decisions.

2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Kemetra/Seshat-BI --skill kpi-contract-builder-kemetra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kpi-contract-builder
Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/kpi-contract-builder
Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill kpi-contract-builder-kemetra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a planned retail KPI into a governed, owner-ready metric contract requires approved business decisions, a named owner, and committed source evidence; this Skill orchestrates that two-trip flow without inventing business meaning or skipping human approvals. ## Core Features & Use Cases - First-Contact Assessment: Evaluates source answerability for a planned KPI, renders a preview with per-field provenance, and lists the exact Decision Store decisions to approve before writing anything. - Engine-Driven Drafting: Calls draft_project_metric_contract once approved kpi_definition and policy_ruling decisions, a named eligible owner, and committed source evidence exist, producing a gold-blocked contract. - Controlled Finalization: Invokes finalize_project_metric_contract after the gold binding is materialized, promoting readiness to pass only when every precondition holds. - Use Case: A user asks to start a metric contract for Inventory Turnover, which the registry marks planned; the Skill identifies missing COGS and inventory snapshot roles, emits the decision-gap list routed to business-knowledge-interview, and stops without writing YAML. ## Quick Start Ask the agent to draft a metric contract for a planned KPI such as Inventory Turnover in the Seshat BI repo.

Frequently Asked Questions about kpi-contract-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a metric contract for a planned retail KPI?▼

First run the assessment trip: resolve the KPI's registry reference, read its blockers and source roles, and check the Decision Store for approved kpi_definition and policy_ruling decisions. Only after those decisions, a named owner, and committed source evidence exist does the Skill call draft_project_metric_contract.

What is a metric contract in the Seshat BI kpi_contracts stage?▼

A metric contract is a governed YAML artifact binding a KPI's business definition to source evidence and decision references. Drafted contracts start with readiness status blocked until the physical gold binding is materialized and finalize_project_metric_contract promotes them to pass.

Can I create a contract for a custom KPI not in the registry?▼

Yes, custom KPIs are supported with custom: true and no registry reference, but every meaning field starts as a gap requiring approved decisions. The owner must be named in Name (authority_class) form, and the Skill never promotes the custom KPI into the product registry.

Why does draft_project_metric_contract raise ContractDraftRefused?▼

The engine refuses drafting when an approved kpi_definition decision, applicable policy_ruling decisions, a named eligible owner, or committed source evidence is missing. Resolve these through business-knowledge-interview first, then retry the draft.

Does this Skill generate DAX or SQL for the KPI?▼

No, it never writes DAX, SQL, or silver and bronze bindings into any field. DAX generation belongs to retail generate and semantic model checks belong to retail semantic-check, which are separate stages.