[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754SA5AGBXD7YWXMZYJHXVB":3,"skill-same:01M754SA5AGBXD7YWXMZYJHXVB":63},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M754SA5AGBXD7YWXMZYJHXVB","org-health-diagnostic",null,"Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.","ASoudy\u002FAGS","ASoudy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F40639702?v=4","01M74G5NTCW8MWDNRTAF303PA1","01M74G5NTZXSE6T0GZR5BCB6V0",0,"MIT","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"org-health-diagnostic\"\ndescription: \"Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: organizational-health\n  updated: 2026-03-05\n  python-tools: health_scorer.py\n  frameworks: health-benchmarks\n---\n\n# Org Health Diagnostic\n\nEight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.\n\n## Keywords\norg health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard\n\n## Quick Start\n\n```bash\npython scripts\u002Fhealth_scorer.py        # Guided CLI — enter metrics, get scored dashboard\npython scripts\u002Fhealth_scorer.py --json # Output raw JSON for integration\n```\n\nOr describe your metrics:\n```\n\u002Fhealth [paste your key metrics or answer prompts]\n\u002Fhealth:dimension [financial|revenue|product|engineering|people|ops|security|market]\n```\n\n## The 8 Dimensions\n\n### 1. 💰 Financial Health (CFO)\n**What it measures:** Can we fund operations and invest in growth?\n\nKey metrics:\n- **Runway** — months at current burn (Green: >12, Yellow: 6-12, Red: \u003C6)\n- **Burn multiple** — net burn \u002F net new ARR (Green: \u003C1.5x, Yellow: 1.5-2.5x, Red: >2.5x)\n- **Gross margin** — SaaS target: >65% (Green: >70%, Yellow: 55-70%, Red: \u003C55%)\n- **MoM growth rate** — contextual by stage (see benchmarks)\n- **Revenue concentration** — top customer % of ARR (Green: \u003C15%, Yellow: 15-25%, Red: >25%)\n\n### 2. 📈 Revenue Health (CRO)\n**What it measures:** Are customers staying, growing, and recommending us?\n\nKey metrics:\n- **NRR (Net Revenue Retention)** — Green: >110%, Yellow: 100-110%, Red: \u003C100%\n- **Logo churn rate (annualized)** — Green: \u003C5%, Yellow: 5-10%, Red: >10%\n- **Pipeline coverage (next quarter)** — Green: >3x, Yellow: 2-3x, Red: \u003C2x\n- **CAC payback period** — Green: \u003C12 months, Yellow: 12-18, Red: >18 months\n- **Average ACV trend** — directional: growing, flat, declining\n\n### 3. 🚀 Product Health (CPO)\n**What it measures:** Do customers love and use the product?\n\nKey metrics:\n- **NPS** — Green: >40, Yellow: 20-40, Red: \u003C20\n- **DAU\u002FMAU ratio** — engagement proxy (Green: >40%, Yellow: 20-40%, Red: \u003C20%)\n- **Core feature adoption** — % of users using primary value feature (Green: >60%)\n- **Time-to-value** — days from signup to first core action (lower is better)\n- **Customer satisfaction (CSAT)** — Green: >4.2\u002F5, Yellow: 3.5-4.2, Red: \u003C3.5\n\n### 4. ⚙️ Engineering Health (CTO)\n**What it measures:** Can we ship reliably and sustain velocity?\n\nKey metrics:\n- **Deployment frequency** — Green: daily, Yellow: weekly, Red: monthly or less\n- **Change failure rate** — % of deployments causing incidents (Green: \u003C5%, Red: >15%)\n- **Mean time to recovery (MTTR)** — Green: \u003C1 hour, Yellow: 1-4 hours, Red: >4 hours\n- **Tech debt ratio** — % of sprint capacity on debt (Green: \u003C20%, Yellow: 20-35%, Red: >35%)\n- **Incident frequency** — P0\u002FP1 per month (Green: \u003C2, Yellow: 2-5, Red: >5)\n\n### 5. 👥 People Health (CHRO)\n**What it measures:** Is the team stable, engaged, and growing?\n\nKey metrics:\n- **Regrettable attrition (annualized)** — Green: \u003C10%, Yellow: 10-20%, Red: >20%\n- **Engagement score** — (eNPS or similar; Green: >30, Yellow: 0-30, Red: \u003C0)\n- **Time-to-fill (avg days)** — Green: \u003C45, Yellow: 45-90, Red: >90\n- **Manager-to-IC ratio** — Green: 1:5–1:8, Yellow: 1:3–1:5 or 1:8–1:12, Red: outside\n- **Internal promotion rate** — at least 25-30% of senior roles filled internally\n\n### 6. 🔄 Operational Health (COO)\n**What it measures:** Are we executing our strategy with discipline?\n\nKey metrics:\n- **OKR completion rate** — % of key results hitting target (Green: >70%, Yellow: 50-70%, Red: \u003C50%)\n- **Decision cycle time** — days from decision needed to decision made (Green: \u003C48h, Yellow: 48h-1w)\n- **Meeting effectiveness** — % of meetings with clear outcome (qualitative)\n- **Process maturity** — level 1-5 scale (see COO advisor)\n- **Cross-functional initiative completion** — % on time, on scope\n\n### 7. 🔒 Security Health (CISO)\n**What it measures:** Are we protecting customers and maintaining compliance?\n\nKey metrics:\n- **Security incidents (last 90 days)** — Green: 0, Yellow: 1-2 minor, Red: 1+ major\n- **Compliance status** — certifications current\u002Fin-progress vs. overdue\n- **Vulnerability remediation SLA** — % of critical CVEs patched within SLA (Green: 100%)\n- **Security training completion** — % of team current (Green: >95%)\n- **Pen test recency** — Green: \u003C12 months, Yellow: 12-24, Red: >24 months\n\n### 8. 📣 Market Health (CMO)\n**What it measures:** Are we winning in the market and growing efficiently?\n\nKey metrics:\n- **CAC trend** — improving, flat, or worsening QoQ\n- **Organic vs paid lead mix** — more organic = healthier (less fragile)\n- **Win rate** — % of qualified opportunities closed-won (Green: >25%, Yellow: 15-25%, Red: \u003C15%)\n- **Competitive win rate** — against primary competitors specifically\n- **Brand NPS** — awareness + preference scores in ICP\n\n---\n\n## Scoring & Traffic Lights\n\nEach dimension is scored 1-10 with traffic light:\n- 🟢 **Green (7-10):** Healthy — maintain and optimize\n- 🟡 **Yellow (4-6):** Watch — trend matters; improving or declining?\n- 🔴 **Red (1-3):** Action required — address within 30 days\n\n**Overall Health Score:**\nWeighted average by company stage (see `references\u002Fhealth-benchmarks.md` for weights).\n\n---\n\n## Dimension Interactions (Why One Problem Creates Another)\n\n| If this dimension is red... | Watch these dimensions next |\n|-----------------------------|----------------------------|\n| Financial Health | People (freeze hiring) → Engineering (freeze infra) → Product (cut scope) |\n| Revenue Health | Financial (cash gap) → People (attrition risk) → Market (lose positioning) |\n| People Health | Engineering (velocity drops) → Product (quality drops) → Revenue (churn rises) |\n| Engineering Health | Product (features slip) → Revenue (deals stall on product) |\n| Product Health | Revenue (NRR drops, churn rises) → Market (CAC rises; referrals dry up) |\n| Operational Health | All dimensions degrade over time (execution failure cascades everywhere) |\n\n---\n\n## Dashboard Output Format\n\n```\nORG HEALTH DIAGNOSTIC — [Company] — [Date]\nStage: [Seed\u002FA\u002FB\u002FC]   Overall: [Score]\u002F10   Trend: [↑ Improving \u002F → Stable \u002F ↓ Declining]\n\nDIMENSION SCORES\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n💰 Financial    🟢 8.2  Runway 14mo, burn 1.6x — strong\n📈 Revenue      🟡 5.8  NRR 104%, pipeline thin (1.8x coverage)\n🚀 Product      🟢 7.4  NPS 42, DAU\u002FMAU 38%\n⚙️  Engineering  🟡 5.2  Debt at 30%, MTTR 3.2h\n👥 People       🔴 3.8  Attrition 24%, eng morale low\n🔄 Operations   🟡 6.0  OKR 65% completion\n🔒 Security     🟢 7.8  SOC 2 Type II complete, 0 incidents\n📣 Market       🟡 5.5  CAC rising, win rate dropped to 22%\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTOP PRIORITIES\n🔴 [1] People: attrition at 24% — engineering velocity will drop in 60 days\n   Action: CHRO + CEO to run retention audit; target top 5 at-risk this week\n🟡 [2] Revenue: pipeline coverage at 1.8x — Q+1 miss risk is high\n   Action: CRO to add 3 qualified opps within 30 days or shift forecast down\n🟡 [3] Engineering: tech debt at 30% of sprint — shipping will slow by Q3\n   Action: CTO to propose debt sprint plan; COO to protect capacity\n\nWATCH\n→ People → Engineering cascade risk if attrition continues (see dimension interactions)\n```\n\n---\n\n## Graceful Degradation\n\nYou don't need all metrics to run a diagnostic. The tool handles partial data:\n- Missing metric → excluded from score, flagged as \"[data needed]\"\n- Score still valid for available dimensions\n- Report flags which gaps to fill for next cycle\n\n## References\n- `references\u002Fhealth-benchmarks.md` — benchmarks by stage (Seed, A, B, C)\n- `scripts\u002Fhealth_scorer.py` — CLI scoring tool with traffic light output\n","# Org Health Diagnostic\n\nEight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.\n\n## Keywords\norg health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard\n\n## Quick Start\n\n```bash\npython scripts\u002Fhealth_scorer.py        # Guided CLI — enter metrics, get scored dashboard\npython scripts\u002Fhealth_scorer.py --json # Output raw JSON for integration\n```\n\nOr describe your metrics:\n```\n\u002Fhealth [paste your key metrics or answer prompts]\n\u002Fhealth:dimension [financial|revenue|product|engineering|people|ops|security|market]\n```\n\n## The 8 Dimensions\n\n### 1. 💰 Financial Health (CFO)\n**What it measures:** Can we fund operations and invest in growth?\n\nKey metrics:\n- **Runway** — months at current burn (Green: >12, Yellow: 6-12, Red: \u003C6)\n- **Burn multiple** — net burn \u002F net new ARR (Green: \u003C1.5x, Yellow: 1.5-2.5x, Red: >2.5x)\n- **Gross margin** — SaaS target: >65% (Green: >70%, Yellow: 55-70%, Red: \u003C55%)\n- **MoM growth rate** — contextual by stage (see benchmarks)\n- **Revenue concentration** — top customer % of ARR (Green: \u003C15%, Yellow: 15-25%, Red: >25%)\n\n### 2. 📈 Revenue Health (CRO)\n**What it measures:** Are customers staying, growing, and recommending us?\n\nKey metrics:\n- **NRR (Net Revenue Retention)** — Green: >110%, Yellow: 100-110%, Red: \u003C100%\n- **Logo churn rate (annualized)** — Green: \u003C5%, Yellow: 5-10%, Red: >10%\n- **Pipeline coverage (next quarter)** — Green: >3x, Yellow: 2-3x, Red: \u003C2x\n- **CAC payback period** — Green: \u003C12 months, Yellow: 12-18, Red: >18 months\n- **Average ACV trend** — directional: growing, flat, declining\n\n### 3. 🚀 Product Health (CPO)\n**What it measures:** Do customers love and use the product?\n\nKey metrics:\n- **NPS** — Green: >40, Yellow: 20-40, Red: \u003C20\n- **DAU\u002FMAU ratio** — engagement proxy (Green: >40%, Yellow: 20-40%, Red: \u003C20%)\n- **Core feature adoption** — % of users using primary value feature (Green: >60%)\n- **Time-to-value** — days from signup to first core action (lower is better)\n- **Customer satisfaction (CSAT)** — Green: >4.2\u002F5, Yellow: 3.5-4.2, Red: \u003C3.5\n\n### 4. ⚙️ Engineering Health (CTO)\n**What it measures:** Can we ship reliably and sustain velocity?\n\nKey metrics:\n- **Deployment frequency** — Green: daily, Yellow: weekly, Red: monthly or less\n- **Change failure rate** — % of deployments causing incidents (Green: \u003C5%, Red: >15%)\n- **Mean time to recovery (MTTR)** — Green: \u003C1 hour, Yellow: 1-4 hours, Red: >4 hours\n- **Tech debt ratio** — % of sprint capacity on debt (Green: \u003C20%, Yellow: 20-35%, Red: >35%)\n- **Incident frequency** — P0\u002FP1 per month (Green: \u003C2, Yellow: 2-5, Red: >5)\n\n### 5. 👥 People Health (CHRO)\n**What it measures:** Is the team stable, engaged, and growing?\n\nKey metrics:\n- **Regrettable attrition (annualized)** — Green: \u003C10%, Yellow: 10-20%, Red: >20%\n- **Engagement score** — (eNPS or similar; Green: >30, Yellow: 0-30, Red: \u003C0)\n- **Time-to-fill (avg days)** — Green: \u003C45, Yellow: 45-90, Red: >90\n- **Manager-to-IC ratio** — Green: 1:5–1:8, Yellow: 1:3–1:5 or 1:8–1:12, Red: outside\n- **Internal promotion rate** — at least 25-30% of senior roles filled internally\n\n### 6. 🔄 Operational Health (COO)\n**What it measures:** Are we executing our strategy with discipline?\n\nKey metrics:\n- **OKR completion rate** — % of key results hitting target (Green: >70%, Yellow: 50-70%, Red: \u003C50%)\n- **Decision cycle time** — days from decision needed to decision made (Green: \u003C48h, Yellow: 48h-1w)\n- **Meeting effectiveness** — % of meetings with clear outcome (qualitative)\n- **Process maturity** — level 1-5 scale (see COO advisor)\n- **Cross-functional initiative completion** — % on time, on scope\n\n### 7. 🔒 Security Health (CISO)\n**What it measures:** Are we protecting customers and maintaining compliance?\n\nKey metrics:\n- **Security incidents (last 90 days)** — Green: 0, Yellow: 1-2 minor, Red: 1+ major\n- **Compliance status** — certifications current\u002Fin-progress vs. overdue\n- **Vulnerability remediation SLA** — % of critical CVEs patched within SLA (Green: 100%)\n- **Security training completion** — % of team current (Green: >95%)\n- **Pen test recency** — Green: \u003C12 months, Yellow: 12-24, Red: >24 months\n\n### 8. 📣 Market Health (CMO)\n**What it measures:** Are we winning in the market and growing efficiently?\n\nKey metrics:\n- **CAC trend** — improving, flat, or worsening QoQ\n- **Organic vs paid lead mix** — more organic = healthier (less fragile)\n- **Win rate** — % of qualified opportunities closed-won (Green: >25%, Yellow: 15-25%, Red: \u003C15%)\n- **Competitive win rate** — against primary competitors specifically\n- **Brand NPS** — awareness + preference scores in ICP\n\n---\n\n## Scoring & Traffic Lights\n\nEach dimension is scored 1-10 with traffic light:\n- 🟢 **Green (7-10):** Healthy — maintain and optimize\n- 🟡 **Yellow (4-6):** Watch — trend matters; improving or declining?\n- 🔴 **Red (1-3):** Action required — address within 30 days\n\n**Overall Health Score:**\nWeighted average by company stage (see `references\u002Fhealth-benchmarks.md` for weights).\n\n---\n\n## Dimension Interactions (Why One Problem Creates Another)\n\n| If this dimension is red... | Watch these dimensions next |\n|-----------------------------|----------------------------|\n| Financial Health | People (freeze hiring) → Engineering (freeze infra) → Product (cut scope) |\n| Revenue Health | Financial (cash gap) → People (attrition risk) → Market (lose positioning) |\n| People Health | Engineering (velocity drops) → Product (quality drops) → Revenue (churn rises) |\n| Engineering Health | Product (features slip) → Revenue (deals stall on product) |\n| Product Health | Revenue (NRR drops, churn rises) → Market (CAC rises; referrals dry up) |\n| Operational Health | All dimensions degrade over time (execution failure cascades everywhere) |\n\n---\n\n## Dashboard Output Format\n\n```\nORG HEALTH DIAGNOSTIC — [Company] — [Date]\nStage: [Seed\u002FA\u002FB\u002FC]   Overall: [Score]\u002F10   Trend: [↑ Improving \u002F → Stable \u002F ↓ Declining]\n\nDIMENSION SCORES\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n💰 Financial    🟢 8.2  Runway 14mo, burn 1.6x — strong\n📈 Revenue      🟡 5.8  NRR 104%, pipeline thin (1.8x coverage)\n🚀 Product      🟢 7.4  NPS 42, DAU\u002FMAU 38%\n⚙️  Engineering  🟡 5.2  Debt at 30%, MTTR 3.2h\n👥 People       🔴 3.8  Attrition 24%, eng morale low\n🔄 Operations   🟡 6.0  OKR 65% completion\n🔒 Security     🟢 7.8  SOC 2 Type II complete, 0 incidents\n📣 Market       🟡 5.5  CAC rising, win rate dropped to 22%\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTOP PRIORITIES\n🔴 [1] People: attrition at 24% — engineering velocity will drop in 60 days\n   Action: CHRO + CEO to run retention audit; target top 5 at-risk this week\n🟡 [2] Revenue: pipeline coverage at 1.8x — Q+1 miss risk is high\n   Action: CRO to add 3 qualified opps within 30 days or shift forecast down\n🟡 [3] Engineering: tech debt at 30% of sprint — shipping will slow by Q3\n   Action: CTO to propose debt sprint plan; COO to protect capacity\n\nWATCH\n→ People → Engineering cascade risk if attrition continues (see dimension interactions)\n```\n\n---\n\n## Graceful Degradation\n\nYou don't need all metrics to run a diagnostic. The tool handles partial data:\n- Missing metric → excluded from score, flagged as \"[data needed]\"\n- Score still valid for available dimensions\n- Report flags which gaps to fill for next cycle\n\n## References\n- `references\u002Fhealth-benchmarks.md` — benchmarks by stage (Seed, A, B, C)\n- `scripts\u002Fhealth_scorer.py` — CLI scoring tool with traffic light output\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","organizational-health",1772668800000,"1.0.0","c-level","health-benchmarks","health_scorer.py","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS","https:\u002F\u002Fgithub.com\u002FASoudy","2026-05-23 09:43:12",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add ASoudy\u002FAGS --skill org-health-diagnostic",{"tool":43,"command":44},"bunx","bunx skills add ASoudy\u002FAGS --skill org-health-diagnostic",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill org-health-diagnostic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fhealth-benchmarks.md","REFERENCE","参考文档",9094,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Freferences\u002Fhealth-benchmarks.md",{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fhealth_scorer.py","SCRIPT","脚本",21377,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Fscripts\u002Fhealth_scorer.py",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M756BTEVC407T0QR8S420JWD","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", or \"typographic scale\". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M756B4RYF2CB17C33X6ZJQT5","ux-heuristics","Evaluate and improve interface usability using heuristic analysis. Use when the user mentions \"usability audit\", \"UX review\", \"users are confused\", \"heuristic evaluation\", \"form usability\", \"navigation problems\", \"Nielsen heuristics\", \"cognitive walkthrough\", or \"usability testing\". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fux-heuristics\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M756ANVFT0T6BAPV6Y93EPR6","traction-eos","Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions \"EOS\", \"V\u002FTO\", \"quarterly rocks\", \"Level 10 meetings\", \"accountability chart\", \"IDS process\", \"Entrepreneurial Operating System\", or \"business operating system\". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftraction-eos\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M756A7NZZMNJN9KZ33QGFHV6","top-design","Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions \"premium website\", \"portfolio site\", \"scroll animations\", \"Awwwards quality\", \"brand experience\", \"cinematic web design\", \"parallax storytelling\", or \"agency-quality site\". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Ftop-design\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7569J5G1NXM3RR194D52SGB","system-design","Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions \"system design\", \"scale this\", \"high availability\", \"rate limiter\", \"design a URL shortener\", \"system design interview\", \"capacity planning\", or \"distributed architecture\". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fsystem-design\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M75691MJKE6PBA1EC398EKQT","storybrand-messaging","Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions \"brand message\", \"website copy\", \"elevator pitch\", \"one-liner\", \"messaging isnt resonating\", \"brand script\", \"StoryBrand framework\", or \"customer as hero\". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.","https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fwondelai-product-strategy\u002Fstorybrand-messaging\u002FSKILL.md",[],[]]