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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A genuinely useful, actionable analytics reference, but it underuses its own bundle (reference files are never linked) and carries some decorative padding. Tightening the inline content and wiring up the references would materially improve it.

Suggestions

Link the existing references/*.md files from the body (e.g., a '## References' section pointing to dashboard-views.md, custom-reports.md, optimization-insights.md, best-practices.md) so the bundle is actually discoverable.

Move detailed inline material (report template, ROI calculation, optimization playbooks, enterprise considerations) into the matching reference files, keeping SKILL.md a concise overview.

Trim the ASCII dashboard mockup and consolidate the three optimization playbooks into a single decision-tree to reduce token overhead while preserving actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and practical, but the ~20-line ASCII dashboard mockup and several self-evident playbook steps are padding that could be tightened without losing actionable value.	2 / 3
Actionability	Gives concrete, copy-paste-ready guidance: specific nav path and URL, metric thresholds (30-50% acceptance, 80%+ of seats), a fill-in monthly report template, and an ROI formula with actual numbers — fully actionable for an instruction skill.	3 / 3
Workflow Clarity	Numbered optimization playbooks and the report template provide clear sequences, but there are no explicit validation checkpoints or feedback loops, and the end-to-end analysis workflow is not presented as a single sequenced process.	2 / 3
Progressive Disclosure	The body is well-sectioned with headers, but 10 reference bundle files exist in references/ and are never linked or signaled from the overview, while detailed content (templates, playbooks, enterprise notes) stays inline that could be offloaded to those files.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete actions, explicit trigger guidance, and a clear niche. Minor formatting noise (stray blank lines inside the YAML value) does not affect content quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'track and analyze Cursor usage metrics via admin dashboard: requests, model usage, team productivity, and cost optimization' — matching the anchor for several specific concrete actions rather than a single domain/action.	3 / 3
Completeness	Explicitly answers both 'what' (track/analyze usage metrics) and 'when' via the explicit 'Triggers on ...' clause, which is equivalent to a 'Use when' trigger guidance, so it is not capped at 2.	3 / 3
Trigger Term Quality	Provides six natural trigger phrases ('cursor analytics', 'cursor usage', 'cursor metrics', 'cursor reporting', 'cursor dashboard', 'cursor ROI') that a user would plausibly say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Cursor-usage-analytics niche with distinct 'cursor ...' triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.