[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MC5R77JFAFV19ER70804WS":3,"skill-same:01M6MC5R77JFAFV19ER70804WS":89},{"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":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6MC5R77JFAFV19ER70804WS","eighty-twenty-power-curve",null,"Apply 80\u002F20 power-curve thinking to sales, marketing, customers, offers, traffic, time, and operations. Use when finding leverage, diagnosing uneven results, prioritizing high-upside segments, or replacing average-based reasoning with Pareto and power-law analysis.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Feighty-twenty-power-curve\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,53],"eighty twenty power curve","curve","power","time","pareto","when","apply","high","traffic","segments","with","leverage","codex","thinking","use","operations","sales","results","marketing","prioritization","analysis","code","2026-11-10 10:12:30",false,"---\nname: eighty-twenty-power-curve\ndescription: Apply 80\u002F20 power-curve thinking to sales, marketing, customers, offers, traffic, time, and operations. Use when finding leverage, diagnosing uneven results, prioritizing high-upside segments, or replacing average-based reasoning with Pareto and power-law analysis.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: 80\u002F20 Power Curve\n  category: Marketing\n  tags: eighty-twenty,pareto,sales,marketing,prioritization\n---\n\n# 80\u002F20 Power Curve\n\nUse this skill to find where a small minority of inputs creates most of the\nvalue, cost, waste, demand, or opportunity. It is based on 80\u002F20 Sales and\nMarketing by Perry Marshall.\n\n## Source Traceability\n\nPrimary source: 80\u002F20 Sales and Marketing, chapters 1, 5, 14, and the appendix.\n\n- Chapter 1 introduces compounding 80\u002F20 behavior and warns against average\n  thinking.\n- Chapter 5 applies the power curve to business opportunity and resource shifts.\n- Chapter 14 explains why positive feedback creates non-linear outcomes.\n- The appendix gives the math-oriented version of the power curve.\n\n## Workflow\n\n### 1. Name The Population\n\nDefine the set being ranked:\n\n- Customers, leads, products, pages, ads, keywords, salespeople, tasks, support\n  issues, markets, partners, content assets, or campaigns.\n- Time window.\n- Outcome metric: revenue, profit, conversions, usage, retention, attention,\n  qualified pipeline, cost, complaints, or effort.\n\nIf the user provides only averages, ask for raw counts or ranked items. If raw\ndata is unavailable, create an explicit estimate and label it.\n\n### 2. Rank By The Outcome That Matters\n\nSort items from strongest to weakest. Prefer profit or qualified action over\nsurface volume.\n\nUse these questions:\n\n- Which few items create most of the upside?\n- Which few items create most of the waste?\n- What is the best item worth compared with the median?\n- Where does the distribution drop sharply?\n- What would change if resources moved from the weak tail to the strong head?\n\n### 3. Look For Nested 80\u002F20\n\nAfter finding the top 20 percent, look inside that group for the top 20 percent\nagain. Stop when the data becomes too thin to interpret.\n\nUseful nested cuts:\n\n- Top customers inside the top customer segment.\n- Best ads inside the best campaign.\n- Highest-intent keywords inside the best keyword cluster.\n- Best tasks inside the highest-value role.\n\n### 4. Decide The Resource Shift\n\nRecommend one of four moves:\n\n- Double down on the strongest items.\n- Split-test or refine the items near the threshold.\n- Stop, delegate, or automate the weak tail.\n- Gather better data before acting.\n\nDo not recommend optimization of the average item unless it unlocks a stronger\npower-curve move.\n\n## Output Format\n\n```markdown\n# 80\u002F20 Power Curve Analysis\n\n## Population\n- Items ranked:\n- Time window:\n- Outcome metric:\n- Data quality:\n\n## Power-Curve Findings\n| Rank\u002FSegment | Item Or Group | Outcome | Interpretation |\n|--------------|---------------|---------|----------------|\n\n## Nested 80\u002F20\n- Strongest sub-segment:\n- Weak tail:\n- Biggest surprise:\n\n## Recommended Resource Shift\n- Move resources from:\n- Move resources to:\n- Expected effect:\n- Data still needed:\n```\n\n## Quality Bar\n\n- Do not use averages as the main conclusion.\n- Do not treat all customers, leads, channels, or tasks as equal.\n- Separate upside concentration from waste concentration.\n- Prefer profit, qualified action, or strategic value over raw volume.\n- Label assumptions when exact ranked data is missing.\n","# 80\u002F20 Power Curve\n\nUse this skill to find where a small minority of inputs creates most of the\nvalue, cost, waste, demand, or opportunity. It is based on 80\u002F20 Sales and\nMarketing by Perry Marshall.\n\n## Source Traceability\n\nPrimary source: 80\u002F20 Sales and Marketing, chapters 1, 5, 14, and the appendix.\n\n- Chapter 1 introduces compounding 80\u002F20 behavior and warns against average\n  thinking.\n- Chapter 5 applies the power curve to business opportunity and resource shifts.\n- Chapter 14 explains why positive feedback creates non-linear outcomes.\n- The appendix gives the math-oriented version of the power curve.\n\n## Workflow\n\n### 1. Name The Population\n\nDefine the set being ranked:\n\n- Customers, leads, products, pages, ads, keywords, salespeople, tasks, support\n  issues, markets, partners, content assets, or campaigns.\n- Time window.\n- Outcome metric: revenue, profit, conversions, usage, retention, attention,\n  qualified pipeline, cost, complaints, or effort.\n\nIf the user provides only averages, ask for raw counts or ranked items. If raw\ndata is unavailable, create an explicit estimate and label it.\n\n### 2. Rank By The Outcome That Matters\n\nSort items from strongest to weakest. Prefer profit or qualified action over\nsurface volume.\n\nUse these questions:\n\n- Which few items create most of the upside?\n- Which few items create most of the waste?\n- What is the best item worth compared with the median?\n- Where does the distribution drop sharply?\n- What would change if resources moved from the weak tail to the strong head?\n\n### 3. Look For Nested 80\u002F20\n\nAfter finding the top 20 percent, look inside that group for the top 20 percent\nagain. Stop when the data becomes too thin to interpret.\n\nUseful nested cuts:\n\n- Top customers inside the top customer segment.\n- Best ads inside the best campaign.\n- Highest-intent keywords inside the best keyword cluster.\n- Best tasks inside the highest-value role.\n\n### 4. Decide The Resource Shift\n\nRecommend one of four moves:\n\n- Double down on the strongest items.\n- Split-test or refine the items near the threshold.\n- Stop, delegate, or automate the weak tail.\n- Gather better data before acting.\n\nDo not recommend optimization of the average item unless it unlocks a stronger\npower-curve move.\n\n## Output Format\n\n```markdown\n# 80\u002F20 Power Curve Analysis\n\n## Population\n- Items ranked:\n- Time window:\n- Outcome metric:\n- Data quality:\n\n## Power-Curve Findings\n| Rank\u002FSegment | Item Or Group | Outcome | Interpretation |\n|--------------|---------------|---------|----------------|\n\n## Nested 80\u002F20\n- Strongest sub-segment:\n- Weak tail:\n- Biggest surprise:\n\n## Recommended Resource Shift\n- Move resources from:\n- Move resources to:\n- Expected effect:\n- Data still needed:\n```\n\n## Quality Bar\n\n- Do not use averages as the main conclusion.\n- Do not treat all customers, leads, channels, or tasks as equal.\n- Separate upside concentration from waste concentration.\n- Prefer profit, qualified action, or strategic value over raw volume.\n- Label assumptions when exact ranked data is missing.\n",{"name":5,"license":15,"metadata":59,"description":7,"compatibility":64},{"tags":60,"version":61,"category":62,"displayName":63},"eighty-twenty,pareto,sales,marketing,prioritization","0.1.0","Marketing","80\u002F20 Power Curve","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Feighty-twenty-power-curve",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill eighty-twenty-power-curve",{"tool":81,"command":82},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill eighty-twenty-power-curve",{"tool":84,"command":85},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill eighty-twenty-power-curve","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Feighty-twenty-power-curve\u002FSKILL.md",true,[],[90,99,106,113,139,163],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":98},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":98},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":98},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":54},"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",[],[120,121,122,123,124,125,126,127,128,129,130,37,131,132,133,134,135,136,137,138],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":54},"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",[],[146,147,148,134,42,149,150,151,152,153,154,155,156,157,125,158,159,160,161,162],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":176,"publishedAt":54},"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",[169,172,173],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[165,177,178,179,180,181,182,159,183,126,184,185,186,187,37,188,189,190,191,192],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]