[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754MV2F5C099MXZARGVWGQP":3,"skill-same:01M754MV2F5C099MXZARGVWGQP":75},{"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},"01M754MV2F5C099MXZARGVWGQP","ceo-advisor",null,"Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.","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\u002Fceo-advisor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"ceo-advisor\"\ndescription: \"Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ceo-leadership\n  updated: 2026-03-05\n  python-tools: strategy_analyzer.py, financial_scenario_analyzer.py\n  frameworks: executive-decisions, board-governance, leadership-culture\n---\n\n# CEO Advisor\n\nStrategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.\n\n## Keywords\nCEO, chief executive officer, strategy, strategic planning, fundraising, board management, investor relations, culture, organizational leadership, vision, mission, stakeholder management, capital allocation, crisis management, succession planning\n\n## Quick Start\n\n```bash\npython scripts\u002Fstrategy_analyzer.py          # Analyze strategic options with weighted scoring\npython scripts\u002Ffinancial_scenario_analyzer.py # Model financial scenarios (base\u002Fbull\u002Fbear)\n```\n\n## Core Responsibilities\n\n### 1. Vision & Strategy\nSet the direction. Not a 50-page document — a clear, compelling answer to \"Where are we going and why?\"\n\n**Strategic planning cycle:**\n- Annual: 3-year vision refresh + 1-year strategic plan\n- Quarterly: OKR setting with C-suite (COO drives execution)\n- Monthly: strategy health check — are we still on track?\n\n**Stage-adaptive time horizons:**\n- Seed\u002FPre-PMF: 3-month \u002F 6-month \u002F 12-month\n- Series A: 6-month \u002F 1-year \u002F 2-year\n- Series B+: 1-year \u002F 3-year \u002F 5-year\n\nSee `references\u002Fexecutive_decision_framework.md` for the full Go\u002FNo-Go framework, crisis playbook, and capital allocation model.\n\n### 2. Capital & Resource Management\nYou're the chief allocator. Every dollar, every person, every hour of engineering time is a bet.\n\n**Capital allocation priorities:**\n1. Keep the lights on (operations, must-haves)\n2. Protect the core (retention, quality, security)\n3. Grow the core (expansion of what works)\n4. Fund new bets (innovation, new products\u002Fmarkets)\n\n**Fundraising:** Know your numbers cold. Timing matters more than valuation. See `references\u002Fboard_governance_investor_relations.md`.\n\n### 3. Stakeholder Leadership\nYou serve multiple masters. Priority order:\n1. Customers (they pay the bills)\n2. Team (they build the product)\n3. Board\u002FInvestors (they fund the mission)\n4. Partners (they extend your reach)\n\n### 4. Organizational Culture\nCulture is what people do when you're not in the room. It's your job to define it, model it, and enforce it.\n\nSee `references\u002Fleadership_organizational_culture.md` for culture development frameworks and the CEO learning agenda. Also see `culture-architect\u002F` for the operational culture toolkit.\n\n### 5. Board & Investor Management\nYour board can be your greatest asset or your biggest liability. The difference is how you manage them.\n\nSee `references\u002Fboard_governance_investor_relations.md` for board meeting prep, investor communication cadence, and managing difficult directors. Also see `board-deck-builder\u002F` for assembling the actual board deck.\n\n## Key Questions a CEO Asks\n\n- \"Can every person in this company explain our strategy in one sentence?\"\n- \"What's the one thing that, if it goes wrong, kills us?\"\n- \"Am I spending my time on the highest-leverage activity right now?\"\n- \"What decision am I avoiding? Why?\"\n- \"If we could only do one thing this quarter, what would it be?\"\n- \"Do our investors and our team hear the same story from me?\"\n- \"Who would replace me if I got hit by a bus tomorrow?\"\n\n## CEO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Strategy** | Annual goals hit rate | > 70% | Quarterly |\n| **Revenue** | ARR growth rate | Stage-dependent | Monthly |\n| **Capital** | Months of runway | > 12 months | Monthly |\n| **Capital** | Burn multiple | \u003C 2x | Monthly |\n| **Product** | NPS \u002F PMF score | > 40 NPS | Quarterly |\n| **People** | Regrettable attrition | \u003C 10% | Monthly |\n| **People** | Employee engagement | > 7\u002F10 | Quarterly |\n| **Board** | Board NPS (your relationship) | Positive trend | Quarterly |\n| **Personal** | % time on strategic work | > 40% | Weekly |\n\n## Red Flags\n\n- You're the bottleneck for more than 3 decisions per week\n- The board surprises you with questions you can't answer\n- Your calendar is 80%+ meetings with no strategic blocks\n- Key people are leaving and you didn't see it coming\n- You're fundraising reactively (runway \u003C 6 months, no plan)\n- Your team can't articulate the strategy without you in the room\n- You're avoiding a hard conversation (co-founder, investor, underperformer)\n\n## Integration with C-Suite Roles\n\n| When... | CEO works with... | To... |\n|---------|-------------------|-------|\n| Setting direction | COO | Translate vision into OKRs and execution plan |\n| Fundraising | CFO | Model scenarios, prep financials, negotiate terms |\n| Board meetings | All C-suite | Each role contributes their section |\n| Culture issues | CHRO | Diagnose and address people\u002Fculture problems |\n| Product vision | CPO | Align product strategy with company direction |\n| Market positioning | CMO | Ensure brand and messaging reflect strategy |\n| Revenue targets | CRO | Set realistic targets backed by pipeline data |\n| Security\u002Fcompliance | CISO | Understand risk posture for board reporting |\n| Technical strategy | CTO | Align tech investments with business priorities |\n| Hard decisions | Executive Mentor | Stress-test before committing |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Runway \u003C 12 months with no fundraising plan → flag immediately\n- Strategy hasn't been reviewed in 2+ quarters → prompt refresh\n- Board meeting approaching with no prep → initiate board-prep flow\n- Founder spending \u003C 20% time on strategic work → raise it\n- Key exec departure risk visible → escalate to CHRO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Help me think about strategy\" | Strategic options matrix with risk-adjusted scoring |\n| \"Prep me for the board\" | Board narrative + anticipated questions + data gaps |\n| \"Should we raise?\" | Fundraising readiness assessment with timeline |\n| \"We need to decide on X\" | Decision framework with options, trade-offs, recommendation |\n| \"How are we doing?\" | CEO scorecard with traffic-light metrics |\n\n## Reasoning Technique: Tree of Thought\n\nExplore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome.\n\n**Stage-adaptive horizons:**\n- Seed: project 3m\u002F6m\u002F12m\n- Series A: project 6m\u002F1y\u002F2y\n- Series B+: project 1y\u002F3y\u002F5y\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## Resources\n- `references\u002Fexecutive_decision_framework.md` — Go\u002FNo-Go framework, crisis playbook, capital allocation\n- `references\u002Fboard_governance_investor_relations.md` — Board management, investor communication, fundraising\n- `references\u002Fleadership_organizational_culture.md` — Culture development, CEO routines, succession planning\n","# CEO Advisor\n\nStrategic leadership frameworks for vision, fundraising, board management, culture, and stakeholder alignment.\n\n## Keywords\nCEO, chief executive officer, strategy, strategic planning, fundraising, board management, investor relations, culture, organizational leadership, vision, mission, stakeholder management, capital allocation, crisis management, succession planning\n\n## Quick Start\n\n```bash\npython scripts\u002Fstrategy_analyzer.py          # Analyze strategic options with weighted scoring\npython scripts\u002Ffinancial_scenario_analyzer.py # Model financial scenarios (base\u002Fbull\u002Fbear)\n```\n\n## Core Responsibilities\n\n### 1. Vision & Strategy\nSet the direction. Not a 50-page document — a clear, compelling answer to \"Where are we going and why?\"\n\n**Strategic planning cycle:**\n- Annual: 3-year vision refresh + 1-year strategic plan\n- Quarterly: OKR setting with C-suite (COO drives execution)\n- Monthly: strategy health check — are we still on track?\n\n**Stage-adaptive time horizons:**\n- Seed\u002FPre-PMF: 3-month \u002F 6-month \u002F 12-month\n- Series A: 6-month \u002F 1-year \u002F 2-year\n- Series B+: 1-year \u002F 3-year \u002F 5-year\n\nSee `references\u002Fexecutive_decision_framework.md` for the full Go\u002FNo-Go framework, crisis playbook, and capital allocation model.\n\n### 2. Capital & Resource Management\nYou're the chief allocator. Every dollar, every person, every hour of engineering time is a bet.\n\n**Capital allocation priorities:**\n1. Keep the lights on (operations, must-haves)\n2. Protect the core (retention, quality, security)\n3. Grow the core (expansion of what works)\n4. Fund new bets (innovation, new products\u002Fmarkets)\n\n**Fundraising:** Know your numbers cold. Timing matters more than valuation. See `references\u002Fboard_governance_investor_relations.md`.\n\n### 3. Stakeholder Leadership\nYou serve multiple masters. Priority order:\n1. Customers (they pay the bills)\n2. Team (they build the product)\n3. Board\u002FInvestors (they fund the mission)\n4. Partners (they extend your reach)\n\n### 4. Organizational Culture\nCulture is what people do when you're not in the room. It's your job to define it, model it, and enforce it.\n\nSee `references\u002Fleadership_organizational_culture.md` for culture development frameworks and the CEO learning agenda. Also see `culture-architect\u002F` for the operational culture toolkit.\n\n### 5. Board & Investor Management\nYour board can be your greatest asset or your biggest liability. The difference is how you manage them.\n\nSee `references\u002Fboard_governance_investor_relations.md` for board meeting prep, investor communication cadence, and managing difficult directors. Also see `board-deck-builder\u002F` for assembling the actual board deck.\n\n## Key Questions a CEO Asks\n\n- \"Can every person in this company explain our strategy in one sentence?\"\n- \"What's the one thing that, if it goes wrong, kills us?\"\n- \"Am I spending my time on the highest-leverage activity right now?\"\n- \"What decision am I avoiding? Why?\"\n- \"If we could only do one thing this quarter, what would it be?\"\n- \"Do our investors and our team hear the same story from me?\"\n- \"Who would replace me if I got hit by a bus tomorrow?\"\n\n## CEO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Strategy** | Annual goals hit rate | > 70% | Quarterly |\n| **Revenue** | ARR growth rate | Stage-dependent | Monthly |\n| **Capital** | Months of runway | > 12 months | Monthly |\n| **Capital** | Burn multiple | \u003C 2x | Monthly |\n| **Product** | NPS \u002F PMF score | > 40 NPS | Quarterly |\n| **People** | Regrettable attrition | \u003C 10% | Monthly |\n| **People** | Employee engagement | > 7\u002F10 | Quarterly |\n| **Board** | Board NPS (your relationship) | Positive trend | Quarterly |\n| **Personal** | % time on strategic work | > 40% | Weekly |\n\n## Red Flags\n\n- You're the bottleneck for more than 3 decisions per week\n- The board surprises you with questions you can't answer\n- Your calendar is 80%+ meetings with no strategic blocks\n- Key people are leaving and you didn't see it coming\n- You're fundraising reactively (runway \u003C 6 months, no plan)\n- Your team can't articulate the strategy without you in the room\n- You're avoiding a hard conversation (co-founder, investor, underperformer)\n\n## Integration with C-Suite Roles\n\n| When... | CEO works with... | To... |\n|---------|-------------------|-------|\n| Setting direction | COO | Translate vision into OKRs and execution plan |\n| Fundraising | CFO | Model scenarios, prep financials, negotiate terms |\n| Board meetings | All C-suite | Each role contributes their section |\n| Culture issues | CHRO | Diagnose and address people\u002Fculture problems |\n| Product vision | CPO | Align product strategy with company direction |\n| Market positioning | CMO | Ensure brand and messaging reflect strategy |\n| Revenue targets | CRO | Set realistic targets backed by pipeline data |\n| Security\u002Fcompliance | CISO | Understand risk posture for board reporting |\n| Technical strategy | CTO | Align tech investments with business priorities |\n| Hard decisions | Executive Mentor | Stress-test before committing |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Runway \u003C 12 months with no fundraising plan → flag immediately\n- Strategy hasn't been reviewed in 2+ quarters → prompt refresh\n- Board meeting approaching with no prep → initiate board-prep flow\n- Founder spending \u003C 20% time on strategic work → raise it\n- Key exec departure risk visible → escalate to CHRO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Help me think about strategy\" | Strategic options matrix with risk-adjusted scoring |\n| \"Prep me for the board\" | Board narrative + anticipated questions + data gaps |\n| \"Should we raise?\" | Fundraising readiness assessment with timeline |\n| \"We need to decide on X\" | Decision framework with options, trade-offs, recommendation |\n| \"How are we doing?\" | CEO scorecard with traffic-light metrics |\n\n## Reasoning Technique: Tree of Thought\n\nExplore multiple futures. For every strategic decision, generate at least 3 paths. Evaluate each path for upside, downside, reversibility, and second-order effects. Pick the path with the best risk-adjusted outcome.\n\n**Stage-adaptive horizons:**\n- Seed: project 3m\u002F6m\u002F12m\n- Series A: project 6m\u002F1y\u002F2y\n- Series B+: project 1y\u002F3y\u002F5y\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## Resources\n- `references\u002Fexecutive_decision_framework.md` — Go\u002FNo-Go framework, crisis playbook, capital allocation\n- `references\u002Fboard_governance_investor_relations.md` — Board management, investor communication, fundraising\n- `references\u002Fleadership_organizational_culture.md` — Culture development, CEO routines, succession planning\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","ceo-leadership",1772668800000,"2.0.0","c-level","executive-decisions, board-governance, leadership-culture","strategy_analyzer.py, financial_scenario_analyzer.py","main","cd1d94757d590093507ef8ac26299eab8bc20478","claude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor","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 ceo-advisor",{"tool":43,"command":44},"bunx","bunx skills add ASoudy\u002FAGS --skill ceo-advisor",{"tool":46,"command":47},"pnpm","pnpm dlx skills add ASoudy\u002FAGS --skill ceo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002FSKILL.md",true,[51,57,61,65,71],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fboard_governance_investor_relations.md","REFERENCE","参考文档",11661,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002Freferences\u002Fboard_governance_investor_relations.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fexecutive_decision_framework.md",11112,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002Freferences\u002Fexecutive_decision_framework.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fleadership_organizational_culture.md",14703,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002Freferences\u002Fleadership_organizational_culture.md",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Ffinancial_scenario_analyzer.py","SCRIPT","脚本",17693,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002Fscripts\u002Ffinancial_scenario_analyzer.py",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fstrategy_analyzer.py",23352,"https:\u002F\u002Fgithub.com\u002FASoudy\u002FAGS\u002Fblob\u002Fmain\u002Fclaude_skills_libraries\u002Fnginity-skills-library\u002Fc-level-advisor\u002Fskills\u002Fceo-advisor\u002Fscripts\u002Fstrategy_analyzer.py",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"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",[],[]]