Agent skill · AI & Agents

metrics

Collect and report metrics on agent usage from git history implementing the 8 key metrics defined in agent-metrics.md for measuring agent system health effectiveness and adoption.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill metrics --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/analysis/metrics/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Metrics Collection Utility ## Purpose This utility collects and reports metrics on agent usage from git history. It implements the 8 key metrics defined in `docs/agent-metrics.md` for measuring agent system health, effectiveness, and adoption. ## Available Scripts | Script | Platform | Usage | |--------|----------|-------| | `collect_metrics.py` | Python 3.8+ | Cross-platform | | `collect-metrics.ps1` | PowerShell 5.1+ | Windows/Linux/macOS | ## Quick Start ### Python ```bash # Basic usage (30 days, summary output) python .claude/skills/metrics/collect_metrics.py # Last 90 days as markdown python .claude/skills/metrics/collect_metrics.py --since 90 --output markdown # JSON output for automation python .claude/skills/metrics/collect_metrics.py --output json ``` ### PowerShell ```powershell # Basic usage (30 days, summary output) .\.agents\utilities\metrics\collect-metrics.ps1 # Last 90 days as markdown .\.agents\utilities\metrics\collect-metrics.ps1 -Since 90 -Output Markdown # JSON output for automation .\.agents\utilities\metrics\collect-metrics.ps1 -Output Json | ConvertFrom-Json ``` ## Metrics Collected The utility collects the following metrics: | Metric | Description |

What's inside
Steps it walks through
  1. Purpose
  2. Available Scripts
  3. Quick Start
  4. Python
  5. PowerShell
  6. Metrics Collected
  7. Detection Patterns
  8. Agent Detection
  9. Infrastructure Files
  10. Commit Types
  11. Output Formats
  12. Summary (Default)
  13. Markdown
  14. JSON
Ships with 1 file
  • metadata.json
Commands it runs
Basic usage (30 days, summary output)
python .claude/skills/metrics/collect_metrics.py
Last 90 days as markdown
python .claude/skills/metrics/collect_metrics.py --since 90 --output markdown
JSON output for automation
python .claude/skills/metrics/collect_metrics.py --output json
Generate report
python .claude/skills/metrics/collect_metrics.py \
Review and commit
git add .agents/metrics/
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the metrics skill do?

Collect and report metrics on agent usage from git history implementing the 8 key metrics defined in agent-metrics.md for measuring agent system health effectiveness and adoption.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill metrics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.