[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FE16A26VPTVR9SSJFGAFXT":3,"skill-same:01M7FE16A26VPTVR9SSJFGAFXT":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FE16A26VPTVR9SSJFGAFXT","business-intelligence",null,"Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fbusiness-intelligence\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: business-intelligence\ndescription: Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.\n---\n\n# Business intelligence\n\nMost organizations have too many dashboards and too little insight. The two are related: when\neverything is measured, nothing is watched.\n\n## Start from the decision\n\nEvery report answers one question for one audience who can act on it. Before building, name the\ndecision it informs and what a viewer would do differently based on it.\n\nIf nothing would change, do not build it. That single filter removes most dashboard requests, and\nthe ones surviving it get used.\n\n## Metric trees\n\nStructure metrics as a tree, not a list. One primary outcome at the top, decomposed into the drivers\nthat mathematically produce it, each decomposed again.\n\nRevenue = customers × average value. Customers = new + retained. New = traffic × conversion. And so\non.\n\nThis does two things a metric list cannot: when the top number moves, you can walk down to find\n*where*; and it makes clear which metrics are levers and which are outcomes. Teams should be\nmeasured on levers they control, not on outcomes they influence.\n\n## Dashboard design\n\n- **One screen, one question.** Scrolling dashboards are several dashboards that were not separated.\n- **Lead with the answer** — the primary number, its comparison, and whether that is good. A number\n  with no comparison is not information.\n- **Comparison always**: prior period, target, or cohort. Choose deliberately, because each tells a\n  different story.\n- **Say what \"good\" is.** A viewer who cannot tell whether 4.2% is good will not act.\n- **Annotate the anomalies.** The spike everyone asks about should carry its explanation, or you\n  will explain it every month.\n- **Cut the rest.** Charts nobody uses cost attention on every visit and make the useful ones harder\n  to find.\n\n## Self-serve\n\nSelf-serve works when the semantic layer is trustworthy and the questions are anticipated. It fails\nwhen people are handed raw tables and left to define metrics themselves — that produces confident\nwrong answers, which is worse than a queue.\n\nGive governed metrics, curated datasets, and templates for common questions. Keep the raw layer for\nanalysts.\n\n## Trust\n\nReporting nobody trusts is not used, and trust is lost far faster than it is rebuilt. Protect it by\nshowing freshness on every dashboard, surfacing failures rather than serving stale data silently, and\nreconciling against the system of record for anything financial.\n\nWhen a number is wrong, say so prominently and fast. Quietly correcting it is how a team learns to\ncheck every figure by hand.\n\n## Maintenance\n\nDashboards accumulate. Review usage periodically and retire what nobody opens — with a notice period,\nsince the one person using it may be using it for something important.\n\n## Tooling\n\nBI: Power BI, Looker, Tableau, Metabase, Omni, Hex, and similar.\n\nMetric definitions belong in a semantic layer — dbt's, Looker's LookML, Cube — rather than\nin each dashboard's SQL, or the same metric will disagree with itself across two tabs.\n\nSpreadsheets remain the most-used BI tool in every organization. Plan for the export rather\nthan pretending it will not happen.\n\n## Never\n\n- Build a dashboard nobody has a decision for. Start from the decision.\n- Ship a metric with two definitions live at the same time.\n- Leave a dashboard published with no owner. Unowned dashboards get trusted, then get wrong.\n- Show a number without the denominator and the window it covers.\n","# Business intelligence\n\nMost organizations have too many dashboards and too little insight. The two are related: when\neverything is measured, nothing is watched.\n\n## Start from the decision\n\nEvery report answers one question for one audience who can act on it. Before building, name the\ndecision it informs and what a viewer would do differently based on it.\n\nIf nothing would change, do not build it. That single filter removes most dashboard requests, and\nthe ones surviving it get used.\n\n## Metric trees\n\nStructure metrics as a tree, not a list. One primary outcome at the top, decomposed into the drivers\nthat mathematically produce it, each decomposed again.\n\nRevenue = customers × average value. Customers = new + retained. New = traffic × conversion. And so\non.\n\nThis does two things a metric list cannot: when the top number moves, you can walk down to find\n*where*; and it makes clear which metrics are levers and which are outcomes. Teams should be\nmeasured on levers they control, not on outcomes they influence.\n\n## Dashboard design\n\n- **One screen, one question.** Scrolling dashboards are several dashboards that were not separated.\n- **Lead with the answer** — the primary number, its comparison, and whether that is good. A number\n  with no comparison is not information.\n- **Comparison always**: prior period, target, or cohort. Choose deliberately, because each tells a\n  different story.\n- **Say what \"good\" is.** A viewer who cannot tell whether 4.2% is good will not act.\n- **Annotate the anomalies.** The spike everyone asks about should carry its explanation, or you\n  will explain it every month.\n- **Cut the rest.** Charts nobody uses cost attention on every visit and make the useful ones harder\n  to find.\n\n## Self-serve\n\nSelf-serve works when the semantic layer is trustworthy and the questions are anticipated. It fails\nwhen people are handed raw tables and left to define metrics themselves — that produces confident\nwrong answers, which is worse than a queue.\n\nGive governed metrics, curated datasets, and templates for common questions. Keep the raw layer for\nanalysts.\n\n## Trust\n\nReporting nobody trusts is not used, and trust is lost far faster than it is rebuilt. Protect it by\nshowing freshness on every dashboard, surfacing failures rather than serving stale data silently, and\nreconciling against the system of record for anything financial.\n\nWhen a number is wrong, say so prominently and fast. Quietly correcting it is how a team learns to\ncheck every figure by hand.\n\n## Maintenance\n\nDashboards accumulate. Review usage periodically and retire what nobody opens — with a notice period,\nsince the one person using it may be using it for something important.\n\n## Tooling\n\nBI: Power BI, Looker, Tableau, Metabase, Omni, Hex, and similar.\n\nMetric definitions belong in a semantic layer — dbt's, Looker's LookML, Cube — rather than\nin each dashboard's SQL, or the same metric will disagree with itself across two tabs.\n\nSpreadsheets remain the most-used BI tool in every organization. Plan for the export rather\nthan pretending it will not happen.\n\n## Never\n\n- Build a dashboard nobody has a decision for. Start from the decision.\n- Ship a metric with two definitions live at the same time.\n- Leave a dashboard published with no owner. Unowned dashboards get trusted, then get wrong.\n- Show a number without the denominator and the window it covers.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fbusiness-intelligence",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill business-intelligence",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill business-intelligence",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill business-intelligence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fbusiness-intelligence\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]