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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-06-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- scorecard-review
- license
- Apache-2.0
- metadata
- { "author": "Harness", "version": "2.0.0", "mcp-server": "harness-mcp-v2" }
- description
- 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.
- compatibility
- Requires Harness MCP v2 server (harness-mcp-v2)
03 SKILL.md 正文
Scorecard Review
Review service maturity and compliance scorecards using Harness Internal Developer Portal (IDP) via MCP.
Instructions
Step 1: List Catalog Entities
Call MCP tool: harness_list
Parameters:
resource_type: "idp_entity"
org_id: "<organization>"
project_id: "<project>"
Step 2: Get Entity Details
Call MCP tool: harness_get
Parameters:
resource_type: "idp_entity"
resource_id: "<entity_id>"
Step 3: Get Scorecard Scores
Call MCP tool: harness_list
Parameters:
resource_type: "idp_score"
org_id: "<organization>"
project_id: "<project>"
Get specific entity score:
Call MCP tool: harness_get
Parameters:
resource_type: "idp_score"
resource_id: "<entity_id>"
Step 4: Check Documentation
Call MCP tool: harness_list
Parameters:
resource_type: "idp_tech_doc"
org_id: "<organization>"
project_id: "<project>"
Step 5: Review Workflows
Call MCP tool: harness_list
Parameters:
resource_type: "idp_workflow"
org_id: "<organization>"
project_id: "<project>"
Common Scorecard Categories
- Production Readiness - CI/CD, monitoring, alerting, runbooks
- Security Compliance - Vulnerability scanning, secrets management, access control
- Documentation - API docs, architecture diagrams, runbooks
- Operational Excellence - SLOs, incident response, on-call
- Developer Experience - Build times, test coverage, onboarding
Report Format
## Service Scorecard Report
**Service:** <name>
**Overall Score:** X/100
### Category Scores
| Category | Score | Status |
|----------|-------|--------|
| Production Readiness | 85/100 | Pass |
| Security | 70/100 | Needs Work |
| Documentation | 45/100 | Failing |
| Operations | 90/100 | Pass |
### Failing Checks
1. Missing API documentation
2. No SBOM generation configured
3. Test coverage below 80%
### Improvement Actions
1. Add API docs to /docs endpoint
2. Enable SBOM in CI pipeline
3. Increase test coverage to 80%+
IDP Resource Types
| Resource Type | Operations | Description |
|---|---|---|
idp_entity |
list, get | Catalog entities |
idp_score |
list, get | Scorecard scores |
idp_tech_doc |
list, get | Technical docs |
idp_workflow |
list, get | IDP workflows |
Examples
- "How is api-gateway doing on scorecards?" - Get idp_score for entity
- "Which services are failing production readiness?" - List idp_score, filter by failing
- "Help me improve checkout-service score" - Get score, identify failing checks, suggest fixes
- "Show all services below 80% compliance" - List and filter idp_score
Performance Notes
- Analyze all scorecard checks before recommending improvements. Do not skip failing checks.
- Cross-reference failing checks with the service's actual configuration and documentation.
- Prioritize recommendations by impact — focus on checks that affect production readiness first.
Troubleshooting
No Scores Available
- Verify scorecards are configured in IDP settings
- Check entity is registered in the catalog
- Ensure data sources (CI/CD, monitoring) are connected
Scores Not Updating
- Check integration sync status
- Verify data source connectivity
- Review scorecard rule configuration
04 同仓库更多 Skills
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.
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).
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/push; 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.
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.
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.
run-pipeline
Execute and monitor Harness pipeline runs via MCP tools. Find pipelines, provide runtime inputs, trigger executions, monitor progress, handle approvals, retry failures, and abort running or stuck executions. Use when asked to run a pipeline, execute a deployment, trigger a build, start a pipeline, deploy a service, check execution status, approve a pipeline, or abort/stop/interrupt executions. Trigger phrases: run pipeline, execute pipeline, deploy, start build, trigger pipeline, check execution, approve deployment, retry failed pipeline, abort execution, stop pipeline, interrupt execution, kill stuck pipeline.