cursor-usage-analytics
Track and analyze Cursor usage metrics via admin dashboard: requests, model usage, team productivity, and cost optimization. Triggers on "cursor analytics", "cursor usage", "cursor metrics", "cursor reporting", "cursor dashboard", "cursor ROI".
54
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-usage-analytics/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with excellent trigger terms and clear distinctiveness. Its main weakness is that the capabilities listed are somewhat categorical rather than describing concrete actions (e.g., 'track and analyze' is somewhat generic). Adding specific actions like 'generate usage reports', 'compare team productivity trends', or 'calculate per-seat costs' would strengthen it.
Suggestions
Replace or supplement the category-level terms ('requests, model usage, team productivity, cost optimization') with specific concrete actions like 'generate usage reports, compare team productivity trends, calculate per-seat ROI, monitor model-specific request volumes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor usage metrics via admin dashboard) and lists some areas (requests, model usage, team productivity, cost optimization), but these are more like categories than concrete actions. It doesn't specify what actions are performed (e.g., 'generate reports', 'export CSV', 'compare monthly trends'). | 2 / 3 |
Completeness | Clearly answers both 'what' (track and analyze Cursor usage metrics including requests, model usage, team productivity, cost optimization) and 'when' (explicit trigger terms listed with 'Triggers on' clause). The trigger guidance is explicit. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms that users would likely say: 'cursor analytics', 'cursor usage', 'cursor metrics', 'cursor reporting', 'cursor dashboard', 'cursor ROI'. These are specific and varied enough to cover common user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Cursor' (specific tool) with 'admin dashboard', 'usage metrics', and 'ROI' creates a clear niche that is unlikely to conflict with other skills. The trigger terms are all prefixed with 'cursor' making them very targeted. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a knowledge base article or wiki page than an actionable skill for Claude. It contains substantial informational content (metric definitions, benchmarks, templates) that Claude could largely generate itself, while lacking the executable, tool-specific guidance that would make it truly useful. The optimization playbooks and quota strategies provide some value but are mostly generic management advice rather than concrete, automatable steps.
Suggestions
Cut the ASCII dashboard mockup, basic ROI arithmetic, and report template — Claude can generate these on demand. Focus on the non-obvious: specific API endpoints, exact dashboard navigation paths, and threshold values.
Add executable scripts or API calls for programmatically retrieving usage data, especially for Enterprise plans that mention API access.
Split the report template and optimization playbooks into separate referenced files to reduce the main skill's token footprint.
Add validation checkpoints to the optimization playbooks, e.g., 'After enabling Auto mode, check quota usage after 1 week — if still over 90%, proceed to step 4.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose with extensive ASCII art dashboards, multiple large tables, and lengthy templates that Claude doesn't need spelled out. The ROI calculation section explains basic arithmetic, the report template is boilerplate Claude could generate on its own, and the optimization playbooks contain generic management advice rather than tool-specific instructions. | 1 / 3 |
Actionability | The skill provides some concrete guidance like specific URLs, threshold numbers, and structured playbooks, but lacks executable code or commands. Most content is informational tables and templates rather than actionable steps Claude can directly execute. There are no API calls, scripts, or programmatic ways to actually retrieve or analyze the metrics. | 2 / 3 |
Workflow Clarity | The optimization playbooks provide numbered steps for different scenarios, and quota management strategies are sequenced. However, there are no validation checkpoints or feedback loops — for example, no way to verify whether optimization steps actually reduced quota usage, and no explicit decision tree for choosing between the different playbooks. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but it's a monolithic document with no references to supporting files. The report template, ROI calculation, and detailed optimization playbooks could be split into separate referenced files. External links are provided but only to Cursor's website, not to bundle files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
6e9558f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.