[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A0CV7HB0G3S359NCAMWGVT":3,"skill-same:01M7A0CV7HB0G3S359NCAMWGVT":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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7A0CV7HB0G3S359NCAMWGVT","north-star-metric",null,"Define a North Star Metric and 3-5 supporting input metrics that form a metrics constellation. Classify the business game (Attention, Transaction, Productivity) and validate against 7 criteria for an effective North Star. Use when choosing a North Star Metric, setting up a metrics framework, learning about the North Star Framework, or deciding what to measure.","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-marketing-growth\u002Fskills\u002Fnorth-star-metric\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: north-star-metric\ndescription: \"Define a North Star Metric and 3-5 supporting input metrics that form a metrics constellation. Classify the business game (Attention, Transaction, Productivity) and validate against 7 criteria for an effective North Star. Use when choosing a North Star Metric, setting up a metrics framework, learning about the North Star Framework, or deciding what to measure.\"\n---\n# North Star Metric\n\nIdentify a North Star Metric and 3-5 Input Metrics that form a metrics constellation. Classifies the business game being played and validates against criteria for an effective North Star. Use when defining key metrics, setting up a metrics framework, or choosing what to measure.\n\n## Domain Context\n\nNSM is **NOT**: multiple metrics, a revenue\u002FLTV metric (must be customer-centric), an OKR (that's a goal-setting technique), or a strategy (but choosing the right NSM is a strategic choice).\n\nNSM **IS**: a single, customer-centric KPI that reflects the value customers get from the product and serves as a leading indicator of long-term business success. You can use Key Results (OKRs) to express expected change in NSM.\n\nFree resource: [The North Star Framework 101 (PDF)](https:\u002F\u002Flearn.productcompass.pm\u002Fnsm101)\n\n## When to Use\n\n- Defining your company's key metric framework\n- Setting up a metrics tracking system\n- Choosing what to measure and optimize for\n- Evaluating potential North Star candidates\n- Triggers: North Star metric, north star, key metric, what to measure, metrics framework, OMTM\n\n## The Three Business Games\n\nBefore identifying your North Star, classify your business into one of these three games:\n\n- **Attention Game**: How much time do customers spend using your product? (Examples: Facebook, Spotify, YouTube, TikTok)\n- **Transaction Game**: How many transactions occur between customers and your platform? (Examples: Amazon, Uber, Airbnb, PayPal)\n- **Productivity Game**: How efficiently can someone complete their work or achieve their goals? (Examples: Canva, Dropbox, Loom, Notion)\n\n## Prompt\n\nYou are a metrics strategist specializing in North Star metrics and growth measurement frameworks.\n\nGiven the following business context: $ARGUMENTS\n\n**Step 1: Classify the Business Game**\nDetermine which game this company plays: Attention, Transaction, or Productivity.\n\n**Step 2: Identify the North Star Metric**\nSuggest a single metric that meets all seven criteria for an effective North Star:\n\n1. **Easy to Understand**: Clear definition that everyone in the organization comprehends\n2. **Customer-Centric**: Reflects value delivered to customers, not just revenue or activity\n3. **Sustainable Value**: Indicates habits and long-term customer engagement\n4. **Vision Alignment**: Represents meaningful progress toward the company's vision and mission\n5. **Quantitative**: Measurable with clear, numeric tracking\n6. **Actionable**: Teams can directly influence it through product, marketing, and operational changes\n7. **Leading Indicator**: Predicts future business success and revenue growth\n\n**Step 3: Identify Input Metrics**\nDefine 3-5 Input Metrics (also called leading indicators) that most directly influence and drive the North Star Metric. Each input metric should:\n- Be easier to move in the short term\n- Directly contribute to the North Star outcome\n- Help identify where optimization efforts should focus\n\n## Tips for Best Results\n\n- Provide details about your business model and revenue model\n- Share your company's vision, mission, or long-term goals\n- Include current metrics you're tracking\n- Mention key customer segments and use cases\n- Describe the primary value you deliver to customers\n\n---\n\n### Further Reading\n\n- [The North Star Framework 101](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-north-star-framework-101)\n- [AARRR (Pirate) Metrics: The 5-Stage Framework for Growth](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Faarrr-pirate-metrics)\n- [The Google HEART Framework: Your Guide to Measuring User-Centric Success](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-google-heart-framework)\n- [The Ultimate List of Product Metrics](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-ultimate-list-of-product-metrics)\n","# North Star Metric\n\nIdentify a North Star Metric and 3-5 Input Metrics that form a metrics constellation. Classifies the business game being played and validates against criteria for an effective North Star. Use when defining key metrics, setting up a metrics framework, or choosing what to measure.\n\n## Domain Context\n\nNSM is **NOT**: multiple metrics, a revenue\u002FLTV metric (must be customer-centric), an OKR (that's a goal-setting technique), or a strategy (but choosing the right NSM is a strategic choice).\n\nNSM **IS**: a single, customer-centric KPI that reflects the value customers get from the product and serves as a leading indicator of long-term business success. You can use Key Results (OKRs) to express expected change in NSM.\n\nFree resource: [The North Star Framework 101 (PDF)](https:\u002F\u002Flearn.productcompass.pm\u002Fnsm101)\n\n## When to Use\n\n- Defining your company's key metric framework\n- Setting up a metrics tracking system\n- Choosing what to measure and optimize for\n- Evaluating potential North Star candidates\n- Triggers: North Star metric, north star, key metric, what to measure, metrics framework, OMTM\n\n## The Three Business Games\n\nBefore identifying your North Star, classify your business into one of these three games:\n\n- **Attention Game**: How much time do customers spend using your product? (Examples: Facebook, Spotify, YouTube, TikTok)\n- **Transaction Game**: How many transactions occur between customers and your platform? (Examples: Amazon, Uber, Airbnb, PayPal)\n- **Productivity Game**: How efficiently can someone complete their work or achieve their goals? (Examples: Canva, Dropbox, Loom, Notion)\n\n## Prompt\n\nYou are a metrics strategist specializing in North Star metrics and growth measurement frameworks.\n\nGiven the following business context: $ARGUMENTS\n\n**Step 1: Classify the Business Game**\nDetermine which game this company plays: Attention, Transaction, or Productivity.\n\n**Step 2: Identify the North Star Metric**\nSuggest a single metric that meets all seven criteria for an effective North Star:\n\n1. **Easy to Understand**: Clear definition that everyone in the organization comprehends\n2. **Customer-Centric**: Reflects value delivered to customers, not just revenue or activity\n3. **Sustainable Value**: Indicates habits and long-term customer engagement\n4. **Vision Alignment**: Represents meaningful progress toward the company's vision and mission\n5. **Quantitative**: Measurable with clear, numeric tracking\n6. **Actionable**: Teams can directly influence it through product, marketing, and operational changes\n7. **Leading Indicator**: Predicts future business success and revenue growth\n\n**Step 3: Identify Input Metrics**\nDefine 3-5 Input Metrics (also called leading indicators) that most directly influence and drive the North Star Metric. Each input metric should:\n- Be easier to move in the short term\n- Directly contribute to the North Star outcome\n- Help identify where optimization efforts should focus\n\n## Tips for Best Results\n\n- Provide details about your business model and revenue model\n- Share your company's vision, mission, or long-term goals\n- Include current metrics you're tracking\n- Mention key customer segments and use cases\n- Describe the primary value you deliver to customers\n\n---\n\n### Further Reading\n\n- [The North Star Framework 101](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-north-star-framework-101)\n- [AARRR (Pirate) Metrics: The 5-Stage Framework for Growth](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Faarrr-pirate-metrics)\n- [The Google HEART Framework: Your Guide to Measuring User-Centric Success](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-google-heart-framework)\n- [The Ultimate List of Product Metrics](https:\u002F\u002Fwww.productcompass.pm\u002Fp\u002Fthe-ultimate-list-of-product-metrics)\n",{"name":5,"description":7},"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fpm-skills\u002Fpm-marketing-growth\u002Fskills\u002Fnorth-star-metric","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kongnakornna\u002Fgolangapi --skill north-star-metric",{"tool":38,"command":39},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill north-star-metric",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill north-star-metric","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpm-skills\u002Fpm-marketing-growth\u002Fskills\u002Fnorth-star-metric\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"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},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]