Skill Invocation Tracker
Instrument any skill with two-line track_start and track_end hooks so you see invocation volume, success rate, and median runtime.
Overview
skill-invocation-tracker is a MCP server for the Operate phase that adds append-only track_start and track_end telemetry to measure skill invocations and latency.
What is this MCP server?
- Append-only track_start and track_end helpers for minimal skill instrumentation
- Produces measurable invocation counts, success rates, and median wallclock
- Designed for daily skill-stats reporter consumption
- Flags dead skills at 0 invocations in 30 days and hot skills above 10 per day
- Instrumentation surface: two helpers (track_start, track_end)
- Dead skill heuristic: 0 invocations in 30 days
- Hot skill heuristic: more than 10 invocations per day
What problem does it solve?
You cannot tell which agent skills are ignored, flaky, or overloaded without per-skill usage and success metrics.
Who is it for?
Solo builders growing a skill catalog who need lightweight usage telemetry without standing up full APM.
Skip if: One-off scripts you never invoke through an agent skill runner or teams already standardized on OpenTelemetry everywhere.
What do I get? / Deliverables
Each instrumented skill emits start/end events so daily reports show invocation counts, success rates, median wallclock, dead skills, and hot skills.
- track_start and track_end instrumentation pattern
- Invocation counts and success rates per skill
- Inputs for identifying 0-invocation-in-30d and greater-than-10-per-day skills
Recommended MCP Servers
Journey fit
Measuring which skills actually run is core production ops once agents are live, not a pre-build prototyping task. Append-only invocation telemetry feeds daily stats reports to spot dead and hot skills—classic monitoring for an agent catalog.
How it compares
Skill-level invocation telemetry via MCP, not a hosted product analytics suite.
Common Questions / FAQ
Who is skill-invocation-tracker for?
Agent operators who maintain multiple skills and need invocation counts and success rates to prune or promote them.
When should I use skill-invocation-tracker?
As soon as skills go into regular agent use, before catalog bloat hides unused or failing entries.
How do I add skill-invocation-tracker to my agent?
Register the MCP server, wire track_start and track_end into skill run paths, and connect append-only logs to your daily skill-stats reporter.