Feature request for product/service
– Other –
Describe the request
Hey folks,
With SKILL.md adoption growing across teams, there’s a gap in the Analytics API. We can track command adoption via /analytics/team/commands, but there’s no visibility into how custom skills are being used.
The problem:
For teams investing in custom skills (API validation, testing patterns, architecture standards, etc.), there’s currently no way to measure adoption or ROI. Skills get consumed as agent context during chat/composer sessions, so they don’t surface in any existing analytics endpoint. You’re essentially flying blind on whether the skills you built are actually being used.
What would help:
A dedicated endpoint like GET /analytics/team/skills that returns daily usage broken down by skill name, similar to how commands adoption works today. Ideally something like:
{
“data”: [
{
“event_date”: “2025-02-10”,
“skill_name”: “api-validation”,
“invocations”: 34
}
]
}
Bonus points for:
- Distinguishing between built-in vs custom skills
- Tracking whether the skill was invoked via slash command, auto-detected, or MCP
Why this matters:
Enterprise teams rolling out Cursor at scale need to justify the investment in building and maintaining custom skills. Without adoption data, it’s hard to know which skills to improve, deprecate, or promote across the org. This is especially relevant now that skills are becoming a core part of the Cursor workflow alongside subagents and rules.
For the broader community, this would also help open-source skill authors understand which skills are getting traction and where to focus their efforts.