retail-discover-portfoliolisted
Install: claude install-skill Kemetra/Seshat-BI
# retail-discover-portfolio
Use this skill when the owner has an unfamiliar database schema or file folder and
needs a governed route from portfolio discovery to the business interview.
## Boundary
This is an agent-conducted flow, not a new state engine or CLI workflow:
portfolio discovery -> domain -> scope -> selected-table onboarding -> interview handoff -> STOP
- Layer A is the metadata-only portfolio survey in
templates/portfolio-survey.md.
- Layer B is the existing value-backed, per-table Source Ready profile owned by
retail-onboard-table.
- Never create a second profiler or author mappings/<table>/source-profile.md here.
- Never select a scale-out route. Record scale evidence for the existing
silver_gold_model_planning boundary to decide later.
- Read the existing stage contracts and committed artifacts to derive exactly one
next action. Create no run-state, projection, or routing file.
The golden reference shapes are:
- tests/fixtures/portfolio-survey/db-schema/survey.md
- tests/fixtures/portfolio-survey/file-folder/survey.md
## 1. Produce the Layer-A survey
For a database schema:
1. Call seshat.portfolio_enumerate.enumerate_tables(schema). This helper is the
only DB table-enumeration path. Do not issue a raw information_schema.tables
query, and do not catch raw config, driver, or connection exceptions.
2. If it returns an error, show only that redacted error. If no metadata is
readable, STOP and name the unblock: configure the gitignored .e