[{"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,105,112,137,162],{"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":93,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":97},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":93,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":97},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":97},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":53},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[119,120,121,122,123,124,125,46,126,127,128,36,129,130,131,132,133,134,135,136],"search","deja search","never","error","ready","memory","re","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":53},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[144,145,146,132,147,148,149,150,151,152,153,154,155,156,124,157,158,159,160,161],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":93,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":175,"publishedAt":53},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[168,171,172],{"categoryNo":169,"categoryName":170,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[164,176,177,178,179,180,181,158,182,125,183,184,185,186,36,187,188,189,190,191],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]