What would you like?
Emit a trace event each time any skill is invoked — bundled or project-local — and provide a script to aggregate invocation counts from trace output.
Motivation
There is no signal on which skills are actually used. Without usage data it is hard to prioritize improvements, retire dead skills, or validate that a skill justifies its token cost.
Proposed approach
Emit a skill.invoked trace event at skill entry. A companion aggregation script reads trace output locally — no external services, no data leaving the machine.
Scope
- Skill invocation path in the harness
scripts/
What would you like?
Emit a trace event each time any skill is invoked — bundled or project-local — and provide a script to aggregate invocation counts from trace output.
Motivation
There is no signal on which skills are actually used. Without usage data it is hard to prioritize improvements, retire dead skills, or validate that a skill justifies its token cost.
Proposed approach
Emit a
skill.invokedtrace event at skill entry. A companion aggregation script reads trace output locally — no external services, no data leaving the machine.Scope
scripts/