track-metrics

Record task outcomes into metrics.json with standardized fields.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/DennisToma/repo_example --skill track-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-metrics
Source: https://github.com/DennisToma/repo_example/tree/main/.claude/skills/track-metrics
Command: npx skills add https://github.com/DennisToma/repo_example --skill track-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often fail to translate completed work into measurable indicators. The track-metrics skill records objective task outcomes to transform efforts into actionable data, enabling better decision-making and accountability.

Core Features & Use Cases

  • After a task completes (e.g., /verify), it writes a structured entry to .claude/metrics/metrics.json for trend analysis.
  • Captures fields such as task_type, outcome, description, skills_used, hooks_triggered, verification, and attempts to support reporting and quality tracking.
  • Use cases include sprint reviews, process improvement initiatives, and QA of workflow reliability.

Quick Start

After finishing a task, insert a new entry into .claude/metrics/metrics.json with the required fields. Example: describe the task_type, outcome, and a brief description; ensure the metrics file exists and is writable.

Frequently Asked Questions about track-metrics

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

FAQPage Schema
How do I record task outcomes to a metrics file for workflow tracking?

To record task outcomes, insert a structured entry into your metrics file containing fields like task_type, outcome, description, skills_used, and verification after a task completes. This translates completed work into measurable data for trend analysis.

What task metadata should I track for feature, bugfix, and refactor tasks?

You should track task_type, outcome, description, skills_used, hooks_triggered, verification, and attempts for feature, bugfix, and refactor tasks. Standardizing these fields in your metrics file supports consistent quality tracking and process improvement reporting.

When do I need to write metrics entries for completed tasks?

You need to write metrics entries after a task completes, such as following a verification step. Recording objective outcomes at this stage ensures accurate measurement of whether your repository's systems are actually improving results.

How does tracking structured task outcomes support sprint reviews?

Tracking structured task outcomes supports sprint reviews by transforming development efforts into actionable data. By capturing fields like attempts and verification status in a metrics file, teams gain measurable indicators for better decision-making and accountability.

Do I need a specific file path to start logging workflow metrics?

Yes, you need a designated metrics file path, such as .claude/metrics/metrics.json, which must exist and be writable. This file receives the standardized structured entries required for each recorded task outcome.

What is the best way to quantify progress for completed repository tasks?

The best way to quantify progress is to log objective outcomes into a structured metrics file after task completion. Capturing standardized fields like task_type and verification results enables reliable trend analysis and workflow reliability assessment.