[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KAS957ZW27BAKWB8HAPAEX":3,"skill-same:01M6KAS957ZW27BAKWB8HAPAEX":98},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6KAS957ZW27BAKWB8HAPAEX","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.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ceo advisor","ceo","advisor","culture","for","updates","investors","strategic","strategic planning","scenario","leadership","decision-making","fundraising","presentations","use","strategy","decisions","decision","planning","development","2026-11-10 10:12:30",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: Md Faiz Alam\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":15,"metadata":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50,"python-tools":51},"Md Faiz Alam","ceo-leadership",1772668800000,"2.0.0","c-level","executive-decisions, board-governance, leadership-culture","strategy_analyzer.py, financial_scenario_analyzer.py","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","c-level-advisor\u002Fceo-advisor",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill ceo-advisor",{"tool":66,"command":67},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill ceo-advisor",{"tool":69,"command":70},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill ceo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002FSKILL.md",true,[74,80,84,88,94],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fboard_governance_investor_relations.md","REFERENCE","参考文档",11661,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002Freferences\u002Fboard_governance_investor_relations.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fexecutive_decision_framework.md",11112,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002Freferences\u002Fexecutive_decision_framework.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fleadership_organizational_culture.md",14703,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002Freferences\u002Fleadership_organizational_culture.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Ffinancial_scenario_analyzer.py","SCRIPT","脚本",17693,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002Fscripts\u002Ffinancial_scenario_analyzer.py",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fstrategy_analyzer.py",23352,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor\u002Fscripts\u002Fstrategy_analyzer.py",[99,129,154,178,210,228],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":110,"publishedAt":39},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[111,112,113,114,115,116,117,118,33,119,120,121,122,123,124,125,126,127,128,23],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":39},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[136,137,138,139,140,141,142,143,118,33,144,145,146,147,148,149,150,151,152,153],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[161,162,163,164,165,166,167,168,34,33,169,170,171,172,173,174,175,176,177,23],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":192,"publishedAt":39},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[184,189],{"categoryNo":185,"categoryName":186,"taxonomyType":187,"taxonomyTypeDesc":188},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":190,"categoryName":191,"taxonomyType":108,"taxonomyTypeDesc":109},"01JBSEEDCAT000000000000032","设计师",[193,194,177,195,196,197,198,199,200,33,201,202,203,204,205,206,207,208,23,209],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":39},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[216],{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},[218,194,177,219,220,221,222,223,111,224,200,225,162,226,22,29,145,205,23,227],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","person",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":241,"publishedAt":39},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[234,237,240],{"categoryNo":235,"categoryName":236,"taxonomyType":187,"taxonomyTypeDesc":188},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":238,"categoryName":239,"taxonomyType":187,"taxonomyTypeDesc":188},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":106,"categoryName":107,"taxonomyType":108,"taxonomyTypeDesc":109},[242,243,194,177,219,244,245,115,200,246,247,248,249,250,146,251,252,253,254,23],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]