[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JR4QMS59MAQA9GWSP085B":3,"skill-same:01M77JR4QMS59MAQA9GWSP085B":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},"01M77JR4QMS59MAQA9GWSP085B","business-knowledge-interview",null,"After a database is discovered and profiled, interview the business owner to capture the meaning-critical decisions the rest of the Database-to-PBIP flow depends on -- KPI meaning, PII handling, table grain, primary keys, relationships, missing-value rules, and ambiguous financial\u002Fquantity\u002Fdate columns -- and record every outcome in the project Decision Store. Use when someone asks to run the interview, capture business knowledge, or resolve the business questions behind a model in the Seshat BI repo. It asks obvious low-risk items as one batch and critical items individually with explicit named-human approval; it uses masked samples and never shows raw suspected PII by default; it records decisions and STOPS. It does NOT define metric contracts or DAX, does NOT self-grant any approval, and does NOT emit a confidence score.","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\u002Fcodex\u002Fseshat-bi\u002Fskills\u002Fbusiness-knowledge-interview\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: business-knowledge-interview\ndescription: >-\n  After a database is discovered and profiled, interview the business owner to\n  capture the meaning-critical decisions the rest of the Database-to-PBIP flow\n  depends on -- KPI meaning, PII handling, table grain, primary keys,\n  relationships, missing-value rules, and ambiguous financial\u002Fquantity\u002Fdate\n  columns -- and record every outcome in the project Decision Store. Use when\n  someone asks to run the interview, capture business knowledge, or resolve the\n  business questions behind a model in the Seshat BI repo. It asks obvious\n  low-risk items as one batch and critical items individually with explicit\n  named-human approval; it uses masked samples and never shows raw suspected PII\n  by default; it records decisions and STOPS. It does NOT define metric contracts\n  or DAX, does NOT self-grant any approval, and does NOT emit a confidence score.\n---\n\n# business-knowledge-interview\n\nThe interview is the front door of the Database-to-PBIP flow's decision layer\n(spec 121). It converts a discovery profile into recorded, approvable business\ndecisions so that every downstream stage consumes governed answers instead of\nunrecorded assumptions.\n\nBehavior is governed by the `business-knowledge-interview` contract and its\nrecorded interview protocol. The\nstatic rules DS1-DS5 (`seshat check`) verify the recorded outcome, not the\nconversation.\n\n## When to use\n\n- After `retail-onboard-table` has produced a committed discovery profile (or an\n  equivalent committed profile exists).\n- Before KPI contracts, Silver\u002FGold planning, DAX, dashboard blueprint, or PBIP\n  readiness -- those stages are blocked until their critical decisions are\n  approved.\n\n## Preconditions (stop if unmet)\n\n- A committed discovery profile exists. **No profile => do not start**; report the\n  gate as blocked naming the missing profile.\n- Load the existing Decision Store first. Existing decisions are presented for\n  confirmation or supersession -- **never overwritten**.\n\n## How it runs\n\n1. **Ground every question in the profile** (profile summaries, candidate grains,\n   column types). Do not walk every column one-by-one unless the owner asks or an\n   ambiguity requires it. Concentrate on: KPI inputs, PII, table grain, keys,\n   relationships, missing-value rules, and ambiguous financial\u002Fquantity\u002Fdate\n   columns.\n2. **Batch the obvious low-risk items** into one owner confirmation. Critical\n   decision types are never in a batch. The owner may exclude any item; the\n   remainder is approved in one action and each excluded item becomes an\n   individual `pending` question.\n3. **Ask critical decisions individually** with an explicit per-decision approval\n   by a named human whose authority class is eligible for the decision type\n   (as recorded in the `approval-authority` contract). Route any KPI-*meaning*\n   question to `retail-kpi-knowledge`; never invent meaning here.\n4. **Ask the domain's owner questions -- only those the scoped KPIs depend on.** For\n   each retail KPI domain the table feeds, open that domain pack in the\n   `retail-kpi-knowledge` skill and ask the cards in its `## Owner questions` section\n   that bear on a KPI actually in scope. **Do not ask a card no scoped KPI depends on:**\n   an unanswered card is recorded as a critical `pending` decision, and the decision gate\n   filters by decision type, not by KPI, so an out-of-scope card blocks the whole stage\n   (asking for Net Sales by Branch must not leave a same-store ruling pending). If scope\n   later widens, ask the cards it newly depends on then. Each card names the\n   `decision_type` its answer records under. A card's stated layer default is CONTEXT\n   shown to the owner -- never record it as their ruling. An unanswered in-scope card is\n   recorded `pending`\u002F`needs_user_input`; this layer never invents a policy to make a\n   number appear (that layer's ambiguity Resolution rule). **Not every card type blocks:**\n   the `kpi_contracts` gate blocks on `kpi_definition`, `policy_ruling` and\n   `missing_value_rule` only, so a pending `data_exclusion` or `table_grain` card is\n   recorded but does NOT stop contract authoring. Report those to the owner explicitly as\n   open-but-not-blocking rather than implying the gate will catch them -- the gate's\n   category list is the authority, not this step.\n   This step supplies the KPI-meaning questions step 3 routes out; it does not define a\n   metric or a contract.\n5. **Mask suspected PII by default.** Show shape-preserving masks, cite the\n   suspicion source. Unmasking requires an explicit owner instruction, recorded\n   as a `pii_handling` decision scoped to the affected columns. Never write a raw\n   suspected-PII value into a committed store file.\n6. **Record every outcome in the Decision Store**\n   (`.seshat\u002Fsemantic-decisions.yaml`, `.seshat\u002Fkpi-contracts.yaml`,\n   `.seshat\u002Fcleaning-rules.yaml`) -- answered => `proposed`\u002F`approved`; refused =>\n   `rejected`\u002F`deferred`; unanswered => `pending`\u002F`needs_user_input`; sample\n   needed but unavailable => `needs_sample`. Confidence (`low`\u002F`medium`\u002F`high`) is\n   the agent's proposal confidence only; it is never approval and never a\n   readiness signal.\n\n## Exit\n\nRegenerate `evidence\u002Fbusiness-interview-review.md` from the store and report the\ncurrent gate verdict for the next requested stage.\n\n## Hard stops (never)\n\n- Never self-grant an approval (Principle V; `never_self_grant_approval`).\n- Never advance a readiness stage.\n- Never emit a numeric confidence score (`never_fabricate_a_confidence_score`).\n- Never display raw suspected-PII values by default, and never commit them.\n- Never define a metric contract or DAX (that is the retail-kpi \u002F DAX layers).\n","# business-knowledge-interview\n\nThe interview is the front door of the Database-to-PBIP flow's decision layer\n(spec 121). It converts a discovery profile into recorded, approvable business\ndecisions so that every downstream stage consumes governed answers instead of\nunrecorded assumptions.\n\nBehavior is governed by the `business-knowledge-interview` contract and its\nrecorded interview protocol. The\nstatic rules DS1-DS5 (`seshat check`) verify the recorded outcome, not the\nconversation.\n\n## When to use\n\n- After `retail-onboard-table` has produced a committed discovery profile (or an\n  equivalent committed profile exists).\n- Before KPI contracts, Silver\u002FGold planning, DAX, dashboard blueprint, or PBIP\n  readiness -- those stages are blocked until their critical decisions are\n  approved.\n\n## Preconditions (stop if unmet)\n\n- A committed discovery profile exists. **No profile => do not start**; report the\n  gate as blocked naming the missing profile.\n- Load the existing Decision Store first. Existing decisions are presented for\n  confirmation or supersession -- **never overwritten**.\n\n## How it runs\n\n1. **Ground every question in the profile** (profile summaries, candidate grains,\n   column types). Do not walk every column one-by-one unless the owner asks or an\n   ambiguity requires it. Concentrate on: KPI inputs, PII, table grain, keys,\n   relationships, missing-value rules, and ambiguous financial\u002Fquantity\u002Fdate\n   columns.\n2. **Batch the obvious low-risk items** into one owner confirmation. Critical\n   decision types are never in a batch. The owner may exclude any item; the\n   remainder is approved in one action and each excluded item becomes an\n   individual `pending` question.\n3. **Ask critical decisions individually** with an explicit per-decision approval\n   by a named human whose authority class is eligible for the decision type\n   (as recorded in the `approval-authority` contract). Route any KPI-*meaning*\n   question to `retail-kpi-knowledge`; never invent meaning here.\n4. **Ask the domain's owner questions -- only those the scoped KPIs depend on.** For\n   each retail KPI domain the table feeds, open that domain pack in the\n   `retail-kpi-knowledge` skill and ask the cards in its `## Owner questions` section\n   that bear on a KPI actually in scope. **Do not ask a card no scoped KPI depends on:**\n   an unanswered card is recorded as a critical `pending` decision, and the decision gate\n   filters by decision type, not by KPI, so an out-of-scope card blocks the whole stage\n   (asking for Net Sales by Branch must not leave a same-store ruling pending). If scope\n   later widens, ask the cards it newly depends on then. Each card names the\n   `decision_type` its answer records under. A card's stated layer default is CONTEXT\n   shown to the owner -- never record it as their ruling. An unanswered in-scope card is\n   recorded `pending`\u002F`needs_user_input`; this layer never invents a policy to make a\n   number appear (that layer's ambiguity Resolution rule). **Not every card type blocks:**\n   the `kpi_contracts` gate blocks on `kpi_definition`, `policy_ruling` and\n   `missing_value_rule` only, so a pending `data_exclusion` or `table_grain` card is\n   recorded but does NOT stop contract authoring. Report those to the owner explicitly as\n   open-but-not-blocking rather than implying the gate will catch them -- the gate's\n   category list is the authority, not this step.\n   This step supplies the KPI-meaning questions step 3 routes out; it does not define a\n   metric or a contract.\n5. **Mask suspected PII by default.** Show shape-preserving masks, cite the\n   suspicion source. Unmasking requires an explicit owner instruction, recorded\n   as a `pii_handling` decision scoped to the affected columns. Never write a raw\n   suspected-PII value into a committed store file.\n6. **Record every outcome in the Decision Store**\n   (`.seshat\u002Fsemantic-decisions.yaml`, `.seshat\u002Fkpi-contracts.yaml`,\n   `.seshat\u002Fcleaning-rules.yaml`) -- answered => `proposed`\u002F`approved`; refused =>\n   `rejected`\u002F`deferred`; unanswered => `pending`\u002F`needs_user_input`; sample\n   needed but unavailable => `needs_sample`. Confidence (`low`\u002F`medium`\u002F`high`) is\n   the agent's proposal confidence only; it is never approval and never a\n   readiness signal.\n\n## Exit\n\nRegenerate `evidence\u002Fbusiness-interview-review.md` from the store and report the\ncurrent gate verdict for the next requested stage.\n\n## Hard stops (never)\n\n- Never self-grant an approval (Principle V; `never_self_grant_approval`).\n- Never advance a readiness stage.\n- Never emit a numeric confidence score (`never_fabricate_a_confidence_score`).\n- Never display raw suspected-PII values by default, and never commit them.\n- Never define a metric contract or DAX (that is the retail-kpi \u002F DAX layers).\n",{"name":5,"description":7},"main","6266e304556a72b75d951b9433fd833481c61233","integrations\u002Fcodex\u002Fseshat-bi\u002Fskills\u002Fbusiness-knowledge-interview",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 business-knowledge-interview",{"tool":37,"command":38},"bunx","bunx skills add Kemetra\u002FSeshat-BI --skill business-knowledge-interview",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Kemetra\u002FSeshat-BI --skill business-knowledge-interview","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fintegrations\u002Fcodex\u002Fseshat-bi\u002Fskills\u002Fbusiness-knowledge-interview\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",[],[]]