Skip to content
Back to skills

271 Metrics 2d8815c0

ASecurity

View agent performance metrics and session history. Shows usage patterns, files changed, and session summaries.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
toolsbashperformance

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 271-metrics_2d8815c0 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 271 Metrics 2d8815c0?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 271 Metrics 2d8815c0
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-271-metrics-2d8815c0/badge)](https://www.skillsdirectory.com/skills/tools-only-271-metrics-2d8815c0)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
allowed-tools: Read, Bash, Glob
description: View agent performance metrics and session history. Shows usage patterns, files changed, and session summaries.
---

## Context

- Metrics file: !`cat .claude/agent-metrics.jsonl 2>/dev/null || echo "NO_METRICS_FILE"`

## Task

Analyze the agent performance metrics and present a summary.

**If the metrics file does not exist or the context above shows "NO_METRICS_FILE":**
Print exactly: "No metrics recorded yet. Metrics are automatically collected after each session."

**If metrics data exists**, parse each JSON line and present:

1. **Overview**
   - Total sessions logged
   - Sessions in the last 7 days (compare timestamps to now)
   - Average files changed per session

2. **Recent Sessions** (last 10)
   Format as a markdown table:

   | #   | Timestamp (UTC) | Files Changed | Commit | Status |
   | --- | --------------- | ------------- | ------ | ------ |
   - Show the most recent 10 sessions, newest first
   - For "Commit", show the short commit message or "—" if none
   - For "Status", show the duration_hint value

3. **Patterns**
   - Note any trends (e.g., sessions with many file changes, frequency of commits)
   - If there are sessions with 0 files changed, note how many were "no-op" sessions

Keep the output concise and well-formatted.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…