bi-sql-knowledge

Applies Seshat SQL knowledge to grain, join, aggregation, and reconciliation reasoning without database execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analysts reasoning about retail source data often guess at row grain, join keys, and aggregation rules, producing metrics that cannot be reconciled. This Skill routes those questions through Seshat's curated SQL knowledge base so reasoning stays grounded in documented facts instead of assumptions. ## Core Features & Use Cases - Routed Knowledge Lookup: Opens the bi-sql-knowledge INDEX and selects only the route relevant to the current question, avoiding context bloat. - Grain and Join Grounding: Enforces explicit row-grain statements and forbids inferring missing source facts during join and aggregation reasoning. - Validation and Reconciliation Guidance: Provides documented rules for validation, reconciliation, and transformation decisions without executing any database. - Use Case: While mapping a messy retail extract into a medallion warehouse, ask how to aggregate line-item sales to daily store totals; the Skill follows the aggregation route and returns grounded rules with stop conditions. ## Quick Start Ask the assistant to use the bi-sql-knowledge skill to determine the correct grain and join keys for aggregating retail sales lines into daily store totals.

Frequently Asked Questions about bi-sql-knowledge

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

FAQPage Schema
How do I determine the grain of a retail data source before aggregation?▼

State the row grain explicitly before any aggregation by following the grain route in the knowledge INDEX. The Skill grounds grain in documented source facts and stops rather than inferring facts that are not present.

How to validate SQL join logic without running a database?▼

Use the join route in the bi-sql-knowledge INDEX to review documented join rules and cardinality expectations. Reasoning happens entirely offline against curated knowledge, so no database connection or query execution is required.

Does this Skill execute SQL queries against my warehouse?▼

No, it performs reasoning only and never executes a database. It reads curated knowledge routes for grain, joins, aggregation, validation, and reconciliation, then applies those rules to your stated scenario.

What happens when source facts are missing during reconciliation reasoning?▼

The Skill follows explicit stop rules and refuses to infer missing source facts. Instead of guessing, it surfaces the gap so a human can supply the missing information before reconciliation proceeds.

When should I use knowledge-based SQL reasoning instead of live query profiling?▼

Use it during early mapping and metric-definition work when you need documented rules for grain, joins, and aggregation before any warehouse exists. Live profiling is appropriate later, when actual data is available to validate those assumptions.