agentleFS
Sign inStart free
thisrohanguptathisrohangupta/harness-skills/skills/scorecard-review/SKILL.md

scorecard-review

Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub

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.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify scorecards are configured in IDP settings

    line 136
  2. Distinctive:

    Check entity is registered in the catalog

    line 137
  3. Distinctive:

    Ensure data sources (CI/CD, monitoring) are connected

    line 138
  4. Distinctive:

    Check integration sync status

    line 141
  5. Distinctive:

    Verify data source connectivity

    line 142

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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 TypeOperationsDescription
idp_entitylist, getCatalog entities
idp_scorelist, getScorecard scores
idp_tech_doclist, getTechnical docs
idp_workflowlist, getIDP 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free