[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T07EZ9D234JSVJD547FST":3,"skill-same:01M77T07EZ9D234JSVJD547FST":49},{"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},"01M77T07EZ9D234JSVJD547FST","traction-critical-path",null,"Set traction goals and identify the Critical Path from Traction so teams focus only on milestones needed for growth. Use when a startup has too many priorities, needs growth goals, is debating product versus marketing work, or wants to decide what not to do.","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\u002Ftraction-critical-path\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: traction-critical-path\ndescription: Set traction goals and identify the Critical Path from Traction so teams focus only on milestones needed for growth. Use when a startup has too many priorities, needs growth goals, is debating product versus marketing work, or wants to decide what not to do.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Traction Critical Path\n  category: Marketing\n  tags: traction,growth,strategy,startups,prioritization\n---\n\n# Traction Critical Path\n\nUse this skill to convert an ambiguous growth objective into a measurable\ntraction goal, required milestones, and a disciplined \"not now\" list.\n\n## Source Traceability\n\nPrimary source: Traction, chapters 2 and 5.\n\n- Chapter 2 covers the 50 percent rule, moving the needle, growth phases, and\n  bright spots. Authoring notes: converted lines 394-554.\n- Chapter 5 defines traction goals, Critical Path milestones, reassessment, and\n  channel bias. Authoring notes: converted lines 787-902.\n\n## Workflow\n\n### 1. Identify The Growth Stage\n\nClassify the current stage:\n\n| Stage | Main Question | Typical Goal |\n|-------|---------------|--------------|\n| Phase I | Can the product get real traction? | First engaged customers or proof of demand |\n| Phase II | Can this become sustainable? | Enough customers or revenue to approach sustainability |\n| Phase III | Can this scale profitably? | Larger growth, market position, or profit expansion |\n\nIf the product is early, keep tests small and feedback-rich. If it is later,\ninsist on goals large enough to move the business.\n\n### 2. Define The Traction Goal\n\nThe traction goal should be quantitative, time-bound, and meaningful enough to\nchange the company's situation.\n\nGood goals include:\n\n- Reach 1,000 paying customers by a date.\n- Add 100 qualified trials per week.\n- Hit a break-even revenue number.\n- Reach a market-share threshold that changes partnership or investor leverage.\n\nWeak goals include:\n\n- Get more awareness.\n- Do marketing.\n- Improve engagement without defining the metric.\n\n### 3. Work Backward Into Necessary Milestones\n\nList milestones that are absolutely necessary to hit the goal. Include product,\ndistribution, hiring, analytics, partnership, or operational milestones only if\nthey are required.\n\nFor each candidate milestone, ask:\n\n- If this does not happen, can we still hit the traction goal?\n- Is this a prerequisite or just attractive?\n- What evidence supports this being necessary?\n- What would make us remove or replace it?\n\n### 4. Cut Off-Path Work\n\nCreate an explicit off-path list. This matters because founders often spend\nscarce time on useful work that is not necessary for the current traction goal.\n\nOff-path work can include:\n\n- Feature requests that do not unlock the next growth stage.\n- Marketing activities that cannot move the needle.\n- Partnerships, events, or content that produce activity without traction.\n- Infrastructure polish that does not affect the current bottleneck.\n\n### 5. Reassess After Every Milestone\n\nThe Critical Path changes as evidence changes. After each milestone, update:\n\n- Goal confidence.\n- Bottleneck.\n- Milestone order.\n- Off-path list.\n- Next test or build decision.\n\n## Output Format\n\n```markdown\n# Critical Path Plan\n\n## Traction Goal\n- Metric:\n- Target:\n- Deadline:\n- Why it matters:\n\n## Stage\n[Phase I, II, or III, with reasoning.]\n\n## Critical Path\n| Order | Milestone | Why Required | Evidence Needed | Owner\u002FDeadline |\n|-------|-----------|--------------|-----------------|----------------|\n\n## Off-Path List\n| Activity | Why It Is Off Path | Revisit Trigger |\n|----------|--------------------|-----------------|\n\n## Reassessment Cadence\n- Review after:\n- Metrics to inspect:\n- Decision rules:\n```\n\n## Quality Bar\n\n- Do not accept vague growth goals.\n- Do not include milestones merely because they are valuable.\n- Do not let product work crowd out traction work by default.\n- Name bright spots when growth is weak but some users are highly engaged.\n- Recommend a pivot only after checking engagement evidence and timing risk.\n","# Traction Critical Path\n\nUse this skill to convert an ambiguous growth objective into a measurable\ntraction goal, required milestones, and a disciplined \"not now\" list.\n\n## Source Traceability\n\nPrimary source: Traction, chapters 2 and 5.\n\n- Chapter 2 covers the 50 percent rule, moving the needle, growth phases, and\n  bright spots. Authoring notes: converted lines 394-554.\n- Chapter 5 defines traction goals, Critical Path milestones, reassessment, and\n  channel bias. Authoring notes: converted lines 787-902.\n\n## Workflow\n\n### 1. Identify The Growth Stage\n\nClassify the current stage:\n\n| Stage | Main Question | Typical Goal |\n|-------|---------------|--------------|\n| Phase I | Can the product get real traction? | First engaged customers or proof of demand |\n| Phase II | Can this become sustainable? | Enough customers or revenue to approach sustainability |\n| Phase III | Can this scale profitably? | Larger growth, market position, or profit expansion |\n\nIf the product is early, keep tests small and feedback-rich. If it is later,\ninsist on goals large enough to move the business.\n\n### 2. Define The Traction Goal\n\nThe traction goal should be quantitative, time-bound, and meaningful enough to\nchange the company's situation.\n\nGood goals include:\n\n- Reach 1,000 paying customers by a date.\n- Add 100 qualified trials per week.\n- Hit a break-even revenue number.\n- Reach a market-share threshold that changes partnership or investor leverage.\n\nWeak goals include:\n\n- Get more awareness.\n- Do marketing.\n- Improve engagement without defining the metric.\n\n### 3. Work Backward Into Necessary Milestones\n\nList milestones that are absolutely necessary to hit the goal. Include product,\ndistribution, hiring, analytics, partnership, or operational milestones only if\nthey are required.\n\nFor each candidate milestone, ask:\n\n- If this does not happen, can we still hit the traction goal?\n- Is this a prerequisite or just attractive?\n- What evidence supports this being necessary?\n- What would make us remove or replace it?\n\n### 4. Cut Off-Path Work\n\nCreate an explicit off-path list. This matters because founders often spend\nscarce time on useful work that is not necessary for the current traction goal.\n\nOff-path work can include:\n\n- Feature requests that do not unlock the next growth stage.\n- Marketing activities that cannot move the needle.\n- Partnerships, events, or content that produce activity without traction.\n- Infrastructure polish that does not affect the current bottleneck.\n\n### 5. Reassess After Every Milestone\n\nThe Critical Path changes as evidence changes. After each milestone, update:\n\n- Goal confidence.\n- Bottleneck.\n- Milestone order.\n- Off-path list.\n- Next test or build decision.\n\n## Output Format\n\n```markdown\n# Critical Path Plan\n\n## Traction Goal\n- Metric:\n- Target:\n- Deadline:\n- Why it matters:\n\n## Stage\n[Phase I, II, or III, with reasoning.]\n\n## Critical Path\n| Order | Milestone | Why Required | Evidence Needed | Owner\u002FDeadline |\n|-------|-----------|--------------|-----------------|----------------|\n\n## Off-Path List\n| Activity | Why It Is Off Path | Revisit Trigger |\n|----------|--------------------|-----------------|\n\n## Reassessment Cadence\n- Review after:\n- Metrics to inspect:\n- Decision rules:\n```\n\n## Quality Bar\n\n- Do not accept vague growth goals.\n- Do not include milestones merely because they are valuable.\n- Do not let product work crowd out traction work by default.\n- Name bright spots when growth is weak but some users are highly engaged.\n- Recommend a pivot only after checking engagement evidence and timing risk.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"traction,growth,strategy,startups,prioritization","0.1.0","Marketing","Traction Critical Path","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Ftraction-critical-path","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 traction-critical-path",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill traction-critical-path",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill traction-critical-path","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Ftraction-critical-path\u002FSKILL.md",true,[],[50,59,66,74,81,88],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"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":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":54,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]