Skill Stats Reporter
Turn skill invocation telemetry into daily dead-skill, hot-skill, failure-rate, and latency reports for cleanup decisions.
Overview
Skill Stats Reporter is an MCP server for the Operate phase that aggregates skill-telemetry JSONL into daily dead, hot, failure, and latency stats with a review markdown export.
What is this MCP server?
- Ingests data/skill-telemetry/invocations.jsonl
- Flags dead skills: zero invocations in the last 30 days
- Flags hot skills: more than 10 invocations per day on average
- Per-skill failure rates and median wallclock
- Writes dead-skill list to data/skill-telemetry/dead-skills-pending-review.md
- Dead skill window: zero invocations in last 30 days
- Hot skill threshold: greater than 10 invocations/day average
- Input path: data/skill-telemetry/invocations.jsonl
What problem does it solve?
Skill libraries rot quietly because you cannot see which skills never run, which ones fail often, or how slow they are.
Who is it for?
Solo builders and ops agents maintaining dozens of skills with local invocation logging.
Skip if: Greenfield projects with no telemetry JSONL or teams who only track public marketplace installs.
What do I get? / Deliverables
You get a daily operational picture and a dead-skills-pending-review file to batch deprecate or fix skills.
- Daily stats summary (dead, hot, failure, latency)
- dead-skills-pending-review.md for batch review
- Per-skill median wallclock and failure rate figures
Recommended MCP Servers
Journey fit
Operate is the canonical phase because the server watches production-like skill usage after shipping, not the act of writing skills. Monitoring fits JSONL invocation analytics, failure rates, and dead-skill lists pending human promote-or-delete review.
How it compares
Private skill telemetry reporter—not skills.sh trending or a generic APM dashboard.
Common Questions / FAQ
Who is skill-stats-reporter for?
Operators and indie builders who log skill invocations locally and need daily hygiene metrics.
When should I use skill-stats-reporter?
Use it once invocations.jsonl is populated and you want automated dead-skill and hot-skill lists for review.
How do I add skill-stats-reporter to my agent?
Register the MCP server, ensure data/skill-telemetry/invocations.jsonl exists, and schedule or invoke the daily reporter.