[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SM7STDB0MK0P70CXCXW19":3,"skill-same:01M77SM7STDB0MK0P70CXCXW19":59},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SM7STDB0MK0P70CXCXW19","customer-segment-slicing",null,"Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-segment-slicing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customer-segment-slicing\ndescription: Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.3\"\n  displayName: Customer Segment Slicing\n  category: Marketing\n  tags: customer-discovery,segmentation,startups,positioning,research\n---\n\n# Customer Segment Slicing\n\nUse this skill before customer conversations, traction tests, sales outreach, or\npersona work when the target customer is too broad to produce consistent\nevidence. A useful segment is a who-where pair: who has the problem and where\nthe team can find them.\n\n## Source Traceability\n\nPrimary source: The Mom Test by Rob Fitzpatrick, especially chapters 6-7.\nGuidance is paraphrased for this MIT repo; authoring notes used converted EPUB\nlines 2791-3610.\n\n## Slicing Workflow\n\n1. Start with the broad audience or market.\n2. Split by demographics, role, use case, behavior, buying context, urgency, or\n   current workaround.\n3. For each slice, state the motivation or problem that makes them care.\n4. Keep slicing any group that still produces mixed goals or feature requests.\n5. Add where to find each group: communities, events, tools, platforms, job\n   titles, search queries, partners, directories, or physical locations.\n6. Score the slices by reachability, expected value, urgency, consistency, and\n   team fit.\n7. Pick one starting segment for the next discovery or traction pass.\n\n## Useful Segment Tests\n\nAsk:\n\n- Would most people in this slice share the same problem or goal?\n- Can we find at least five of them this week?\n- Do they already spend time, money, attention, or reputation on this problem?\n- Would their feedback point toward one product direction rather than many?\n- Are there hidden stakeholders, buyers, users, or partners?\n- Is this slice narrow enough to learn from but valuable enough to matter?\n\n## Output Format\n\n```markdown\n# Customer Segment Slicing\n\n## Broad Segment\n[Starting audience.]\n\n## Candidate Slices\n| Segment | Problem or Goal | Where To Find Them | Current Behavior | Reachability | Value | Urgency | Consistency | Fit |\n|---------|-----------------|--------------------|------------------|--------------|-------|---------|-------------|-----|\n\n## Recommended Starting Segment\n[One who-where pair.]\n\n## Why This Segment\n- Strong shared motivation:\n- Easy access path:\n- Evidence to gather:\n- Risks:\n\n## Next Conversations\n1. [Person\u002Fsource]\n2. [Person\u002Fsource]\n3. [Person\u002Fsource]\n```\n\n## Workflow\n\nUse `workflows\u002Fslice-customer-segment.md` for a full segmentation pass.\n\n## Quality Bar\n\n- Do not accept categories like \"students\", \"businesses\", or \"creators\" without\n  further slicing.\n- Do not optimize positioning or features from mixed-segment feedback.\n- Do not choose a segment that cannot be found.\n- Do not talk only to impressive people if they are not representative users,\n  buyers, or stakeholders.\n","# Customer Segment Slicing\n\nUse this skill before customer conversations, traction tests, sales outreach, or\npersona work when the target customer is too broad to produce consistent\nevidence. A useful segment is a who-where pair: who has the problem and where\nthe team can find them.\n\n## Source Traceability\n\nPrimary source: The Mom Test by Rob Fitzpatrick, especially chapters 6-7.\nGuidance is paraphrased for this MIT repo; authoring notes used converted EPUB\nlines 2791-3610.\n\n## Slicing Workflow\n\n1. Start with the broad audience or market.\n2. Split by demographics, role, use case, behavior, buying context, urgency, or\n   current workaround.\n3. For each slice, state the motivation or problem that makes them care.\n4. Keep slicing any group that still produces mixed goals or feature requests.\n5. Add where to find each group: communities, events, tools, platforms, job\n   titles, search queries, partners, directories, or physical locations.\n6. Score the slices by reachability, expected value, urgency, consistency, and\n   team fit.\n7. Pick one starting segment for the next discovery or traction pass.\n\n## Useful Segment Tests\n\nAsk:\n\n- Would most people in this slice share the same problem or goal?\n- Can we find at least five of them this week?\n- Do they already spend time, money, attention, or reputation on this problem?\n- Would their feedback point toward one product direction rather than many?\n- Are there hidden stakeholders, buyers, users, or partners?\n- Is this slice narrow enough to learn from but valuable enough to matter?\n\n## Output Format\n\n```markdown\n# Customer Segment Slicing\n\n## Broad Segment\n[Starting audience.]\n\n## Candidate Slices\n| Segment | Problem or Goal | Where To Find Them | Current Behavior | Reachability | Value | Urgency | Consistency | Fit |\n|---------|-----------------|--------------------|------------------|--------------|-------|---------|-------------|-----|\n\n## Recommended Starting Segment\n[One who-where pair.]\n\n## Why This Segment\n- Strong shared motivation:\n- Easy access path:\n- Evidence to gather:\n- Risks:\n\n## Next Conversations\n1. [Person\u002Fsource]\n2. [Person\u002Fsource]\n3. [Person\u002Fsource]\n```\n\n## Workflow\n\nUse `workflows\u002Fslice-customer-segment.md` for a full segmentation pass.\n\n## Quality Bar\n\n- Do not accept categories like \"students\", \"businesses\", or \"creators\" without\n  further slicing.\n- Do not optimize positioning or features from mixed-segment feedback.\n- Do not choose a segment that cannot be found.\n- Do not talk only to impressive people if they are not representative users,\n  buyers, or stakeholders.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"customer-discovery,segmentation,startups,positioning,research","0.1.3","Marketing","Customer Segment Slicing","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-segment-slicing","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-segment-slicing",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-segment-slicing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill customer-segment-slicing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-segment-slicing\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-segment-slicing\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"workflows\u002Fslice-customer-segment.md",1332,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fcustomer-segment-slicing\u002Fworkflows\u002Fslice-customer-segment.md",[60,69,76,84,91,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\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},"01M77Y7AA8N45G6NM0WJSS2W9C","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\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":64,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]