[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZSSPXCEXDR4BTRV2MXMD1":3,"skill-same:01M72ZSSPXCEXDR4BTRV2MXMD1":65},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M72ZSSPXCEXDR4BTRV2MXMD1","org-health-diagnostic",null,"Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.","ciciliaETH\u002Fclaude-skills","ciciliaETH","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F94572860?v=4","01M72Z3SEH31MEG7M94G85GE0V","cicilia_eth","01M72Z3SF42XENX7AMJVA7SCQX",0,"MIT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"org-health-diagnostic\"\ndescription: \"Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, or when user mentions org health, health check, or health dashboard.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: organizational-health\n  updated: 2026-03-05\n  python-tools: health_scorer.py\n  frameworks: health-benchmarks\n---\n\n# Org Health Diagnostic\n\nEight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.\n\n## Keywords\norg health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard\n\n## Quick Start\n\n```bash\npython scripts\u002Fhealth_scorer.py        # Guided CLI — enter metrics, get scored dashboard\npython scripts\u002Fhealth_scorer.py --json # Output raw JSON for integration\n```\n\nOr describe your metrics:\n```\n\u002Fhealth [paste your key metrics or answer prompts]\n\u002Fhealth:dimension [financial|revenue|product|engineering|people|ops|security|market]\n```\n\n## The 8 Dimensions\n\n### 1. 💰 Financial Health (CFO)\n**What it measures:** Can we fund operations and invest in growth?\n\nKey metrics:\n- **Runway** — months at current burn (Green: >12, Yellow: 6-12, Red: \u003C6)\n- **Burn multiple** — net burn \u002F net new ARR (Green: \u003C1.5x, Yellow: 1.5-2.5x, Red: >2.5x)\n- **Gross margin** — SaaS target: >65% (Green: >70%, Yellow: 55-70%, Red: \u003C55%)\n- **MoM growth rate** — contextual by stage (see benchmarks)\n- **Revenue concentration** — top customer % of ARR (Green: \u003C15%, Yellow: 15-25%, Red: >25%)\n\n### 2. 📈 Revenue Health (CRO)\n**What it measures:** Are customers staying, growing, and recommending us?\n\nKey metrics:\n- **NRR (Net Revenue Retention)** — Green: >110%, Yellow: 100-110%, Red: \u003C100%\n- **Logo churn rate (annualized)** — Green: \u003C5%, Yellow: 5-10%, Red: >10%\n- **Pipeline coverage (next quarter)** — Green: >3x, Yellow: 2-3x, Red: \u003C2x\n- **CAC payback period** — Green: \u003C12 months, Yellow: 12-18, Red: >18 months\n- **Average ACV trend** — directional: growing, flat, declining\n\n### 3. 🚀 Product Health (CPO)\n**What it measures:** Do customers love and use the product?\n\nKey metrics:\n- **NPS** — Green: >40, Yellow: 20-40, Red: \u003C20\n- **DAU\u002FMAU ratio** — engagement proxy (Green: >40%, Yellow: 20-40%, Red: \u003C20%)\n- **Core feature adoption** — % of users using primary value feature (Green: >60%)\n- **Time-to-value** — days from signup to first core action (lower is better)\n- **Customer satisfaction (CSAT)** — Green: >4.2\u002F5, Yellow: 3.5-4.2, Red: \u003C3.5\n\n### 4. ⚙️ Engineering Health (CTO)\n**What it measures:** Can we ship reliably and sustain velocity?\n\nKey metrics:\n- **Deployment frequency** — Green: daily, Yellow: weekly, Red: monthly or less\n- **Change failure rate** — % of deployments causing incidents (Green: \u003C5%, Red: >15%)\n- **Mean time to recovery (MTTR)** — Green: \u003C1 hour, Yellow: 1-4 hours, Red: >4 hours\n- **Tech debt ratio** — % of sprint capacity on debt (Green: \u003C20%, Yellow: 20-35%, Red: >35%)\n- **Incident frequency** — P0\u002FP1 per month (Green: \u003C2, Yellow: 2-5, Red: >5)\n\n### 5. 👥 People Health (CHRO)\n**What it measures:** Is the team stable, engaged, and growing?\n\nKey metrics:\n- **Regrettable attrition (annualized)** — Green: \u003C10%, Yellow: 10-20%, Red: >20%\n- **Engagement score** — (eNPS or similar; Green: >30, Yellow: 0-30, Red: \u003C0)\n- **Time-to-fill (avg days)** — Green: \u003C45, Yellow: 45-90, Red: >90\n- **Manager-to-IC ratio** — Green: 1:5–1:8, Yellow: 1:3–1:5 or 1:8–1:12, Red: outside\n- **Internal promotion rate** — at least 25-30% of senior roles filled internally\n\n### 6. 🔄 Operational Health (COO)\n**What it measures:** Are we executing our strategy with discipline?\n\nKey metrics:\n- **OKR completion rate** — % of key results hitting target (Green: >70%, Yellow: 50-70%, Red: \u003C50%)\n- **Decision cycle time** — days from decision needed to decision made (Green: \u003C48h, Yellow: 48h-1w)\n- **Meeting effectiveness** — % of meetings with clear outcome (qualitative)\n- **Process maturity** — level 1-5 scale (see COO advisor)\n- **Cross-functional initiative completion** — % on time, on scope\n\n### 7. 🔒 Security Health (CISO)\n**What it measures:** Are we protecting customers and maintaining compliance?\n\nKey metrics:\n- **Security incidents (last 90 days)** — Green: 0, Yellow: 1-2 minor, Red: 1+ major\n- **Compliance status** — certifications current\u002Fin-progress vs. overdue\n- **Vulnerability remediation SLA** — % of critical CVEs patched within SLA (Green: 100%)\n- **Security training completion** — % of team current (Green: >95%)\n- **Pen test recency** — Green: \u003C12 months, Yellow: 12-24, Red: >24 months\n\n### 8. 📣 Market Health (CMO)\n**What it measures:** Are we winning in the market and growing efficiently?\n\nKey metrics:\n- **CAC trend** — improving, flat, or worsening QoQ\n- **Organic vs paid lead mix** — more organic = healthier (less fragile)\n- **Win rate** — % of qualified opportunities closed-won (Green: >25%, Yellow: 15-25%, Red: \u003C15%)\n- **Competitive win rate** — against primary competitors specifically\n- **Brand NPS** — awareness + preference scores in ICP\n\n---\n\n## Scoring & Traffic Lights\n\nEach dimension is scored 1-10 with traffic light:\n- 🟢 **Green (7-10):** Healthy — maintain and optimize\n- 🟡 **Yellow (4-6):** Watch — trend matters; improving or declining?\n- 🔴 **Red (1-3):** Action required — address within 30 days\n\n**Overall Health Score:**\nWeighted average by company stage (see `references\u002Fhealth-benchmarks.md` for weights).\n\n---\n\n## Dimension Interactions (Why One Problem Creates Another)\n\n| If this dimension is red... | Watch these dimensions next |\n|-----------------------------|----------------------------|\n| Financial Health | People (freeze hiring) → Engineering (freeze infra) → Product (cut scope) |\n| Revenue Health | Financial (cash gap) → People (attrition risk) → Market (lose positioning) |\n| People Health | Engineering (velocity drops) → Product (quality drops) → Revenue (churn rises) |\n| Engineering Health | Product (features slip) → Revenue (deals stall on product) |\n| Product Health | Revenue (NRR drops, churn rises) → Market (CAC rises; referrals dry up) |\n| Operational Health | All dimensions degrade over time (execution failure cascades everywhere) |\n\n---\n\n## Dashboard Output Format\n\n```\nORG HEALTH DIAGNOSTIC — [Company] — [Date]\nStage: [Seed\u002FA\u002FB\u002FC]   Overall: [Score]\u002F10   Trend: [↑ Improving \u002F → Stable \u002F ↓ Declining]\n\nDIMENSION SCORES\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n💰 Financial    🟢 8.2  Runway 14mo, burn 1.6x — strong\n📈 Revenue      🟡 5.8  NRR 104%, pipeline thin (1.8x coverage)\n🚀 Product      🟢 7.4  NPS 42, DAU\u002FMAU 38%\n⚙️  Engineering  🟡 5.2  Debt at 30%, MTTR 3.2h\n👥 People       🔴 3.8  Attrition 24%, eng morale low\n🔄 Operations   🟡 6.0  OKR 65% completion\n🔒 Security     🟢 7.8  SOC 2 Type II complete, 0 incidents\n📣 Market       🟡 5.5  CAC rising, win rate dropped to 22%\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTOP PRIORITIES\n🔴 [1] People: attrition at 24% — engineering velocity will drop in 60 days\n   Action: CHRO + CEO to run retention audit; target top 5 at-risk this week\n🟡 [2] Revenue: pipeline coverage at 1.8x — Q+1 miss risk is high\n   Action: CRO to add 3 qualified opps within 30 days or shift forecast down\n🟡 [3] Engineering: tech debt at 30% of sprint — shipping will slow by Q3\n   Action: CTO to propose debt sprint plan; COO to protect capacity\n\nWATCH\n→ People → Engineering cascade risk if attrition continues (see dimension interactions)\n```\n\n---\n\n## Graceful Degradation\n\nYou don't need all metrics to run a diagnostic. The tool handles partial data:\n- Missing metric → excluded from score, flagged as \"[data needed]\"\n- Score still valid for available dimensions\n- Report flags which gaps to fill for next cycle\n\n## References\n- `references\u002Fhealth-benchmarks.md` — benchmarks by stage (Seed, A, B, C)\n- `scripts\u002Fhealth_scorer.py` — CLI scoring tool with traffic light output\n","# Org Health Diagnostic\n\nEight dimensions. Traffic lights. Real benchmarks. Surfaces the problems you don't know you have.\n\n## Keywords\norg health, organizational health, health diagnostic, health dashboard, health check, company health, functional health, team health, startup health, health scorecard, health assessment, risk dashboard\n\n## Quick Start\n\n```bash\npython scripts\u002Fhealth_scorer.py        # Guided CLI — enter metrics, get scored dashboard\npython scripts\u002Fhealth_scorer.py --json # Output raw JSON for integration\n```\n\nOr describe your metrics:\n```\n\u002Fhealth [paste your key metrics or answer prompts]\n\u002Fhealth:dimension [financial|revenue|product|engineering|people|ops|security|market]\n```\n\n## The 8 Dimensions\n\n### 1. 💰 Financial Health (CFO)\n**What it measures:** Can we fund operations and invest in growth?\n\nKey metrics:\n- **Runway** — months at current burn (Green: >12, Yellow: 6-12, Red: \u003C6)\n- **Burn multiple** — net burn \u002F net new ARR (Green: \u003C1.5x, Yellow: 1.5-2.5x, Red: >2.5x)\n- **Gross margin** — SaaS target: >65% (Green: >70%, Yellow: 55-70%, Red: \u003C55%)\n- **MoM growth rate** — contextual by stage (see benchmarks)\n- **Revenue concentration** — top customer % of ARR (Green: \u003C15%, Yellow: 15-25%, Red: >25%)\n\n### 2. 📈 Revenue Health (CRO)\n**What it measures:** Are customers staying, growing, and recommending us?\n\nKey metrics:\n- **NRR (Net Revenue Retention)** — Green: >110%, Yellow: 100-110%, Red: \u003C100%\n- **Logo churn rate (annualized)** — Green: \u003C5%, Yellow: 5-10%, Red: >10%\n- **Pipeline coverage (next quarter)** — Green: >3x, Yellow: 2-3x, Red: \u003C2x\n- **CAC payback period** — Green: \u003C12 months, Yellow: 12-18, Red: >18 months\n- **Average ACV trend** — directional: growing, flat, declining\n\n### 3. 🚀 Product Health (CPO)\n**What it measures:** Do customers love and use the product?\n\nKey metrics:\n- **NPS** — Green: >40, Yellow: 20-40, Red: \u003C20\n- **DAU\u002FMAU ratio** — engagement proxy (Green: >40%, Yellow: 20-40%, Red: \u003C20%)\n- **Core feature adoption** — % of users using primary value feature (Green: >60%)\n- **Time-to-value** — days from signup to first core action (lower is better)\n- **Customer satisfaction (CSAT)** — Green: >4.2\u002F5, Yellow: 3.5-4.2, Red: \u003C3.5\n\n### 4. ⚙️ Engineering Health (CTO)\n**What it measures:** Can we ship reliably and sustain velocity?\n\nKey metrics:\n- **Deployment frequency** — Green: daily, Yellow: weekly, Red: monthly or less\n- **Change failure rate** — % of deployments causing incidents (Green: \u003C5%, Red: >15%)\n- **Mean time to recovery (MTTR)** — Green: \u003C1 hour, Yellow: 1-4 hours, Red: >4 hours\n- **Tech debt ratio** — % of sprint capacity on debt (Green: \u003C20%, Yellow: 20-35%, Red: >35%)\n- **Incident frequency** — P0\u002FP1 per month (Green: \u003C2, Yellow: 2-5, Red: >5)\n\n### 5. 👥 People Health (CHRO)\n**What it measures:** Is the team stable, engaged, and growing?\n\nKey metrics:\n- **Regrettable attrition (annualized)** — Green: \u003C10%, Yellow: 10-20%, Red: >20%\n- **Engagement score** — (eNPS or similar; Green: >30, Yellow: 0-30, Red: \u003C0)\n- **Time-to-fill (avg days)** — Green: \u003C45, Yellow: 45-90, Red: >90\n- **Manager-to-IC ratio** — Green: 1:5–1:8, Yellow: 1:3–1:5 or 1:8–1:12, Red: outside\n- **Internal promotion rate** — at least 25-30% of senior roles filled internally\n\n### 6. 🔄 Operational Health (COO)\n**What it measures:** Are we executing our strategy with discipline?\n\nKey metrics:\n- **OKR completion rate** — % of key results hitting target (Green: >70%, Yellow: 50-70%, Red: \u003C50%)\n- **Decision cycle time** — days from decision needed to decision made (Green: \u003C48h, Yellow: 48h-1w)\n- **Meeting effectiveness** — % of meetings with clear outcome (qualitative)\n- **Process maturity** — level 1-5 scale (see COO advisor)\n- **Cross-functional initiative completion** — % on time, on scope\n\n### 7. 🔒 Security Health (CISO)\n**What it measures:** Are we protecting customers and maintaining compliance?\n\nKey metrics:\n- **Security incidents (last 90 days)** — Green: 0, Yellow: 1-2 minor, Red: 1+ major\n- **Compliance status** — certifications current\u002Fin-progress vs. overdue\n- **Vulnerability remediation SLA** — % of critical CVEs patched within SLA (Green: 100%)\n- **Security training completion** — % of team current (Green: >95%)\n- **Pen test recency** — Green: \u003C12 months, Yellow: 12-24, Red: >24 months\n\n### 8. 📣 Market Health (CMO)\n**What it measures:** Are we winning in the market and growing efficiently?\n\nKey metrics:\n- **CAC trend** — improving, flat, or worsening QoQ\n- **Organic vs paid lead mix** — more organic = healthier (less fragile)\n- **Win rate** — % of qualified opportunities closed-won (Green: >25%, Yellow: 15-25%, Red: \u003C15%)\n- **Competitive win rate** — against primary competitors specifically\n- **Brand NPS** — awareness + preference scores in ICP\n\n---\n\n## Scoring & Traffic Lights\n\nEach dimension is scored 1-10 with traffic light:\n- 🟢 **Green (7-10):** Healthy — maintain and optimize\n- 🟡 **Yellow (4-6):** Watch — trend matters; improving or declining?\n- 🔴 **Red (1-3):** Action required — address within 30 days\n\n**Overall Health Score:**\nWeighted average by company stage (see `references\u002Fhealth-benchmarks.md` for weights).\n\n---\n\n## Dimension Interactions (Why One Problem Creates Another)\n\n| If this dimension is red... | Watch these dimensions next |\n|-----------------------------|----------------------------|\n| Financial Health | People (freeze hiring) → Engineering (freeze infra) → Product (cut scope) |\n| Revenue Health | Financial (cash gap) → People (attrition risk) → Market (lose positioning) |\n| People Health | Engineering (velocity drops) → Product (quality drops) → Revenue (churn rises) |\n| Engineering Health | Product (features slip) → Revenue (deals stall on product) |\n| Product Health | Revenue (NRR drops, churn rises) → Market (CAC rises; referrals dry up) |\n| Operational Health | All dimensions degrade over time (execution failure cascades everywhere) |\n\n---\n\n## Dashboard Output Format\n\n```\nORG HEALTH DIAGNOSTIC — [Company] — [Date]\nStage: [Seed\u002FA\u002FB\u002FC]   Overall: [Score]\u002F10   Trend: [↑ Improving \u002F → Stable \u002F ↓ Declining]\n\nDIMENSION SCORES\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n💰 Financial    🟢 8.2  Runway 14mo, burn 1.6x — strong\n📈 Revenue      🟡 5.8  NRR 104%, pipeline thin (1.8x coverage)\n🚀 Product      🟢 7.4  NPS 42, DAU\u002FMAU 38%\n⚙️  Engineering  🟡 5.2  Debt at 30%, MTTR 3.2h\n👥 People       🔴 3.8  Attrition 24%, eng morale low\n🔄 Operations   🟡 6.0  OKR 65% completion\n🔒 Security     🟢 7.8  SOC 2 Type II complete, 0 incidents\n📣 Market       🟡 5.5  CAC rising, win rate dropped to 22%\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nTOP PRIORITIES\n🔴 [1] People: attrition at 24% — engineering velocity will drop in 60 days\n   Action: CHRO + CEO to run retention audit; target top 5 at-risk this week\n🟡 [2] Revenue: pipeline coverage at 1.8x — Q+1 miss risk is high\n   Action: CRO to add 3 qualified opps within 30 days or shift forecast down\n🟡 [3] Engineering: tech debt at 30% of sprint — shipping will slow by Q3\n   Action: CTO to propose debt sprint plan; COO to protect capacity\n\nWATCH\n→ People → Engineering cascade risk if attrition continues (see dimension interactions)\n```\n\n---\n\n## Graceful Degradation\n\nYou don't need all metrics to run a diagnostic. The tool handles partial data:\n- Missing metric → excluded from score, flagged as \"[data needed]\"\n- Score still valid for available dimensions\n- Report flags which gaps to fill for next cycle\n\n## References\n- `references\u002Fhealth-benchmarks.md` — benchmarks by stage (Seed, A, B, C)\n- `scripts\u002Fhealth_scorer.py` — CLI scoring tool with traffic light output\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"domain":26,"updated":27,"version":28,"category":29,"frameworks":30,"python-tools":31},"Alireza Rezvani","organizational-health",1772668800000,"1.0.0","c-level","health-benchmarks","health_scorer.py","main","04d625a73841ac3f69c0d6ab4a7308680faffe02","c-level-advisor\u002Fskills\u002Forg-health-diagnostic","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002FciciliaETH","web3 dev, blockchain enthusiast, token reviewer, all about telegram bot.","2026-05-17 05:17:16",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add ciciliaETH\u002Fclaude-skills --skill org-health-diagnostic",{"tool":45,"command":46},"bunx","bunx skills add ciciliaETH\u002Fclaude-skills --skill org-health-diagnostic",{"tool":48,"command":49},"pnpm","pnpm dlx skills add ciciliaETH\u002Fclaude-skills --skill org-health-diagnostic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",true,[53,59],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fhealth-benchmarks.md","REFERENCE","参考文档",9094,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Freferences\u002Fhealth-benchmarks.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fhealth_scorer.py","SCRIPT","脚本",21377,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Fscripts\u002Fhealth_scorer.py",[66,73,80,87,92,97],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M730RQEKV70CXBH2TQF045GT","ra-qm-skills","12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017\u002F745, FDA 510(k)\u002FPMA, ISO 27001 ISMS, GDPR\u002FDSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fra-qm-skills\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M730QTT31DKCCZC573H22GX6","iso42001-specialist","ISO\u002FIEC 42001:2023 AI Management System (AIMS) specialist for compliance teams running internal audits. Three decisions: (1) Where are the gaps against Clauses 4-10 and what do we close first? (2) What goes in the AI risk register and which Annex A controls treat each risk? (3) What's the 12-month internal audit plan that satisfies Clause 9.2? Use when preparing for certification, scoping internal audit cycles, or onboarding AI systems into an existing ISMS (27001) \u002F QMS (13485) program. NOT an executive AI strategy skill (see chief-ai-officer-advisor). NOT EU AI Act compliance (see compliance-team-eu-ai-act).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M730Q40HCJJ97V6HGDF4FPS0","eu-ai-act-specialist","EU AI Act (Regulation (EU) 2024\u002F1689) operational compliance for compliance teams. Three Article-level decisions: (1) What's the risk tier of this AI system — prohibited (Art. 5), high-risk (Art. 6 + Annex III), limited-risk (Art. 50), or minimal-risk? (2) For high-risk systems, what's the Article 43 conformity assessment route (Module A internal control vs Module H full QMS + notified body) and what goes in the Annex IV technical documentation? (3) Per organizational role (provider \u002F deployer \u002F importer \u002F distributor \u002F authorized representative), what are the active obligations and deadlines? Use during AI system intake review, when planning conformity assessment, or when scoping deployer obligations. Cites Articles + Annexes for every output. NOT executive AI strategy (see chief-ai-officer-advisor). NOT a legal substitute.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":88,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M730PQWQ9N9FWV52Y14A1NJT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-iso42001\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":93,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M730PFX71VE2Q2HFHNYRDKQX","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-eu-ai-act\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M730NW4DAJ4JF9KRXMF35ADB","scrum-master","Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fscrum-master\u002FSKILL.md",[],[]]