approval-evidence-pack

Assembles committed readiness evidence into a pre-approval pack for one table and stage gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a named human must sign off a readiness stage gate in the Seshat BI pipeline, the evidence they need is scattered across readiness docs, readiness-status.yaml files, metric contracts, and parked-on dependency maps. This Skill composes those committed artifacts into one ordered, reviewable pack without inventing content or granting the approval itself. ## Core Features & Use Cases - Evidence Composition: Collects gate requirements, four-status readiness state, open blockers, unresolved AL1 assumptions, blocking parked-on edges, and pending metric contracts into a single pack at mappings/<table>/approval-evidence-pack-<stage>.md. - Approval Boundary Enforcement: Ends with an empty approval slot (Form A), a read-only recorded approval (Form B), or a not-applicable statement for mechanical gates (Form C); it never writes approvals[] or moves a stage to pass. - Honest-State Handling: Missing or unreadable sources become named blockers rather than fabricated content, and no numeric score or completeness count is ever emitted. - Use Case: Before a metric owner signs the Semantic Model Ready gate for a retail table, run this Skill to produce the full pre-approval pack they review, then hand the decision to the Approval Console. ## Quick Start Ask the agent to assemble the approval evidence pack for table retail_store_sales at the semantic_model_ready stage.

Frequently Asked Questions about approval-evidence-pack

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

FAQPage Schema
How do I prepare evidence for a readiness stage approval in Seshat BI?▼

Invoke the approval-evidence-pack skill with a table and stage; it composes gate requirements, readiness status, blockers, unresolved assumptions, and pending contracts into mappings/<table>/approval-evidence-pack-<stage>.md. The pack ends with an empty approval slot for the named human.

What is the difference between approval-evidence-pack and evidence-pack-generator?▼

approval-evidence-pack (F035) builds a pre-approval pack generic across all seven stage gates, scoped to what one gate needs. evidence-pack-generator (F028) builds a late-stage 10-section pack covering only the Semantic Model to Publish window.

Can the approval evidence pack grant or record a stage approval?▼

No. The skill is structurally incapable of writing approvals[], moving a stage to pass, or defining business meaning. Recording the human's decision is the job of the Approval Console (F027), which runs after this pack is reviewed.

What happens when a readiness-status.yaml or metric contract is missing?▼

The skill records a top-level blocker naming the missing or unreadable path and still renders the pack shell with the approval slot empty. It never fabricates status, self-approves, or proceeds past a missing gate.

Does the approval evidence pack connect to a database or Power BI?▼

No. It reads only committed repository artifacts such as readiness docs, YAML status files, metric contracts, and the parked-on map. Live databases, PBIP models, execution adapters, and network access are explicitly out of scope.