dora-metrics

Generate DORA metrics reports from Harness SEI via MCP.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill dora-metrics-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dora-metrics
Source: https://github.com/harness/harness-skills/tree/main/skills/dora-metrics
Command: npx skills add https://github.com/harness/harness-skills --skill dora-metrics-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DORA metrics provide a clear view of software delivery performance, but collecting, aligning, and interpreting frequency, lead time, CFR, and MTTR across teams and time ranges is complex without a unified tool. This skill uses Harness SEI via MCP to generate standardized reports, benchmarks, and drilldowns to support data-driven improvement.

Core Features & Use Cases

  • Consolidated DORA variants are exposed through a single resource type (sei_dora_metric) with a metric parameter to switch between deployment_frequency, lead_time, change_failure_rate, and mttr.
  • Drilldown and team-scoped insights: obtain per-deployment details and CFR breakdowns, and retrieve team-level mappings for developer and integration data.
  • Use Case: an engineering manager wants a weekly CFR trend for a team and a daily deployment cadence to identify bottlenecks and improve change adoption.

Quick Start

Ask it to generate a DORA metrics report for a given team between two dates.

Frequently Asked Questions about dora-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate DORA metrics for a specific engineering team over a custom date range?

To generate DORA metrics, you provide a team reference ID, start and end dates, and time granularity. The skill aggregates deployment frequency, lead time, change failure rate, and MTTR via SEI to deliver a standardized performance report.

Can I retrieve per-deployment drilldown details for change failure rate?

Yes, you can retrieve per-deployment drilldown details and change failure rate breakdowns. The skill exposes team-scoped insights, allowing engineering managers to analyze specific deployment failures alongside overall DORA metric trends.

What DORA metrics are supported for calculating software delivery performance?

Supported DORA metrics include deployment frequency, lead time for changes, change failure rate, and mean time to recovery (MTTR). These are exposed through a single resource type with parameters to switch between each metric.

Does the DORA metrics skill support daily and weekly granularity for trend analysis?

Yes, the skill supports daily, weekly, and monthly granularity. This allows you to track deployment cadence or identify bottlenecks over your requested date range, supporting agile planning and continuous process improvements.

Do I need a team reference ID to report MTTR and deployment frequency?

Yes, a team reference ID is a required input to report MTTR and deployment frequency. You must also specify start and end dates along with the desired granularity to retrieve accurate team-level mappings and integration data.

Why use SEI for aggregating lead time and MTTR instead of manual tracking?

Using SEI standardizes the collection and alignment of lead time, MTTR, and deployment frequency across teams. It automates data aggregation and provides drilldown capabilities, eliminating the complexity and misalignment of manual tracking methods.