[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KATXKC6PSP5C8BGWTPHDN8":3,"skill-same:01M6KATXKC6PSP5C8BGWTPHDN8":103},{"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":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6KATXKC6PSP5C8BGWTPHDN8","coo-advisor",null,"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.","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\u002Fcoo-advisor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"coo advisor","coo","advisor","improvement","design","for","process design","cadence","scaling","leadership","efficiency","frameworks","tracker","up","use","execution","playbook","analyzing","planning","teams","2026-11-10 10:12:30",false,"---\nname: \"coo-advisor\"\ndescription: \"Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Md Faiz Alam\n  category: c-level\n  domain: coo-leadership\n  updated: 2026-03-05\n  python-tools: ops_efficiency_analyzer.py, okr_tracker.py\n  frameworks: scaling-playbook, ops-cadence, process-frameworks\n---\n\n# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\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","# COO Advisor\n\nOperational frameworks and tools for turning strategy into execution, scaling processes, and building the organizational engine.\n\n## Keywords\nCOO, chief operating officer, operations, operational excellence, process improvement, OKRs, objectives and key results, scaling, operational efficiency, execution, bottleneck analysis, process design, operational cadence, meeting cadence, org scaling, lean operations, continuous improvement\n\n## Quick Start\n\n```bash\npython scripts\u002Fops_efficiency_analyzer.py   # Map processes, find bottlenecks, score maturity\npython scripts\u002Fokr_tracker.py               # Cascade OKRs, track progress, flag at-risk items\n```\n\n## Core Responsibilities\n\n### 1. Strategy Execution\nThe CEO sets direction. The COO makes it happen. Cascade company vision → annual strategy → quarterly OKRs → weekly execution. See `references\u002Fops_cadence.md` for full OKR cascade framework.\n\n### 2. Process Design\nMap current state → find the bottleneck → design improvement → implement incrementally → standardize. See `references\u002Fprocess_frameworks.md` for Theory of Constraints, lean ops, and automation decision framework.\n\n**Process Maturity Scale:**\n| Level | Name | Signal |\n|-------|------|--------|\n| 1 | Ad hoc | Different every time |\n| 2 | Defined | Written but not followed |\n| 3 | Measured | KPIs tracked |\n| 4 | Managed | Data-driven improvement |\n| 5 | Optimized | Continuous improvement loops |\n\n### 3. Operational Cadence\nDaily standups (15 min, blockers only) → Weekly leadership sync → Monthly business review → Quarterly OKR planning. See `references\u002Fops_cadence.md` for full templates.\n\n### 4. Scaling Operations\nWhat breaks at each stage: Seed (tribal knowledge) → Series A (documentation) → Series B (coordination) → Series C (decision speed) → Growth (culture). See `references\u002Fscaling_playbook.md` for detailed playbook per stage.\n\n### 5. Cross-Functional Coordination\nRACI for key decisions. Escalation framework: Team lead → Dept head → COO → CEO based on impact scope.\n\n## Key Questions a COO Asks\n\n- \"What's the bottleneck? Not what's annoying — what limits throughput.\"\n- \"How many manual steps? Which break at 3x volume?\"\n- \"Who's the single point of failure?\"\n- \"Can every team articulate how their work connects to company goals?\"\n- \"The same blocker appeared 3 weeks in a row. Why isn't it fixed?\"\n\n## Operational Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Execution | OKR progress (% on track) | > 70% |\n| Execution | Quarterly goals hit rate | > 80% |\n| Speed | Decision cycle time | \u003C 48 hours |\n| Quality | Customer-facing incidents | \u003C 2\u002Fmonth |\n| Efficiency | Revenue per employee | Track trend |\n| Efficiency | Burn multiple | \u003C 2x |\n| People | Regrettable attrition | \u003C 10% |\n\n## Red Flags\n\n- OKRs consistently 1.0 (not ambitious) or \u003C 0.3 (disconnected from reality)\n- Teams can't explain how their work maps to company goals\n- Leadership meetings produce no action items two weeks running\n- Same blocker in three consecutive syncs\n- Process exists but nobody follows it\n- Departments optimize local metrics at expense of company metrics\n\n## Integration with Other C-Suite Roles\n\n| When... | COO works with... | To... |\n|---------|-------------------|-------|\n| Strategy shifts | CEO | Translate direction into ops plan |\n| Roadmap changes | CPO + CTO | Assess operational impact |\n| Revenue targets change | CRO | Adjust capacity planning |\n| Budget constraints | CFO | Find efficiency gains |\n| Hiring plans | CHRO | Align headcount with ops needs |\n| Security incidents | CISO | Coordinate response |\n\n## Detailed References\n- `references\u002Fscaling_playbook.md` — what changes at each growth stage\n- `references\u002Fops_cadence.md` — meeting rhythms, OKR cascades, reporting\n- `references\u002Fprocess_frameworks.md` — lean ops, TOC, automation decisions\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Same blocker appearing 3+ weeks → process is broken, not just slow\n- OKR check-in overdue → prompt quarterly review\n- Team growing past a scaling threshold (10→30, 30→80) → flag what will break\n- Decision cycle time increasing → authority structure needs adjustment\n- Meeting cadence not established → propose rhythm before chaos sets in\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Set up OKRs\" | Cascaded OKR framework (company → dept → team) |\n| \"We're scaling fast\" | Scaling readiness report with what breaks next |\n| \"Our process is broken\" | Process map with bottleneck identified + fix plan |\n| \"How efficient are we?\" | Ops efficiency scorecard with maturity ratings |\n| \"Design our meeting cadence\" | Full cadence template (daily → quarterly) |\n\n## Reasoning Technique: Step by Step\n\nMap processes sequentially. Identify each step, handoff, and decision point. Find the bottleneck using throughput analysis. Propose improvements one step at a time.\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",{"name":5,"license":15,"metadata":49,"description":7},{"author":50,"domain":51,"updated":52,"version":53,"category":54,"frameworks":55,"python-tools":56},"Md Faiz Alam","coo-leadership",1772668800000,"1.0.0","c-level","scaling-playbook, ops-cadence, process-frameworks","ops_efficiency_analyzer.py, okr_tracker.py","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","c-level-advisor\u002Fcoo-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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill coo-advisor",{"tool":71,"command":72},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill coo-advisor",{"tool":74,"command":75},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill coo-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002FSKILL.md",true,[79,85,89,93,99],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fops_cadence.md","REFERENCE","参考文档",18849,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002Freferences\u002Fops_cadence.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fprocess_frameworks.md",20077,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002Freferences\u002Fprocess_frameworks.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fscaling_playbook.md",24048,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002Freferences\u002Fscaling_playbook.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fokr_tracker.py","SCRIPT","脚本",43573,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002Fscripts\u002Fokr_tracker.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fops_efficiency_analyzer.py",40590,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fcoo-advisor\u002Fscripts\u002Fops_efficiency_analyzer.py",[104,134,159,184,211,230],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"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",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[116,117,118,119,120,121,122,123,38,124,125,126,127,128,129,130,131,132,133,29],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"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",[],[141,142,143,144,145,146,147,148,123,38,149,150,151,152,153,154,155,156,157,158],"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":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"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",[],[166,167,168,169,170,171,172,173,174,38,175,176,177,178,179,180,181,182,183,29],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":194,"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",[190,191],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":192,"categoryName":193,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000032","设计师",[195,196,183,28,197,198,199,200,201,38,202,203,204,205,206,207,208,209,29,210],"quality manager qms iso13485","quality","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"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",[217],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[219,196,183,220,221,222,223,224,116,225,201,226,167,227,228,33,150,206,29,229],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","person",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":243,"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",[236,239,242],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[244,245,196,183,220,246,247,120,201,248,249,250,251,252,151,253,254,255,256,29],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]