[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KARNDGFPVSPCEGEK6KC39S":3,"skill-same:01M6KARNDGFPVSPCEGEK6KC39S":111},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":5,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6KARNDGFPVSPCEGEK6KC39S","c-level-advisor",null,"10 C-level advisory agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor. Multi-role board meetings, strategy routing, structured recommendations. For founders needing executive-level decision support.","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\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"c level advisor","advisor","for","openclaw","cto","founders","multi","cmo","ciso","recommendations","advisory","strategy","decision","cro","mentor","code","support","gemini cli","gemini","cli","2026-11-10 10:12:30",false,"---\nname: \"c-level-advisor\"\ndescription: \"10 C-level advisory agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor. Multi-role board meetings, strategy routing, structured recommendations. For founders needing executive-level decision support.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Md Faiz Alam\n  category: c-level\n  domain: executive-advisory\n  updated: 2026-03-05\n  skills_count: 28\n  scripts_count: 25\n  references_count: 52\n---\n\n# C-Level Advisory Ecosystem\n\nA complete virtual board of directors for founders and executives.\n\n## Quick Start\n\n```\n1. Run \u002Fcs:setup → creates company-context.md (all agents read this)\n   ✓ Verify company-context.md was created and contains your company name,\n     stage, and core metrics before proceeding.\n2. Ask any strategic question → Chief of Staff routes to the right role\n3. For big decisions → \u002Fcs:board triggers a multi-role board meeting\n   ✓ Confirm at least 3 roles have weighed in before accepting a conclusion.\n```\n\n### Commands\n\n#### `\u002Fcs:setup` — Onboarding Questionnaire\n\nWalks through the following prompts and writes `company-context.md` to the project root. Run once per company or when context changes significantly.\n\n```\nQ1. What is your company name and one-line description?\nQ2. What stage are you at? (Idea \u002F Pre-seed \u002F Seed \u002F Series A \u002F Series B+)\nQ3. What is your current ARR (or MRR) and runway in months?\nQ4. What is your team size and structure?\nQ5. What industry and customer segment do you serve?\nQ6. What are your top 3 priorities for the next 90 days?\nQ7. What is your biggest current risk or blocker?\n```\n\nAfter collecting answers, the agent writes structured output:\n\n```markdown\n# Company Context\n- Name: \u003Canswer>\n- Stage: \u003Canswer>\n- Industry: \u003Canswer>\n- Team size: \u003Canswer>\n- Key metrics: \u003CARR\u002FMRR, growth rate, runway>\n- Top priorities: \u003Canswer>\n- Key risks: \u003Canswer>\n```\n\n#### `\u002Fcs:board` — Full Board Meeting\n\nConvenes all relevant executive roles in three phases:\n\n```\nPhase 1 — Framing:   Chief of Staff states the decision and success criteria.\nPhase 2 — Isolation: Each role produces independent analysis (no cross-talk).\nPhase 3 — Debate:    Roles surface conflicts, stress-test assumptions, align on\n                     a recommendation. Dissenting views are preserved in the log.\n```\n\nUse for high-stakes or cross-functional decisions. Confirm at least 3 roles have weighed in before accepting a conclusion.\n\n### Chief of Staff Routing Matrix\n\nWhen a question arrives without a role prefix, the Chief of Staff maps it to the appropriate executive using these primary signals:\n\n| Topic Signal | Primary Role | Supporting Roles |\n|---|---|---|\n| Fundraising, valuation, burn | CFO | CEO, CRO |\n| Architecture, build vs. buy, tech debt | CTO | CPO, CISO |\n| Hiring, culture, performance | CHRO | CEO, Executive Mentor |\n| GTM, demand gen, positioning | CMO | CRO, CPO |\n| Revenue, pipeline, sales motion | CRO | CMO, CFO |\n| Security, compliance, risk | CISO | CTO, CFO |\n| Product roadmap, prioritisation | CPO | CTO, CMO |\n| Ops, process, scaling | COO | CFO, CHRO |\n| Vision, strategy, investor relations | CEO | Executive Mentor |\n| Career, founder psychology, leadership | Executive Mentor | CEO, CHRO |\n| Multi-domain \u002F unclear | Chief of Staff convenes board | All relevant roles |\n\n### Invoking a Specific Role Directly\n\nTo bypass Chief of Staff routing and address one executive directly, prefix your question with the role name:\n\n```\nCFO: What is our optimal burn rate heading into a Series A?\nCTO: Should we rebuild our auth layer in-house or buy a solution?\nCHRO: How do we design a performance review process for a 15-person team?\n```\n\nThe Chief of Staff still logs the exchange; only routing is skipped.\n\n### Example: Strategic Question\n\n**Input:** \"Should we raise a Series A now or extend runway and grow ARR first?\"\n\n**Output format:**\n- **Bottom Line:** Extend runway 6 months; raise at $2M ARR for better terms.\n- **What:** Current $800K ARR is below the threshold most Series A investors benchmark.\n- **Why:** Raising now increases dilution risk; 6-month extension is achievable with current burn.\n- **How to Act:** Cut 2 low-ROI channels, hit $2M ARR, then run a 6-week fundraise sprint.\n- **Your Decision:** Proceed with extension \u002F Raise now anyway (choose one).\n\n### Example: company-context.md (after \u002Fcs:setup)\n\n```markdown\n# Company Context\n- Name: Acme Inc.\n- Stage: Seed ($800K ARR)\n- Industry: B2B SaaS\n- Team size: 12\n- Key metrics: 15% MoM growth, 18-month runway\n- Top priorities: Series A readiness, enterprise GTM\n```\n\n## What's Included\n\n### 10 C-Suite Roles\nCEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n\n### 6 Orchestration Skills\nFounder Onboard, Chief of Staff (router), Board Meeting, Decision Logger, Agent Protocol, Context Engine\n\n### 6 Cross-Cutting Capabilities\nBoard Deck Builder, Scenario War Room, Competitive Intel, Org Health Diagnostic, M&A Playbook, International Expansion\n\n### 6 Culture & Collaboration\nCulture Architect, Company OS, Founder Coach, Strategic Alignment, Change Management, Internal Narrative\n\n## Key Features\n\n- **Internal Quality Loop:** Self-verify → peer-verify → critic pre-screen → present\n- **Two-Layer Memory:** Raw transcripts + approved decisions only (prevents hallucinated consensus)\n- **Board Meeting Isolation:** Phase 2 independent analysis before cross-examination\n- **Proactive Triggers:** Context-driven early warnings without being asked\n- **Structured Output:** Bottom Line → What → Why → How to Act → Your Decision\n- **25 Python Tools:** All stdlib-only, CLI-first, JSON output, zero dependencies\n\n## See Also\n\n- `CLAUDE.md` — full architecture diagram and integration guide\n- `agent-protocol\u002FSKILL.md` — communication standard and quality loop details\n- `chief-of-staff\u002FSKILL.md` — routing matrix for all 28 skills\n","# C-Level Advisory Ecosystem\n\nA complete virtual board of directors for founders and executives.\n\n## Quick Start\n\n```\n1. Run \u002Fcs:setup → creates company-context.md (all agents read this)\n   ✓ Verify company-context.md was created and contains your company name,\n     stage, and core metrics before proceeding.\n2. Ask any strategic question → Chief of Staff routes to the right role\n3. For big decisions → \u002Fcs:board triggers a multi-role board meeting\n   ✓ Confirm at least 3 roles have weighed in before accepting a conclusion.\n```\n\n### Commands\n\n#### `\u002Fcs:setup` — Onboarding Questionnaire\n\nWalks through the following prompts and writes `company-context.md` to the project root. Run once per company or when context changes significantly.\n\n```\nQ1. What is your company name and one-line description?\nQ2. What stage are you at? (Idea \u002F Pre-seed \u002F Seed \u002F Series A \u002F Series B+)\nQ3. What is your current ARR (or MRR) and runway in months?\nQ4. What is your team size and structure?\nQ5. What industry and customer segment do you serve?\nQ6. What are your top 3 priorities for the next 90 days?\nQ7. What is your biggest current risk or blocker?\n```\n\nAfter collecting answers, the agent writes structured output:\n\n```markdown\n# Company Context\n- Name: \u003Canswer>\n- Stage: \u003Canswer>\n- Industry: \u003Canswer>\n- Team size: \u003Canswer>\n- Key metrics: \u003CARR\u002FMRR, growth rate, runway>\n- Top priorities: \u003Canswer>\n- Key risks: \u003Canswer>\n```\n\n#### `\u002Fcs:board` — Full Board Meeting\n\nConvenes all relevant executive roles in three phases:\n\n```\nPhase 1 — Framing:   Chief of Staff states the decision and success criteria.\nPhase 2 — Isolation: Each role produces independent analysis (no cross-talk).\nPhase 3 — Debate:    Roles surface conflicts, stress-test assumptions, align on\n                     a recommendation. Dissenting views are preserved in the log.\n```\n\nUse for high-stakes or cross-functional decisions. Confirm at least 3 roles have weighed in before accepting a conclusion.\n\n### Chief of Staff Routing Matrix\n\nWhen a question arrives without a role prefix, the Chief of Staff maps it to the appropriate executive using these primary signals:\n\n| Topic Signal | Primary Role | Supporting Roles |\n|---|---|---|\n| Fundraising, valuation, burn | CFO | CEO, CRO |\n| Architecture, build vs. buy, tech debt | CTO | CPO, CISO |\n| Hiring, culture, performance | CHRO | CEO, Executive Mentor |\n| GTM, demand gen, positioning | CMO | CRO, CPO |\n| Revenue, pipeline, sales motion | CRO | CMO, CFO |\n| Security, compliance, risk | CISO | CTO, CFO |\n| Product roadmap, prioritisation | CPO | CTO, CMO |\n| Ops, process, scaling | COO | CFO, CHRO |\n| Vision, strategy, investor relations | CEO | Executive Mentor |\n| Career, founder psychology, leadership | Executive Mentor | CEO, CHRO |\n| Multi-domain \u002F unclear | Chief of Staff convenes board | All relevant roles |\n\n### Invoking a Specific Role Directly\n\nTo bypass Chief of Staff routing and address one executive directly, prefix your question with the role name:\n\n```\nCFO: What is our optimal burn rate heading into a Series A?\nCTO: Should we rebuild our auth layer in-house or buy a solution?\nCHRO: How do we design a performance review process for a 15-person team?\n```\n\nThe Chief of Staff still logs the exchange; only routing is skipped.\n\n### Example: Strategic Question\n\n**Input:** \"Should we raise a Series A now or extend runway and grow ARR first?\"\n\n**Output format:**\n- **Bottom Line:** Extend runway 6 months; raise at $2M ARR for better terms.\n- **What:** Current $800K ARR is below the threshold most Series A investors benchmark.\n- **Why:** Raising now increases dilution risk; 6-month extension is achievable with current burn.\n- **How to Act:** Cut 2 low-ROI channels, hit $2M ARR, then run a 6-week fundraise sprint.\n- **Your Decision:** Proceed with extension \u002F Raise now anyway (choose one).\n\n### Example: company-context.md (after \u002Fcs:setup)\n\n```markdown\n# Company Context\n- Name: Acme Inc.\n- Stage: Seed ($800K ARR)\n- Industry: B2B SaaS\n- Team size: 12\n- Key metrics: 15% MoM growth, 18-month runway\n- Top priorities: Series A readiness, enterprise GTM\n```\n\n## What's Included\n\n### 10 C-Suite Roles\nCEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor\n\n### 6 Orchestration Skills\nFounder Onboard, Chief of Staff (router), Board Meeting, Decision Logger, Agent Protocol, Context Engine\n\n### 6 Cross-Cutting Capabilities\nBoard Deck Builder, Scenario War Room, Competitive Intel, Org Health Diagnostic, M&A Playbook, International Expansion\n\n### 6 Culture & Collaboration\nCulture Architect, Company OS, Founder Coach, Strategic Alignment, Change Management, Internal Narrative\n\n## Key Features\n\n- **Internal Quality Loop:** Self-verify → peer-verify → critic pre-screen → present\n- **Two-Layer Memory:** Raw transcripts + approved decisions only (prevents hallucinated consensus)\n- **Board Meeting Isolation:** Phase 2 independent analysis before cross-examination\n- **Proactive Triggers:** Context-driven early warnings without being asked\n- **Structured Output:** Bottom Line → What → Why → How to Act → Your Decision\n- **25 Python Tools:** All stdlib-only, CLI-first, JSON output, zero dependencies\n\n## See Also\n\n- `CLAUDE.md` — full architecture diagram and integration guide\n- `agent-protocol\u002FSKILL.md` — communication standard and quality loop details\n- `chief-of-staff\u002FSKILL.md` — routing matrix for all 28 skills\n",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":54,"skills_count":55,"scripts_count":56,"references_count":57},"Md Faiz Alam","executive-advisory",1772668800000,"2.0.0","c-level",28,25,52,"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill c-level-advisor",{"tool":71,"command":72},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill c-level-advisor",{"tool":74,"command":75},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill c-level-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002FSKILL.md",true,[79,85,89,93,99,103,107],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",844,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002F.claude-plugin\u002Fplugin.json",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},".codex\u002Finstructions.md",1338,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002F.codex\u002Finstructions.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"c_level_leadership_skills_overview.md",9399,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fc_level_leadership_skills_overview.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"ceo-advisor.zip","ASSET","资产文件",30261,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fceo-advisor.zip",{"path":100,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":101,"sourceHtmlUrl":102},"CLAUDE.md",5837,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002FCLAUDE.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"cto-advisor.zip",25742,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcto-advisor.zip",{"path":108,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":109,"sourceHtmlUrl":110},"README.md",10567,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002FREADME.md",[112,141,166,190,222,242],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":44},"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",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,26],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":44},"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",[],[148,149,150,151,152,153,154,155,129,130,156,157,158,159,160,161,162,163,164,165],"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":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":44},"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",[],[173,174,175,176,177,178,179,180,35,130,181,182,183,184,185,186,187,188,189,26],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":204,"publishedAt":44},"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",[196,201],{"categoryNo":197,"categoryName":198,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[205,206,189,207,208,209,210,211,212,130,213,214,215,216,217,218,219,220,26,221],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":44},"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",[228],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},[230,206,189,231,232,233,234,235,122,236,212,237,174,238,239,240,157,217,26,241],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":255,"publishedAt":44},"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",[248,251,254],{"categoryNo":249,"categoryName":250,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":252,"categoryName":253,"taxonomyType":199,"taxonomyTypeDesc":200},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},[256,257,206,189,231,258,259,126,212,260,261,262,263,264,158,265,266,267,268,26],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]