metrics

Aggregate git tags, value-hypothesis.yaml, and telemetry.db into a markdown report.

8|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill metrics-heavy-chain-engineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics
Source: https://github.com/Heavy-Chain-Engineering/etc/tree/main/skills/metrics
Command: npx skills add https://github.com/Heavy-Chain-Engineering/etc --skill metrics-heavy-chain-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill aggregates process data, outcome assessments, and cost telemetry into a single, reproducible markdown report, reducing manual collection and interpretation overhead.

Core Features & Use Cases

  • Deterministic processing of process data from git tags into a concise markdown report.
  • Outcome evaluation by loading value-hypothesis.yaml for each feature and summarizing per role with validation status.
  • Cost analysis from .etc_sdlc/telemetry.db with a date range and event-type breakdown for project health insights.
  • Use Case: A team runs a weekly health check and shares a consistent summary across stakeholders.

Quick Start

Run the metrics skill to emit the current repository's weekly three-layer report to stdout.

Frequently Asked Questions about metrics

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

FAQPage Schema
How do I generate a deterministic metrics report from git tags and SQLite telemetry?

This skill generates a deterministic metrics report by aggregating git tags, value-hypothesis.yaml files, and SQLite telemetry data into a single markdown report output to stdout.

What is a three-layer metrics report for software development?

A three-layer metrics report combines process data from git tags, outcome assessments from YAML files, and cost telemetry from a SQLite database to summarize project health.

Can I automate weekly health check reporting without manual data collection?

Yes, you can automate weekly health check reporting by running this skill non-interactively to read on-disk sources and emit a consistent summary markdown report for stakeholders.

Does the report generation process require an interactive setup or database connection configuration?

No interactive setup is required; the process operates non-interactively, reading exclusively from on-disk sources including git tags, YAML files, and the local telemetry SQLite database.

How does YAML outcome evaluation work when summarizing feature value hypotheses?

YAML outcome evaluation works by loading value-hypothesis.yaml files for each feature and summarizing the validation status per role within the generated markdown report.

What are the limitations of using on-disk SQLite telemetry for cost analysis?

A key limitation is that cost analysis strictly reads from the local .etc_sdlc/telemetry.db SQLite file, meaning it cannot query external databases or remote telemetry streams.