metrics

Compute pipeline timing metrics from YAML frontmatter and Git/PR data.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/dpaola2/pipeline-skills --skill metrics-dpaola2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/metrics
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill metrics-dpaola2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the computation and reporting of pipeline timing metrics, providing insights into project duration, human review time, and agent efficiency.

Core Features & Use Cases

  • Automated Metric Calculation: Gathers timing data from artifact frontmatter and Git/PR information.
  • Detailed Reporting: Generates a comprehensive report including stage durations, wait times, and summary metrics.
  • Use Case: After a development cycle, use this Skill to understand where delays occurred in the pipeline, identify bottlenecks in human review, and calculate the overall lead time from PRD to merged PR.

Quick Start

Use the metrics skill to compute and display pipeline timing metrics for the work item 'SN-3'.

Frequently Asked Questions about metrics

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

FAQPage Schema
How do I compute pipeline timing metrics for a project from Git and PR data?

To compute pipeline timing metrics, this Skill parses YAML frontmatter from WCP artifacts and enriches it with Git and GitHub CLI data to calculate stage durations, human review times, and overall lead time for a given project callsign.

What is the best way to analyze agent efficiency and human review time in a development pipeline?

Analyzing agent efficiency involves parsing artifact frontmatter to extract stage durations and wait times, then enriching that data with Git and PR information to calculate the overall lead time from PRD to merged PR.

Do I need GitHub CLI and Git access to calculate lead time from PRD to merged PR?

Yes, you need access to Git, the GitHub CLI, and WCP artifacts to retrieve the data required for calculating lead time, as the Skill enriches YAML frontmatter with Git and PR data to generate the report.

Can I use pipeline performance analytics to identify bottlenecks in stage durations?

Yes, pipeline performance analytics can identify bottlenecks by generating a detailed report of stage durations, wait times, and human review times, highlighting where delays occurred during the development cycle.

How do I report on pipeline wait times and stage durations after a development cycle?

You can report on pipeline wait times and stage durations by running the metrics analysis on a specific project callsign, which automatically gathers and parses YAML frontmatter to generate a comprehensive timing report.

What limitations exist when parsing YAML frontmatter from WCP artifacts for metrics reporting?

The metrics reporting relies on accurately parsing YAML frontmatter from WCP artifacts and requires proper Git and GitHub CLI access; without these dependencies, the Skill cannot retrieve the data needed to calculate timing metrics.