cursor-performance-tuning
Optimize Cursor IDE performance: reduce memory usage, speed up indexing, tune AI features, and manage extensions for large codebases. Triggers on "cursor performance", "cursor slow", "cursor optimization", "cursor memory", "speed up cursor", "cursor lag".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly communicates specific capabilities (memory reduction, indexing speed, AI feature tuning, extension management) for a well-defined niche (Cursor IDE performance). The explicit trigger terms cover natural user language variations effectively, and the description is concise without unnecessary padding. It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'reduce memory usage', 'speed up indexing', 'tune AI features', and 'manage extensions for large codebases'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (optimize Cursor IDE performance via memory, indexing, AI features, extensions) and 'when' (explicit trigger terms listed with 'Triggers on' clause). The trigger guidance is explicit and well-defined. | 3 / 3 |
Trigger Term Quality | Includes excellent natural keywords users would actually say: 'cursor performance', 'cursor slow', 'cursor optimization', 'cursor memory', 'speed up cursor', 'cursor lag'. These cover common variations of how users would describe performance issues with Cursor IDE. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific IDE (Cursor) with specific performance optimization tasks. The trigger terms are all Cursor-specific, making it very unlikely to conflict with general IDE or performance skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent concrete guidance—copy-paste ready settings, bash commands, and clear diagnostic workflows. Its main weakness is length: the document tries to cover everything inline rather than splitting detailed reference material (settings templates, .cursorignore examples, platform-specific cache paths) into separate files. Some minor verbosity in explanatory text could be trimmed to better respect token budget.
Suggestions
Extract the .cursorignore template, platform-specific cache paths, and extension audit table into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Trim explanatory sentences that describe what Claude already knows (e.g., 'Tab completion is fast by design', 'Cursor stores extension data in SQLite databases') to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—e.g., the enterprise considerations section and some explanatory text that Claude wouldn't need. The diagnostic workflow ASCII tree is helpful but the overall document could be tightened by ~20-30%. Some sections like 'Tab completion is fast by design (~100ms)' explain things Claude already knows. | 2 / 3 |
Actionability | Highly actionable throughout: provides copy-paste ready settings.json blocks, executable bash commands for cache clearing and memory monitoring, specific .cursorignore contents, concrete command palette actions, and a detailed table of extensions with specific mitigation settings. Nearly everything is directly executable. | 3 / 3 |
Workflow Clarity | The diagnostic workflow at the top provides a clear decision tree for identifying bottlenecks and routing to the correct section. Steps are well-sequenced within each section (e.g., cache clearing followed by restart, memory monitoring with thresholds and remediation steps). The 'Signs of chat-related slowdown' section includes a clear symptom→fix pattern. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and logical sections, but it's a long monolithic document (~200+ lines of substantive content) with no bundle files to offload detail into. The .cursorignore template, extension audit details, and cache management commands could each be separate referenced files. The Resources section at the end provides external links but no internal file references for progressive discovery. | 2 / 3 |
Total | 10 / 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
09b10d6
- 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.