retail-kpi-knowledge

Defines governed retail KPI meaning, additivity, grain, and contracts before implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Retail metrics like VAT, returns, cost, same-store sales, and snapshot policy are often undefined or ambiguous, leading to untrustworthy dashboards. This Skill routes you through Seshat's public retail KPI knowledge base so every metric has governed meaning, grain, and required fields before any implementation begins. ## Core Features & Use Cases - Governed Metric Definitions: Establish KPI meaning, additivity, grain, and required fields using curated retail knowledge routes. - Ambiguity Escalation: Flags undefined VAT, returns, cost, same-store, or snapshot policy as named-human decisions rather than agent defaults. - Contracts and Handoffs: Produces metric contracts and handoff artifacts ready for downstream warehouse and Power BI implementation. - Use Case: Before building a sales dashboard, use this Skill to define how returns and VAT affect net revenue, lock the grain at store-day level, and record the contract so engineers implement exactly what the business approved. ## Quick Start Use the retail KPI knowledge to define the net sales metric, including VAT and returns policy, grain, and required fields, before implementation.

Frequently Asked Questions about retail-kpi-knowledge

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

FAQPage Schema
How do I define retail KPIs before building a dashboard?▼

Open the retail KPI knowledge index, select only the route matching your metric, and follow its stop rules to record meaning, additivity, grain, and required fields. Undefined policy areas must be decided by a named human, not assumed.

What retail metrics does this KPI knowledge cover?▼

It covers governed definitions for VAT handling, returns, cost, same-store comparisons, and snapshot policy, along with additivity, grain, required fields, contracts, and handoffs for each metric.

Can an AI agent decide VAT or returns policy automatically?▼

No. Undefined VAT, returns, cost, same-store, or snapshot policy is explicitly a named-human decision. The Skill's stop rules prevent agents from defaulting these judgment calls.

When should I use governed KPI definitions in a BI project?▼

Use them before implementation, when binding metrics to contracts for a warehouse or Power BI delivery. Defining grain and additivity upfront prevents reconciliation failures and disputed totals later.

What are the limitations of a KPI knowledge base?▼

It provides definitions and decision routes, not data validation or computation. You still need profiling, mapping governance, and warehouse validation to confirm the implemented metrics match the agreed contracts.