[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JKZSC9QH1FQ4JB2RSCSVN":3,"skill-same:01M77JKZSC9QH1FQ4JB2RSCSVN":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77JKZSC9QH1FQ4JB2RSCSVN","first-hour-compass",null,"Show a NEW-table author the stateful \"you are here \u002F next artifact \u002F authoring skill\" orientation card for ONE table in the Seshat BI repo. Use when someone asks \"where is this table in the readiness journey\", \"what do I do next for \u003Ctable>\", or \"orient me on a new table\". READ-ONLY and invoke-and-present only: it parses that table's mappings\u002F\u003Ctable>\u002Freadiness-status.yaml and RENDERS a single-table orientation card (current stage, the next non-pass stage + the artifact it needs + the authoring skill that produces it, plus recorded STOP rows). It RENDERS recorded state (never recomputes a status, advances a stage, writes a pass, infers\u002Fback-fills an approval, or fabricates evidence), runs NO validator, opens NO DB connection, and emits NO numeric health\u002Fconfidence\u002Fpercent-ready\u002Fmaturity score (hard rule #9). It is the STATEFUL single-table sibling of the F026 readiness-viewer (multi-table matrix) and the stateful form of the F006 static onboarding checklist.","Kemetra\u002FSeshat-BI","Kemetra","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206601658?v=4","01M77J5APND9QAJK8XMBH5B1A8","01M77J5AR4TM1GN2G4GS5KH02J",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fintegrations\u002Fclaude-code\u002Fseshat-bi\u002Fskills\u002Ffirst-hour-compass\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: first-hour-compass\ndescription: >-\n  Show a NEW-table author the stateful \"you are here \u002F next artifact \u002F\n  authoring skill\" orientation card for ONE table in the Seshat BI repo. Use\n  when someone asks \"where is this table in the readiness journey\", \"what do\n  I do next for \u003Ctable>\", or \"orient me on a new table\". READ-ONLY and\n  invoke-and-present only: it parses that table's\n  mappings\u002F\u003Ctable>\u002Freadiness-status.yaml and RENDERS a single-table\n  orientation card (current stage, the next non-pass stage + the artifact it\n  needs + the authoring skill that produces it, plus recorded STOP rows). It\n  RENDERS recorded state (never recomputes a status, advances a stage,\n  writes a pass, infers\u002Fback-fills an approval, or fabricates evidence),\n  runs NO validator, opens NO DB connection, and emits NO numeric\n  health\u002Fconfidence\u002Fpercent-ready\u002Fmaturity score (hard rule #9). It is the\n  STATEFUL single-table sibling of the F026 readiness-viewer (multi-table\n  matrix) and the stateful form of the F006 static onboarding checklist.\n---\n\n# First-Hour Compass\n\nThe stateful single-table orientation card for a new-table author. F024 module class:\n**Product Module \u002F `read-only`**. It answers, for ONE table: *where am I, what is the next\nartifact, which skill authors it, and what human STOP is recorded?*\n\n## What it does \u002F does NOT do\n\n- **Creates no truth.** It copies recorded fields; it defines no meaning, sets no status.\n- **Changes no state.** It edits no file and runs no git mutation (a run leaves `git status`\n  clean -- see the read-only proof below).\n- **Infers no approval.** It never populates, back-fills, or synthesizes an approval; it only\n  reports whether the next stage's `\u003Cstage>-ready.md` names a required owner and whether an\n  `approvals[]` entry is recorded.\n- **Fabricates no evidence.** A missing\u002Fabsent field is reported as the honest not-started\n  state, never invented.\n- **Runs no validator, opens no DB.** It reads `readiness-status.yaml` only.\n- **Emits no score.** No numeric health \u002F confidence \u002F percent-ready \u002F maturity value. A\n  request for one is DECLINED (hard rule #9); orientation is the four explicit statuses +\n  evidence + blockers + the next allowed step.\n\n## How it renders (renders, never re-derives)\n\n| Card field | Source (copied verbatim) |\n|------------|--------------------------|\n| You are here | `readiness-status.yaml` `current_stage` + that stage's `status` |\n| Next stage | the FIRST non-`pass` stage in pipeline order (Source -> Mapping -> Silver -> Gold -> Semantic Model -> Dashboard -> Publish) |\n| Next artifact | the required artifact named in that stage's readiness definition |\n| Authoring skill | the cross-walk row for that stage in the compass card template |\n| STOP rows | that stage's `blocking_reasons[]` verbatim + an approval-required flag |\n| Conflict flags | surfaced (never auto-corrected): a `pass` with empty `evidence[]`; a downstream stage entered while an upstream is not `pass` |\n\n## Honest-state rules\n\n- **No file** for the table -> \"Not yet onboarded -- start at Source Ready with\n  `retail-onboard-table`.\" (Absent is not-started, never a fabricated stage.)\n- **A stage `pass`** is reported only as recorded; the card never sets or upgrades it.\n- **Pipeline ordering** is respected: a downstream stage is never presented as reachable while\n  an upstream gate is not `pass`.\n\n## First arrival: offer a worked example as the reference pattern\n\nWhen there is **no table yet** -- the user has just arrived and named nothing -- do not stop\nat \"run `retail-onboard-table`\". First give them a concrete pattern to steer by. This is the\nfirst-hour \"aha\": a new author's fastest path is to hold up a filled example and copy its\n*shape*, not to start from an empty gate.\n\nPresent the committed worked example as the reference pattern to steer by:\n\n| Worked example | What it demonstrates | Pick it when your table is... |\n|----------------|----------------------|-------------------------------|\n| `retail-store-sales` | The **full seven-stage spine** to Dashboard Ready -- metric contracts, governed model, dashboard design, handoff (on the public Kaggle retail-store-sales dataset) | ...any retail-sales table; it carries the build mechanics AND the later stages (semantic model, dashboard, handoff) |\n\nThen hand off to `retail-onboard-table` for the user's own table, **holding the example\nup as the reference** for that walk (see the worked-examples index). Be explicit\nabout what \"use this example\" means:\n\n- The example is a **narrative pattern, not a file template** -- `retail-store-sales.md` itself\n  says \"copy this section structure, swap in the new table, run the playbook's 7 phases\". So the\n  skill **references** the example while onboarding; it does **not** copy files into the user's\n  table dir. (The actual starting artifacts come from `templates\u002F`, seeded by\n  `retail-onboard-table`.)\n- **Read-only + route only.** This section presents the worked example and routes into the\n  existing onboarding walk. It creates no truth, seeds no artifact, and writes nothing itself\n  (the run still leaves `git status` clean; `retail-onboard-table` is what later authors files).\n\nSet expectations honestly on the same breath: **the agent handles the sequence and the\nplumbing; the user still owns the judgment** -- grain, PII placement, business rollups, and\nmetric policy are the four human seams `retail-onboard-table` will surface and STOP on, never\nauto-resolve (Principle V).\n\n## The two-condition approval flag\n\nThe card flags \"approval required\" for the next stage only when BOTH hold, read from the stage\ndoc's \"Required owner \u002F approval\" field: (1) that stage requires a named human sign-off, and\n(2) no matching `approvals[]` entry is recorded. It never names, infers, or supplies the owner\n(mirrors the readiness-viewer contract) -- a Principle-V human seam.\n\n## The four judgment seams (surfaced, never resolved -- Principle V)\n\nGrain\u002Funiqueness, PII publish-safety, business rollup\u002Fsegment, and product identity are human\njudgment calls. The Compass RE-PRESENTS a recorded STOP touching any of these; it never\nasserts a grain, clears a PII gap, embeds a rollup\u002Fsegment, or fixes a product identity.\n\n## Deltas vs its parents\n\n- **vs F026 readiness-viewer**: F026 is the multi-table stage MATRIX (all items, all stages).\n  The Compass is the SINGLE-table, next-artifact, authoring-skill-routed orientation card.\n- **vs F006 onboarding-checklist**: F006 is the STATIC definition-of-done. The Compass is the\n  STATEFUL \"you are at Stage N of it\" read of the same journey.\n\n## Read-only proof\n\nRendering the card writes nothing. After a run, `git status` is clean (the skill mutates no\ntracked file); the only output is the rendered card in the response.\n\n## See also\n\n- The card template + stage->skill cross-walk: the first-hour-compass card template.\n- First-arrival reference pattern: the `retail-store-sales` worked example\n  (a narrative pattern, not a template)\n- The onboarding walk this routes into: the `retail-onboard-table` skill.\n- Usage + boundary: the first-hour-compass usage note.\n- Multi-table parent (F026): the `readiness-viewer` skill.\n- Static parent (F006): the onboarding checklist.\n- Pipeline ordering + gates: the readiness-pipeline definition.\n","# First-Hour Compass\n\nThe stateful single-table orientation card for a new-table author. F024 module class:\n**Product Module \u002F `read-only`**. It answers, for ONE table: *where am I, what is the next\nartifact, which skill authors it, and what human STOP is recorded?*\n\n## What it does \u002F does NOT do\n\n- **Creates no truth.** It copies recorded fields; it defines no meaning, sets no status.\n- **Changes no state.** It edits no file and runs no git mutation (a run leaves `git status`\n  clean -- see the read-only proof below).\n- **Infers no approval.** It never populates, back-fills, or synthesizes an approval; it only\n  reports whether the next stage's `\u003Cstage>-ready.md` names a required owner and whether an\n  `approvals[]` entry is recorded.\n- **Fabricates no evidence.** A missing\u002Fabsent field is reported as the honest not-started\n  state, never invented.\n- **Runs no validator, opens no DB.** It reads `readiness-status.yaml` only.\n- **Emits no score.** No numeric health \u002F confidence \u002F percent-ready \u002F maturity value. A\n  request for one is DECLINED (hard rule #9); orientation is the four explicit statuses +\n  evidence + blockers + the next allowed step.\n\n## How it renders (renders, never re-derives)\n\n| Card field | Source (copied verbatim) |\n|------------|--------------------------|\n| You are here | `readiness-status.yaml` `current_stage` + that stage's `status` |\n| Next stage | the FIRST non-`pass` stage in pipeline order (Source -> Mapping -> Silver -> Gold -> Semantic Model -> Dashboard -> Publish) |\n| Next artifact | the required artifact named in that stage's readiness definition |\n| Authoring skill | the cross-walk row for that stage in the compass card template |\n| STOP rows | that stage's `blocking_reasons[]` verbatim + an approval-required flag |\n| Conflict flags | surfaced (never auto-corrected): a `pass` with empty `evidence[]`; a downstream stage entered while an upstream is not `pass` |\n\n## Honest-state rules\n\n- **No file** for the table -> \"Not yet onboarded -- start at Source Ready with\n  `retail-onboard-table`.\" (Absent is not-started, never a fabricated stage.)\n- **A stage `pass`** is reported only as recorded; the card never sets or upgrades it.\n- **Pipeline ordering** is respected: a downstream stage is never presented as reachable while\n  an upstream gate is not `pass`.\n\n## First arrival: offer a worked example as the reference pattern\n\nWhen there is **no table yet** -- the user has just arrived and named nothing -- do not stop\nat \"run `retail-onboard-table`\". First give them a concrete pattern to steer by. This is the\nfirst-hour \"aha\": a new author's fastest path is to hold up a filled example and copy its\n*shape*, not to start from an empty gate.\n\nPresent the committed worked example as the reference pattern to steer by:\n\n| Worked example | What it demonstrates | Pick it when your table is... |\n|----------------|----------------------|-------------------------------|\n| `retail-store-sales` | The **full seven-stage spine** to Dashboard Ready -- metric contracts, governed model, dashboard design, handoff (on the public Kaggle retail-store-sales dataset) | ...any retail-sales table; it carries the build mechanics AND the later stages (semantic model, dashboard, handoff) |\n\nThen hand off to `retail-onboard-table` for the user's own table, **holding the example\nup as the reference** for that walk (see the worked-examples index). Be explicit\nabout what \"use this example\" means:\n\n- The example is a **narrative pattern, not a file template** -- `retail-store-sales.md` itself\n  says \"copy this section structure, swap in the new table, run the playbook's 7 phases\". So the\n  skill **references** the example while onboarding; it does **not** copy files into the user's\n  table dir. (The actual starting artifacts come from `templates\u002F`, seeded by\n  `retail-onboard-table`.)\n- **Read-only + route only.** This section presents the worked example and routes into the\n  existing onboarding walk. It creates no truth, seeds no artifact, and writes nothing itself\n  (the run still leaves `git status` clean; `retail-onboard-table` is what later authors files).\n\nSet expectations honestly on the same breath: **the agent handles the sequence and the\nplumbing; the user still owns the judgment** -- grain, PII placement, business rollups, and\nmetric policy are the four human seams `retail-onboard-table` will surface and STOP on, never\nauto-resolve (Principle V).\n\n## The two-condition approval flag\n\nThe card flags \"approval required\" for the next stage only when BOTH hold, read from the stage\ndoc's \"Required owner \u002F approval\" field: (1) that stage requires a named human sign-off, and\n(2) no matching `approvals[]` entry is recorded. It never names, infers, or supplies the owner\n(mirrors the readiness-viewer contract) -- a Principle-V human seam.\n\n## The four judgment seams (surfaced, never resolved -- Principle V)\n\nGrain\u002Funiqueness, PII publish-safety, business rollup\u002Fsegment, and product identity are human\njudgment calls. The Compass RE-PRESENTS a recorded STOP touching any of these; it never\nasserts a grain, clears a PII gap, embeds a rollup\u002Fsegment, or fixes a product identity.\n\n## Deltas vs its parents\n\n- **vs F026 readiness-viewer**: F026 is the multi-table stage MATRIX (all items, all stages).\n  The Compass is the SINGLE-table, next-artifact, authoring-skill-routed orientation card.\n- **vs F006 onboarding-checklist**: F006 is the STATIC definition-of-done. The Compass is the\n  STATEFUL \"you are at Stage N of it\" read of the same journey.\n\n## Read-only proof\n\nRendering the card writes nothing. After a run, `git status` is clean (the skill mutates no\ntracked file); the only output is the rendered card in the response.\n\n## See also\n\n- The card template + stage->skill cross-walk: the first-hour-compass card template.\n- First-arrival reference pattern: the `retail-store-sales` worked example\n  (a narrative pattern, not a template)\n- The onboarding walk this routes into: the `retail-onboard-table` skill.\n- Usage + boundary: the first-hour-compass usage note.\n- Multi-table parent (F026): the `readiness-viewer` skill.\n- Static parent (F006): the onboarding checklist.\n- Pipeline ordering + gates: the readiness-pipeline definition.\n",{"name":5,"description":7},"main","6266e304556a72b75d951b9433fd833481c61233","integrations\u002Fclaude-code\u002Fseshat-bi\u002Fskills\u002Ffirst-hour-compass",0,"https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI","https:\u002F\u002Fpypi.org\u002Fproject\u002Fseshat-bi\u002F","https:\u002F\u002Fgithub.com\u002FKemetra","2026-11-11 21:44:25",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Kemetra\u002FSeshat-BI --skill first-hour-compass",{"tool":37,"command":38},"bunx","bunx skills add Kemetra\u002FSeshat-BI --skill first-hour-compass",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Kemetra\u002FSeshat-BI --skill first-hour-compass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fintegrations\u002Fclaude-code\u002Fseshat-bi\u002Fskills\u002Ffirst-hour-compass\u002FSKILL.md",true,[],[46,53,58,64,69,76],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M77JWCTJ88JWPDD25WZ2NEY8","fake-skill","A fixture skill with declaring frontmatter, used as positive shipped evidence.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Funlisted\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":54,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M77JWA0BTG4JB2HR52Q99216","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M77JW6VE59XEFHWBTNDYAS2Q","bare-skill-no-frontmatter","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Fbare-skill-no-frontmatter\u002FSKILL.md",[],[],{"skillNo":65,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M77JW4TD1FNFSBNP5C0WXAA5","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Fgood\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M77JVWCVE3WZ82ZNFCSFVDCP","retail-kpi-knowledge","Retail KPI \u002F metric-contract reasoning layer for BI agents in the Seshat BI project. Use when an agent must reason about the BUSINESS MEANING of a retail KPI before any implementation — defining a KPI in business terms, classifying additivity (fully\u002Fsemi\u002Fnon-additive), identifying grain, listing required source fields, resolving ambiguity (gross vs net, VAT, returns, cost method, same-store), choosing an MVP KPI pack, reviewing a metric contract for completeness, or preparing a clean handoff to an implementation layer. Also use it to classify KPI sufficiency or prepare an owner policy decision packet. This is a meaning\u002Fdefinition + review layer, not an executor: it does not write DAX\u002FSQL\u002FPython, grant readiness, approve policy, or design dashboards. See INDEX.md for live\u002Fplanned routes; registry.yaml is the authoritative machine-readable inventory.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fretail-kpi-knowledge\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M77JVNDM1NGYGSCPTBW9ZCF5","bi-sql-knowledge","SQL reasoning, validation, reconciliation, transformation, diagnostics, and anti-pattern knowledge layer for Seshat BI agents. Use when a task involves reasoning about source SQL: source profiling, table grain, keys & uniqueness, joins & fan-out amplification, aggregation correctness, COUNT\u002FNULL semantics, deduplication, validation queries, reconciliation queries, silver\u002Fgold transformation logic, window\u002Fdate-time analytics, SQL anti-patterns, or basic SQL performance reasoning, or interpretation of a supplied sanitized PostgreSQL JSON execution plan. The SQL counterpart to bi-dax-knowledge. It is a thinking & validation layer, not a database executor, runtime validator, dbt\u002FDagster project, or automatic tuning service.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fbi-sql-knowledge\u002FSKILL.md",[],[]]