cmetrics

Compile project health, ROI, and workflow metrics from QA and code data.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill cmetrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmetrics
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/cmetrics
Command: npx skills add https://github.com/joshft/correctless --skill cmetrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project health and ROI tracking by aggregating data from QA findings, verification, drift, antipatterns, and token logs into a single dashboard to inform decisions and demonstrate workflow value.

Core Features & Use Cases

  • Dashboard-driven insights: aggregates data across QA findings, verification, drift debt, antipatterns, and milestones to show trends, ROI, and bug patterns.
  • Periodic health checks: runs monthly or pre-present to stakeholders to justify investments and action items.
  • Operational visibility: surfaces metrics like bugs caught, token cost, cycle times, and escape rates to guide process improvements.
  • Use Case: generate a project health dashboard at month end to present to leadership with key drivers and risks.

Quick Start

Run the metrics dashboard to compile the latest project health and ROI data from all sources.

Frequently Asked Questions about cmetrics

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

FAQPage Schema
How do I track project health and ROI from QA findings and token logs?

Track project health and ROI by aggregating QA findings, verification, drift debt, antipatterns, and token usage into a unified dashboard. This process surfaces trends, escape rates, and ROI estimates to justify investments and guide workflow improvements.

What is the best way to compile metrics for a monthly stakeholder briefing?

The best way to compile metrics for monthly stakeholder briefings is to synthesize code delivery timelines and bug patterns into a single dashboard. This exposes operational visibility like cycle times and token costs to demonstrate workflow value.

Can I generate a project health dashboard without manual data aggregation?

Yes, you can generate a project health dashboard without manual aggregation by running an automated compilation across diverse data sources. It identifies and synthesizes metrics from QA findings, drift debt, and antipatterns automatically.

Does tracking workflow efficiency require connecting multiple separate data sources?

Tracking workflow efficiency requires connecting data from QA findings, verification, drift debt, antipatterns, and token logs. Aggregating these diverse sources into a single dashboard is necessary to accurately surface trends and calculate ROI estimates.

When do I need to run a dashboard-driven project health check?

You need to run a dashboard-driven project health check at month end or pre-presentation to stakeholders. It justifies investments and highlights action items by surfacing metrics like bugs caught, token cost, and escape rates.