retail-onboard-table

Walks a new raw retail table from Source Ready through Mapping Ready with readiness bookkeeping.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Onboarding a new raw retail table into a governed analytics pipeline requires profiling the source, authoring mapping artifacts, and recording readiness status, all without skipping human judgment calls on grain, PII, and business rollups. This Skill sequences that first stage transition so no table reaches mapping without evidence and review. ## Core Features & Use Cases - Stage 1 Source Ready profiling: Measures row counts, column missingness, candidate-key uniqueness, and returns-column population over a read-only connection, recording results in source-profile.md. - Stage 2 mapping delegation: Invokes the source-mapping skill to author source-map.yaml, assumptions.md, unresolved-questions.md, and the reconciliation report blank, without duplicating the mapping procedure. - Readiness bookkeeping and hard stops: Seeds readiness-status.yaml with explicit pass/warning/blocked statuses plus evidence, and halts at four human decision seams (grain, PII publish-safety, business rollup, product identity). - Use Case: When a new table like raw store transactions arrives, ask the agent to onboard it; it profiles the data, delegates the mapping artifacts, flags open judgment questions for named owners, and stops at Mapping Ready pending human approval. ## Quick Start Ask the agent to onboard the new raw table by saying "onboard schema.table from nothing to a reviewed map" and let it profile, delegate mapping, and seed the readiness status.

Frequently Asked Questions about retail-onboard-table

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

FAQPage Schema
How do I onboard a new raw retail table into a governed analytics pipeline?▼

Invoke this skill with the schema-qualified table name; it profiles the source, delegates mapping artifact authoring to the source-mapping skill, and seeds a readiness-status.yaml. It stops at Mapping Ready until a human approves the mapping gate.

What artifacts does the retail table onboarding process produce?▼

It produces source-profile.md with measured row counts, missingness, and key uniqueness, plus delegated artifacts: source-map.yaml, assumptions.md, unresolved-questions.md, a reconciliation report blank, and readiness-status.yaml tracking stage statuses.

Can the onboarding wizard approve its own mapping gate?▼

No. The wizard never self-grants approval; it sets mapping_ready to blocked while review is pending and only promotes it to pass after a human records approval and clears the gate in unresolved-questions.md.

What happens when there is no database connection configured?▼

The skill enters deferred-boundary mode: it marks mechanical profile rows as pending live profile, records source_ready as warning rather than pass, and prints enable steps for installing the db extra and setting DATABASE_URL.

Does this skill write silver-layer SQL or build the warehouse?▼

No. It never writes silver.* SQL, migrations, or calls retail-build-warehouse. Its terminal state is Mapping Ready; the Silver Ready stage is explicitly out of scope and handled by a separate downstream skill.

How are judgment calls like grain, PII, and rollups handled during onboarding?▼

They are proposed with supporting data facts and raised as rows in unresolved-questions.md with named owners, then the wizard stops. It never silently defaults grain, PII publish-safety, business rollups, or product identity decisions.