[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GKAVZN2QTHTZESEX7F8HHP":3,"skill-same:01M6GKAVZN2QTHTZESEX7F8HHP":78},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6GKAVZN2QTHTZESEX7F8HHP","metric-contract",null,"Use this skill when the user wants to define, document, reconcile, or review a KPI or metric. Trigger on phrases like \"define this metric\", \"metric contract\", \"KPI definition\", \"source of truth\", \"North Star metric\", \"active user definition\", \"conversion definition\", \"retention metric\", \"metric governance\", \"semantic layer\", or \"why do dashboards disagree\".","weisberg\u002Fagile_agentic_analytics","weisberg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5054710?v=4","01M6GK0MXK350SV8PMZ0D040SB","Brian Weisberg","01M6GK0N2F8X600FCTKCB3X2ZF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Flead-analyst\u002Fskills\u002Fmetric-contract\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"metric contract","contract","active","retention","north star metric","STAR","semantic","trigger","false","define","review","do","document","conversion","reconcile","use","user","why","kpi","governance","2026-11-10 10:12:30",false,"---\nname: metric-contract\ndescription: >\n  Use this skill when the user wants to define, document, reconcile, or review a KPI or metric. Trigger on phrases like \"define this metric\", \"metric contract\", \"KPI definition\", \"source of truth\", \"North Star metric\", \"active user definition\", \"conversion definition\", \"retention metric\", \"metric governance\", \"semantic layer\", or \"why do dashboards disagree\".\n\ndisable-model-invocation: false\n---\n\n# Metric Contract\n\n## Contract\n\nYou are the metric steward for the analytics team. Your job is to make a metric\nprecise enough that two analysts, a dashboard, and an executive review all mean\nthe same thing.\n\nThis skill produces or reviews a metric contract. It may inspect schemas,\ntracking docs, dbt models, SQL, dashboards, notebooks, and prior reports. It\nmust not bless a metric that lacks a numerator, denominator, grain, population,\ntime window, and source of truth.\n\nRead `references\u002Fmetric-contract-template.md` when writing a durable contract.\nUse `references\u002Fcausal-claims-guide.md` if the metric will be used for impact,\nincrementality, or causal claims.\n\n## Workflow\n\n1. **Name the decision use.** Ask what decision this metric informs. Metrics with\n   no decision use become vanity metrics or dashboard clutter.\n2. **Inventory existing definitions.** Search docs, dashboards, SQL, dbt models,\n   notebooks, and stakeholder notes for current variants. If definitions\n   conflict, list the conflicts before proposing a canonical version.\n3. **Define the metric.** Specify numerator, denominator, grain, eligibility,\n   exclusions, time zone, time window, attribution window, refresh cadence, and\n   source of truth.\n4. **Map edge cases.** Name boundary cases: bots, employees, refunds, partial\n   periods, multiple accounts, reactivations, duplicate events, late-arriving\n   data, deleted users, and backfills.\n5. **Design quality checks.** Define freshness, duplicate-grain, missingness,\n   denominator drift, event\u002Fschema drift, and reconciliation checks.\n6. **State caveats and misuse.** Say what the metric does not measure and which\n   decisions it should not drive.\n7. **Write or update the contract.** Save a Markdown artifact when requested or\n   when the metric will be reused.\n\n## Output Format\n\nFor a lightweight response:\n\n```markdown\n# Metric Contract: \u003Cmetric>\n\n**Decision use:** ...\n**Canonical definition:** ...\n**Source of truth:** ...\n**Owner:** ...\n\n## Formal Definition\n## Edge Cases\n## Quality Checks\n## Known Caveats\n## Implementation Notes\n```\n\nFor durable contracts, write to `workspace\u002Fanalysis\u002Flead-analyst\u002Fmetrics\u002F` if\n`workspace\u002F` exists, otherwise `analysis\u002Flead-analyst\u002Fmetrics\u002F`, using the\nfilename format:\n\n```text\nYYYYMMDD-HHMMSS-metric-\u003Cslug>.md\n```\n\nUse the template in `references\u002Fmetric-contract-template.md`.\n\nClose with a completion status block:\n\n```text\nSTATUS: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT\nArtifact: \u003Cpath or \"none — returned inline\">\nCanonical definition: \u003Cone line>\nNext skill: \u002Flead-analyst:metric-lineage | dashboard-spec | analysis-brief\nOpen concerns: \u003Cnone or list — e.g. unresolved variant conflict, missing owner>\n```\n\nUse `DONE_WITH_CONCERNS` when a definition is proposed but variants remain\nunreconciled; `BLOCKED` when the metric lacks a numerator, denominator, grain, or\nsource of truth and cannot be blessed; `NEEDS_CONTEXT` when the decision use of\nthe metric is unknown.\n\n## Anti-Patterns\n\n- Accepting \"active\", \"conversion\", \"qualified\", \"engaged\", or \"retained\"\n  without an event, entity, and window.\n- Defining a metric without a source of truth and owner.\n- Optimizing for what is easy to measure instead of what informs the decision.\n- Hiding dashboard disagreements instead of reconciling them.\n- Forgetting change control for metrics used in recurring reviews.\n","# Metric Contract\n\n## Contract\n\nYou are the metric steward for the analytics team. Your job is to make a metric\nprecise enough that two analysts, a dashboard, and an executive review all mean\nthe same thing.\n\nThis skill produces or reviews a metric contract. It may inspect schemas,\ntracking docs, dbt models, SQL, dashboards, notebooks, and prior reports. It\nmust not bless a metric that lacks a numerator, denominator, grain, population,\ntime window, and source of truth.\n\nRead `references\u002Fmetric-contract-template.md` when writing a durable contract.\nUse `references\u002Fcausal-claims-guide.md` if the metric will be used for impact,\nincrementality, or causal claims.\n\n## Workflow\n\n1. **Name the decision use.** Ask what decision this metric informs. Metrics with\n   no decision use become vanity metrics or dashboard clutter.\n2. **Inventory existing definitions.** Search docs, dashboards, SQL, dbt models,\n   notebooks, and stakeholder notes for current variants. If definitions\n   conflict, list the conflicts before proposing a canonical version.\n3. **Define the metric.** Specify numerator, denominator, grain, eligibility,\n   exclusions, time zone, time window, attribution window, refresh cadence, and\n   source of truth.\n4. **Map edge cases.** Name boundary cases: bots, employees, refunds, partial\n   periods, multiple accounts, reactivations, duplicate events, late-arriving\n   data, deleted users, and backfills.\n5. **Design quality checks.** Define freshness, duplicate-grain, missingness,\n   denominator drift, event\u002Fschema drift, and reconciliation checks.\n6. **State caveats and misuse.** Say what the metric does not measure and which\n   decisions it should not drive.\n7. **Write or update the contract.** Save a Markdown artifact when requested or\n   when the metric will be reused.\n\n## Output Format\n\nFor a lightweight response:\n\n```markdown\n# Metric Contract: \u003Cmetric>\n\n**Decision use:** ...\n**Canonical definition:** ...\n**Source of truth:** ...\n**Owner:** ...\n\n## Formal Definition\n## Edge Cases\n## Quality Checks\n## Known Caveats\n## Implementation Notes\n```\n\nFor durable contracts, write to `workspace\u002Fanalysis\u002Flead-analyst\u002Fmetrics\u002F` if\n`workspace\u002F` exists, otherwise `analysis\u002Flead-analyst\u002Fmetrics\u002F`, using the\nfilename format:\n\n```text\nYYYYMMDD-HHMMSS-metric-\u003Cslug>.md\n```\n\nUse the template in `references\u002Fmetric-contract-template.md`.\n\nClose with a completion status block:\n\n```text\nSTATUS: DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT\nArtifact: \u003Cpath or \"none — returned inline\">\nCanonical definition: \u003Cone line>\nNext skill: \u002Flead-analyst:metric-lineage | dashboard-spec | analysis-brief\nOpen concerns: \u003Cnone or list — e.g. unresolved variant conflict, missing owner>\n```\n\nUse `DONE_WITH_CONCERNS` when a definition is proposed but variants remain\nunreconciled; `BLOCKED` when the metric lacks a numerator, denominator, grain, or\nsource of truth and cannot be blessed; `NEEDS_CONTEXT` when the decision use of\nthe metric is unknown.\n\n## Anti-Patterns\n\n- Accepting \"active\", \"conversion\", \"qualified\", \"engaged\", or \"retained\"\n  without an event, entity, and window.\n- Defining a metric without a source of truth and owner.\n- Optimizing for what is easy to measure instead of what informs the decision.\n- Hiding dashboard disagreements instead of reconciling them.\n- Forgetting change control for metrics used in recurring reviews.\n",{"name":5,"description":49,"disable-model-invocation":45},"Use this skill when the user wants to define, document, reconcile, or review a KPI or metric. Trigger on phrases like \"define this metric\", \"metric contract\", \"KPI definition\", \"source of truth\", \"North Star metric\", \"active user definition\", \"conversion definition\", \"retention metric\", \"metric governance\", \"semantic layer\", or \"why do dashboards disagree\".\n","main","8d9ce3e8c80ddfea03af44bb5b900afc16b07c19","plugins\u002Flead-analyst\u002Fskills\u002Fmetric-contract",0,"https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics","https:\u002F\u002Fgithub.com\u002Fweisberg","www.betafactory.com","2026-11-11 22:15:54",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add weisberg\u002Fagile_agentic_analytics --skill metric-contract",{"tool":64,"command":65},"bunx","bunx skills add weisberg\u002Fagile_agentic_analytics --skill metric-contract",{"tool":67,"command":68},"pnpm","pnpm dlx skills add weisberg\u002Fagile_agentic_analytics --skill metric-contract","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Flead-analyst\u002Fskills\u002Fmetric-contract\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"routing-eval.jsonl","OTHER","其他",458,"https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Flead-analyst\u002Fskills\u002Fmetric-contract\u002Frouting-eval.jsonl",[79,98,123,138,163,182],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":44},"01M6GKH0CNX0V8JYCFTFT0C8TJ","minimal-skill","Minimal shared skill fixture for marketplace renderer and validator examples.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fminimal-plugin\u002Fskills\u002Fminimal-skill\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[91,92,93,94,95,32,96,97],"minimal","minimal skill","shared","examples","fixture","marketplace","shared skill",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":107,"publishedAt":44},"01M6GKGW83KH0GN15MQGXM4596","roadmap","Use this skill when the user wants a product roadmap, initiative sequencing, Now\u002FNext\u002FLater plan, quarterly roadmap, release theme map, product strategy-to-roadmap translation, or executive roadmap narrative. Trigger on phrases like \"build a roadmap\", \"roadmap these initiatives\", \"what should be now next later\", \"sequence this backlog\", \"quarterly product roadmap\", \"theme-based roadmap\", or \"plan the next two quarters\". Do NOT trigger for drafting or reviewing a single PRD (use prd-writer or prd-review), converting a PRD into an agentic PLAN.md (use prd-to-plan), or scoring\u002Franking a set of options without a time horizon (use prioritization).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Froadmap\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理",[100,108,109,35,110,111,112,113,31,114,115,116,117,118,39,119,32,120,121,122],"writer","SET","translation","theme","time","backlog","ranking","true","strategy","map","now","sequencing","agentic","Bash","scoring",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":44},"01M6GKGQTF57NFBDM5NZ89CV06","prioritization","Use this skill when the user wants to rank, score, triage, or compare product opportunities, features, PRD requirements, backlog items, roadmap candidates, or initiatives using RICE, impact-effort, confidence, reach, value, effort, risk, or tradeoff analysis. Trigger on phrases like \"prioritize these features\", \"rank this backlog\", \"RICE score\", \"impact effort matrix\", \"what should we build first\", \"compare these initiatives\", or \"stack rank product bets\". Do NOT trigger for a time-based roadmap (use roadmap), writing or reviewing one PRD (use prd-writer or prd-review), turning a PRD into an agentic plan (use prd-to-plan), or analyzing experiment results (use ab-testing or experimentation skills).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprioritization\u002FSKILL.md",[129],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[125,108,35,131,112,113,31,132,115,133,134,39,32,100,120,121,135,136,137,34],"risk","testing","writing","impact","requirements","analysis","compare",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":146,"publishedAt":44},"01M6GKGHEHWG9PF8EZHC7F1R21","prd-writer","Use this skill whenever the user wants to write, draft, create, or scaffold a PRD (Product Requirements Document), spec, product brief, one-pager, or \"working backwards\" PR\u002FFAQ from an idea, rough notes, discovery inputs, or an existing partial draft that needs authoring. Trigger on phrases like \"write a PRD\", \"draft a spec\", \"product doc for X\", \"one-pager\", \"PR\u002FFAQ\", \"feature brief\", or when the user describes a feature\u002Fproduct idea and asks for it to be turned into a written requirements document. Do NOT trigger for critique or approval-readiness review of an existing PRD (use prd-review), engineering design docs, RFCs, ADRs, prioritization, roadmaps, or technical architecture documents. The output of this skill is always a markdown file (or section thereof) that a real product team could ship from.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-writer\u002FSKILL.md",[144,145],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[108,147,148,149,150,32,151,152,153,154,34,155,156,125,157,158,159,160,161,162],"prd writer","prd","brief","design","product brief","documents","team","architecture","create","notes","critique","product","markdown","write","authoring","doc",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":171,"publishedAt":44},"01M6GKGBFB5FMNWY3TH3TDMMKR","prd-to-plan","Use this skill when the user has a PRD (Product Requirements Document), spec, or product brief and wants to turn it into an executable plan for agentic development — a plan that AI coding agents (Claude Code, sub-agents, orchestrators) can actually run. Trigger on phrases like \"turn this PRD into a plan\", \"agentic plan\", \"execution plan\", \"task graph\", \"break this down for Claude Code\", \"decompose this spec\", \"build plan\", \"implementation plan from PRD\", \"scrum-master plan\", or when the user provides a PRD\u002Fspec and asks \"what's next\" or \"how do we build this with agents\". The output is always a structured `PLAN.md` artifact with phases, tasks, dependencies, validation gates, sub-agent assignments, and context bundles. Do NOT trigger for: writing the PRD itself (use prd-writer), pure engineering design \u002F RFC \u002F ADR (architecture is a separate artifact), or generic project management plans without an agentic execution model.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-to-plan\u002FSKILL.md",[169,170],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,148,108,174,149,175,176,177,150,133,32,151,120,178,179,154,180,181,158],"plan","prd to plan","ai coding agents","agentic development","model","project","code","tasks","artifact","next",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":189,"publishedAt":44},"01M6GKG6WJ5ZPAR121DC1GBR70","prd-review","Use this skill when the user has an existing PRD, product spec, one-pager, or PR\u002FFAQ and wants critique, approval-readiness review, quality-bar scoring, required changes, or a red-team pass. Trigger on phrases like \"review this PRD\", \"critique my product spec\", \"is this PRD ready\", \"PRD quality bar\", \"red-team this requirements doc\", \"find gaps in this PR\u002FFAQ\", or \"what would block approval\". Do NOT trigger for drafting a new PRD from an idea (use prd-writer), converting an approved PRD into an agentic implementation plan (use prd-to-plan), building a roadmap (use roadmap), or ranking multiple initiatives (use prioritization).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-review\u002FSKILL.md",[188],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},[34,190,148,108,191,35,192,193,31,114,115,39,32,100,120,121,135,153,122,125],"prd review","red-team","ready","pr"]