[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CHSDR2CDDCJQC62R6EY7M":3,"skill-same:01M75CHSDR2CDDCJQC62R6EY7M":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M75CHSDR2CDDCJQC62R6EY7M","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.","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","organizational-health",1772668800000,"1.0.0","c-level","health-benchmarks","health_scorer.py","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository","https:\u002F\u002Fgithub.com\u002FAdmiralGallade","Eager to learn!\r\nI'll do anything for more knowledge anywhere.","2026-06-06 07:34:31",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill org-health-diagnostic",{"tool":44,"command":45},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill org-health-diagnostic",{"tool":47,"command":48},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill org-health-diagnostic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002FSKILL.md",true,[52,58],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fhealth-benchmarks.md","REFERENCE","参考文档",9094,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Freferences\u002Fhealth-benchmarks.md",{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"scripts\u002Fhealth_scorer.py","SCRIPT","脚本",21377,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Forg-health-diagnostic\u002Fscripts\u002Fhealth_scorer.py",[65,73,80,87,94,101],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75JSM6WGJ71BTHM6VC8CJ1X","verify-sign","Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75JSDSTP77TFM3JFGBB8QKP","template-usage","Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Ftemplate-usage\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75JS76Q2KC8PD598H2DZZRA","sign-artifact","Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build\u002Fpush; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsign-artifact\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75JS16EEFFHA44EBNE8KWNT","sei-analytics","Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsei-analytics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M75JRWE3X3E7V9JFQ4ENZYZM","security-report","Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says \"security report\", \"vulnerabilities\", \"SBOM\", \"security scan\", \"compliance check\", or asks about application security.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsecurity-report\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M75JRSFJSNZFZRFKX8MSPCS2","scorecard-review","Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says \"scorecard\", \"service maturity\", \"production readiness\", \"compliance score\", or asks about service health scores.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fscorecard-review\u002FSKILL.md",[],[]]