[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCSWW5DPBZZB2ZVZDR27ZV":3,"skill-same:01M6MCSWW5DPBZZB2ZVZDR27ZV":88},{"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":31,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6MCSWW5DPBZZB2ZVZDR27ZV","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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftraction-critical-path\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"traction critical path","path","critical","only","when","milestones","for","startups","focus","priorities","do","teams","use","strategy","decide","work","marketing","prioritization","SET","product","code","2026-11-10 10:12:30",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":15,"metadata":58,"description":7,"compatibility":63},{"tags":59,"version":60,"category":61,"displayName":62},"traction,growth,strategy,startups,prioritization","0.1.0","Marketing","Traction Critical Path","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftraction-critical-path",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill traction-critical-path",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill traction-critical-path",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill traction-critical-path","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftraction-critical-path\u002FSKILL.md",true,[],[89,98,106,114,122,130],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"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":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":97},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":97},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":97},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":97},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":97},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]