agentleFS
Sign inStart free
thisrohanguptathisrohangupta/harness-skills/skills/dora-metrics/SKILL.md

dora-metrics

Skill2 starsChanged 7 months agoApache-2.0Archived repositoryView on GitHub

Generate DORA metrics and engineering performance reports using Harness SEI via MCP. Track deployment frequency, lead time, change failure rate, and MTTR. Use when user says "DORA metrics", "deployment frequency", "lead time", "engineering metrics", or asks about team performance.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    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 SEI integrations are configured (Git, CI/CD, issue tracking)

    line 155
  2. Distinctive:

    Check team mappings exist

    line 156
  3. Distinctive:

    Verify deployment detection rules in SEI settings

    line 160
  4. Distinctive:

    Check failure classification criteria

    line 161

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

DORA Metrics

Generate DORA metrics reports using Harness Software Engineering Insights (SEI) via MCP.

Instructions

Step 1: Get DORA Metrics

Deployment Frequency:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_deployment_frequency"

Lead Time for Changes:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_lead_time"

Change Failure Rate:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_change_failure_rate"

Mean Time to Recovery:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_mttr"

Step 2: Get Drilldown Data

For detailed deployment frequency:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_deployment_frequency_drilldown"

For detailed change failure rate:

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_change_failure_rate_drilldown"

Step 3: Get Team Data

Call MCP tool: harness_list
Parameters:
  resource_type: "sei_team"
Call MCP tool: harness_list
Parameters:
  resource_type: "sei_team_developer"

Step 4: AI Metrics (Optional)

Call MCP tool: harness_get
Parameters:
  resource_type: "sei_ai_adoption"

Also: sei_ai_adoption_breakdown, sei_ai_impact, sei_ai_usage, sei_ai_usage_breakdown

DORA Benchmarks

MetricEliteHighMediumLow
Deployment FrequencyMultiple/dayWeekly-MonthlyMonthly-6mo6mo+
Lead Time< 1 hour1 day-1 week1-6 months6mo+
Change Failure Rate< 5%5-10%10-15%> 15%
MTTR< 1 hour< 1 day1 day-1 week1 week+

Report Format

## DORA Metrics Report

**Period:** <date range>
**Team:** <team or org>

### Performance Summary

| Metric | Value | Rating | Trend |
|--------|-------|--------|-------|
| Deployment Frequency | X/week | High | Improving |
| Lead Time | X hours | Elite | Stable |
| Change Failure Rate | X% | Medium | Needs attention |
| MTTR | X hours | High | Improving |

### Overall Rating: <Elite/High/Medium/Low>

### Recommendations
1. CFR at X% - invest in test automation and code review
2. Lead time trending up - look at PR review bottlenecks
3. Consider feature flags to decouple deploy from release

SEI Resource Types

Resource TypeOperationsDescription
sei_deployment_frequencygetDeploy frequency metric
sei_deployment_frequency_drilldowngetDetailed frequency data
sei_lead_timegetLead time for changes
sei_change_failure_rategetChange failure rate
sei_change_failure_rate_drilldowngetDetailed CFR data
sei_mttrgetMean time to recovery
sei_teamlist, getTeam definitions
sei_team_developerlistTeam members
sei_metriclist, getGeneric metrics
sei_org_treegetOrganization structure
sei_business_alignmentgetBusiness alignment
sei_ai_adoptiongetAI adoption metrics

Examples

  • "How are we doing on DORA metrics?" - Get all 4 metrics, compare to benchmarks
  • "Compare DORA across teams" - List teams, get metrics per team
  • "What's our deployment frequency trend?" - Get sei_deployment_frequency with drilldown
  • "Show AI adoption metrics" - Get sei_ai_adoption and breakdown

Performance Notes

  • Gather metrics across the full requested time range before generating the report. Partial data skews results.
  • Compare metrics across multiple time periods to identify trends, not just snapshots.
  • Quality of analysis and actionable recommendations is more important than speed.

Troubleshooting

No Metric Data

  • Verify SEI integrations are configured (Git, CI/CD, issue tracking)
  • Check team mappings exist
  • Allow time for data collection and calculation

Metrics Seem Incorrect

  • Verify deployment detection rules in SEI settings
  • Check failure classification criteria
  • Review team member mappings

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