retail-initlisted

Bootstrap the Compass-Driven kit and lead a NEW user to a first visible result on THEIR own table in the Seshat BI repo. Use when someone asks to "set up the kit", "initialize seshat", "onboard me / get me started", or runs `retail init`. The AGENT performs this: it writes the backstage substrate (compass router + fenced AGENTS.md/CLAUDE.md regions + manifests) via the substrate-only `retail init` CLI, DELEGATES the worked-example offer + human-seam list to `first-hour-compass`, and ROUTES into `retail-onboard-table` for the Stage-1 read-only profile (grain candidates + column types over a live DB, or `[PENDING LIVE PROFILE]` without one). It is NOT a terminal wizard, stores no run-state, fetches no remote, self-grants no approval, and emits no confidence score.
Kemetra/Seshat-BI · ★ 2 · AI & Automation · score 68

Install: claude install-skill Kemetra/Seshat-BI

# retail-init The install-time front door for the Compass-Driven kit. Its one job is to turn a fresh `pip install` into a first visible result on the user's own table — leading with analyst value, keeping the substrate backstage. **You (the agent) perform this flow; the `retail init` CLI only writes substrate and prints the next step.** This is Phase-1 Step 1-2 of `docs/roadmap/distribution-ideas.md`. ## Scope + non-negotiables (read first) - **Agent-first, not a wizard (Principle I).** The `retail init` CLI is substrate-writing ONLY — it writes `.seshat/` + the fenced regions and prints the next step. It never prompts, shows a menu, or emits a profile. The delegate → route → profile flow is YOU performing this skill over the existing prose verbs. - **Delegate, never fork (anti-fork).** The worked-example offer, the human-seam list, and the single-table orientation card belong to `first-hour-compass` — its single source. The Stage-1 profile belongs to `retail-onboard-table`. Do NOT restate any of them here; route into them. - **No run-state (FR-005).** `compass.yaml` declares the orientation protocol and points at per-table `readiness-status.yaml`; it stores no `current_stage`. There is no repo-level stage. - **Fence-only writes (FR-006/FR-007).** The substrate write touches only the `…` region of AGENTS.md / CLAUDE.md; everything outside is hand-authored / constitution-owned and stays byte-identical. - **