[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CFFABAFPTQHK27THJDAQA":3,"skill-same:01M75CFFABAFPTQHK27THJDAQA":76},{"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},"01M75CFFABAFPTQHK27THJDAQA","ciso-advisor",null,"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.","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\u002Fciso-advisor\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"ciso-advisor\"\ndescription: \"Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ciso-leadership\n  updated: 2026-03-05\n  python-tools: risk_quantifier.py, compliance_tracker.py\n  frameworks: risk-based-security, zero-trust, defense-in-depth\n---\n\n# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\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","# CISO Advisor\n\nRisk-based security frameworks for growth-stage companies. Quantify risk in dollars, sequence compliance for business value, and turn security into a sales enabler — not a checkbox exercise.\n\n## Keywords\nCISO, security strategy, risk quantification, ALE, SLE, ARO, security posture, compliance roadmap, SOC 2, ISO 27001, HIPAA, GDPR, zero trust, defense in depth, incident response, board security reporting, vendor assessment, security budget, cyber risk, program maturity\n\n## Quick Start\n\n```bash\npython scripts\u002Frisk_quantifier.py      # Quantify security risks in $, prioritize by ALE\npython scripts\u002Fcompliance_tracker.py   # Map framework overlaps, estimate effort and cost\n```\n\n## Core Responsibilities\n\n### 1. Risk Quantification\nTranslate technical risks into business impact: revenue loss, regulatory fines, reputational damage. Use ALE to prioritize. See `references\u002Fsecurity_strategy.md`.\n\n**Formula:** `ALE = SLE × ARO` (Single Loss Expectancy × Annual Rate of Occurrence). Board language: \"This risk has $X expected annual loss. Mitigation costs $Y.\"\n\n### 2. Compliance Roadmap\nSequence for business value: SOC 2 Type I (3–6 mo) → SOC 2 Type II (12 mo) → ISO 27001 or HIPAA based on customer demand. See `references\u002Fcompliance_roadmap.md` for timelines and costs.\n\n### 3. Security Architecture Strategy\nZero trust is a direction, not a product. Sequence: identity (IAM + MFA) → network segmentation → data classification. Defense in depth beats single-layer reliance. See `references\u002Fsecurity_strategy.md`.\n\n### 4. Incident Response Leadership\nThe CISO owns the executive IR playbook: communication decisions, escalation triggers, board notification, regulatory timelines. See `references\u002Fincident_response.md` for templates.\n\n### 5. Security Budget Justification\nFrame security spend as risk transfer cost. A $200K program preventing a $2M breach at 40% annual probability has $800K expected value. See `references\u002Fsecurity_strategy.md`.\n\n### 6. Vendor Security Assessment\nTier vendors by data access: Tier 1 (PII\u002FPHI) — full assessment annually; Tier 2 (business data) — questionnaire + review; Tier 3 (no data) — self-attestation.\n\n## Key Questions a CISO Asks\n\n- \"What's our crown jewel data, and who can access it right now?\"\n- \"If we had a breach today, what's our regulatory notification timeline?\"\n- \"Which compliance framework do our top 3 prospects actually require?\"\n- \"What's our blast radius if our largest SaaS vendor is compromised?\"\n- \"We spent $X on security last year — what specific risks did that reduce?\"\n\n## Security Metrics\n\n| Category | Metric | Target |\n|----------|--------|--------|\n| Risk | ALE coverage (mitigated risk \u002F total risk) | > 80% |\n| Detection | Mean Time to Detect (MTTD) | \u003C 24 hours |\n| Response | Mean Time to Respond (MTTR) | \u003C 4 hours |\n| Compliance | Controls passing audit | > 95% |\n| Hygiene | Critical patches within SLA | > 99% |\n| Access | Privileged accounts reviewed quarterly | 100% |\n| Vendor | Tier 1 vendors assessed annually | 100% |\n| Training | Phishing simulation click rate | \u003C 5% |\n\n## Red Flags\n\n- Security budget justified by \"industry benchmarks\" rather than risk analysis\n- Certifications pursued before basic hygiene (patching, MFA, backups)\n- No documented asset inventory — can't protect what you don't know you have\n- IR plan exists but has never been tested (tabletop or live drill)\n- Security team reports to IT, not executive level — misaligned incentives\n- Single vendor for identity + endpoint + email — one breach, total exposure\n- Security questionnaire backlog > 30 days — silently losing enterprise deals\n\n## Integration with Other C-Suite Roles\n\n| When... | CISO works with... | To... |\n|---------|--------------------|-------|\n| Enterprise sales | CRO | Answer questionnaires, unblock deals |\n| New product features | CTO\u002FCPO | Threat modeling, security review |\n| Compliance budget | CFO | Size program against risk exposure |\n| Vendor contracts | Legal\u002FCOO | Security SLAs and right-to-audit |\n| M&A due diligence | CEO\u002FCFO | Target security posture assessment |\n| Incident occurs | CEO\u002FLegal | Response coordination and disclosure |\n\n## Detailed References\n- `references\u002Fsecurity_strategy.md` — risk-based security, zero trust, maturity model, board reporting\n- `references\u002Fcompliance_roadmap.md` — SOC 2\u002FISO 27001\u002FHIPAA\u002FGDPR timelines, costs, overlaps\n- `references\u002Fincident_response.md` — executive IR playbook, communication templates, tabletop design\n\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- No security audit in 12+ months → schedule one before a customer asks\n- Enterprise deal requires SOC 2 and you don't have it → compliance roadmap needed now\n- New market expansion planned → check data residency and privacy requirements\n- Key system has no access logging → flag as compliance and forensic risk\n- Vendor with access to sensitive data hasn't been assessed → vendor security review\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our security posture\" | Risk register with quantified business impact (ALE) |\n| \"We need SOC 2\" | Compliance roadmap with timeline, cost, effort, quick wins |\n| \"Prep for security audit\" | Gap analysis against target framework with remediation plan |\n| \"We had an incident\" | IR coordination plan + communication templates |\n| \"Security board section\" | Risk posture summary, compliance status, incident report |\n\n## Reasoning Technique: Risk-Based Reasoning\n\nEvaluate every decision through probability × impact. Quantify risks in business terms (dollars, not severity labels). Prioritize by expected annual loss.\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":14,"metadata":23,"description":7},{"author":24,"domain":25,"updated":26,"version":27,"category":28,"frameworks":29,"python-tools":30},"Alireza Rezvani","ciso-leadership",1772668800000,"1.0.0","c-level","risk-based-security, zero-trust, defense-in-depth","risk_quantifier.py, compliance_tracker.py","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor","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 ciso-advisor",{"tool":44,"command":45},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill ciso-advisor",{"tool":47,"command":48},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill ciso-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002FSKILL.md",true,[52,58,62,66,72],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcompliance_roadmap.md","REFERENCE","参考文档",16627,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fcompliance_roadmap.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fincident_response.md",16423,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fincident_response.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fsecurity_strategy.md",12079,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Freferences\u002Fsecurity_strategy.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Fcompliance_tracker.py","SCRIPT","脚本",31058,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Fcompliance_tracker.py",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Frisk_quantifier.py",28429,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fc-level-advisor\u002Fskills\u002Fciso-advisor\u002Fscripts\u002Frisk_quantifier.py",[77,85,92,99,106,113],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]