cursor-performance-tuning
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-performance-tuningOptimize Cursor IDE performance. Triggers on "cursor performance", "cursor slow", "cursor optimization", "cursor memory", "speed up cursor". Use when working with cursor performance tuning functionality. Trigger with phrases like "cursor performance tuning", "cursor tuning", "cursor".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
22%This skill provides a structural outline but lacks the concrete, actionable content needed to be useful. The instructions are abstract descriptions rather than specific commands or settings, and there are no code examples, specific setting paths, or configuration snippets. The skill relies heavily on external references without providing sufficient standalone value.
Suggestions
Add specific Cursor settings paths and values, e.g., 'Set `editor.minimap.enabled: false` in Settings > Editor' with exact navigation steps
Include concrete .cursorignore examples showing patterns to exclude (e.g., `node_modules/`, `*.log`, `.git/`)
Provide specific Process Explorer metrics to look for and threshold values that indicate problems (e.g., 'CPU > 30% idle indicates extension issues')
Add a validation step with before/after metrics to verify performance improvements were achieved
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the 'Prerequisites' section stating obvious requirements ('Cursor IDE installed', 'Understanding of extensions'). The 'Output' section describes expected outcomes rather than actionable content. | 2 / 3 |
Actionability | Instructions are vague and abstract with no concrete commands, settings paths, or executable examples. 'Use Process Explorer to identify bottlenecks' and 'Disable visual features' provide no specific guidance on what to do or where to find these settings. | 1 / 3 |
Workflow Clarity | Steps are listed but lack any specificity, validation checkpoints, or feedback loops. There's no indication of how to verify performance improvements or what metrics to check before/after changes. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too sparse to serve as a useful overview. The skill offloads critical content (examples, error handling) without providing enough actionable guidance in the main file. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
55%The description has strong trigger term coverage but lacks specificity about what optimization actions are actually performed. The 'what' portion is too vague ('optimize performance') while the 'when' portion is adequately covered with explicit triggers. The generic 'cursor' trigger term creates potential conflict risk with other Cursor-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Adjusts memory limits, clears extension cache, configures indexing settings, disables resource-heavy features'
Remove the overly generic 'cursor' trigger term to reduce conflict risk with other Cursor IDE skills
Specify what types of performance issues this addresses (startup time, memory usage, responsiveness, large file handling)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Optimize Cursor IDE performance' without listing concrete actions. It doesn't specify what optimization actions are performed (e.g., clearing cache, adjusting settings, disabling extensions). | 1 / 3 |
Completeness | Has explicit 'Use when' and 'Trigger with' clauses, but the 'what' portion is weak - it only says 'optimize performance' without explaining what specific actions or capabilities the skill provides. | 2 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms including 'cursor performance', 'cursor slow', 'cursor optimization', 'cursor memory', 'speed up cursor', and variations like 'cursor tuning'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The Cursor IDE focus provides some distinctiveness, but 'cursor' alone as a trigger is too generic and could conflict with other Cursor-related skills. The performance focus helps but isn't fully distinct. | 2 / 3 |
Total | 8 / 12 Passed |
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.