cursor-common-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-common-errorsExecute troubleshoot common Cursor IDE errors and issues. Triggers on "cursor error", "cursor not working", "cursor issue", "cursor problem", "fix cursor". Use when working with cursor common errors functionality. Trigger with phrases like "cursor common errors", "cursor errors", "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 is essentially a placeholder that provides no actionable troubleshooting guidance. It lists generic steps without any specific error messages, actual solutions, concrete commands, or real examples. A troubleshooting skill should contain specific error patterns and their fixes, not abstract instructions to 'check common solutions.'
Suggestions
Add specific error messages with their exact solutions (e.g., 'Error: Authentication failed' → specific fix steps with commands)
Include actual troubleshooting commands (e.g., paths to log files, cache clearing commands, config file locations)
Provide concrete examples of common errors inline rather than deferring everything to external files
Replace generic instructions with decision trees or specific diagnostic steps (e.g., 'Run `cursor --version` to check installation')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the prerequisites section (Claude knows what logs and network connectivity are) and generic instructions that don't add specific value. | 2 / 3 |
Actionability | The instructions are entirely vague and abstract ('Identify the error type', 'Check common solutions') with no concrete commands, specific error messages, actual solutions, or executable steps. It describes what to do rather than showing how. | 1 / 3 |
Workflow Clarity | The 6-step process is generic and lacks any specific validation checkpoints, actual troubleshooting commands, or concrete decision points. Steps like 'Try basic troubleshooting (restart, clear cache)' provide no actual commands or paths. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so thin that it's unclear what value those references provide. The structure exists but the overview itself lacks substance. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vagueness and circular language. While it correctly identifies the domain (Cursor IDE troubleshooting) and attempts to provide trigger terms, it fails to specify what concrete troubleshooting actions are performed or what types of errors it handles. The repetitive trigger terms and circular 'Use when' clause weaken its effectiveness for skill selection.
Suggestions
Replace vague 'troubleshoot common errors' with specific actions like 'Diagnose extension conflicts, fix workspace configuration issues, resolve indexing problems, clear cache corruption'
Expand trigger terms to include specific error scenarios users encounter: 'cursor crash', 'cursor slow', 'cursor won't index', 'cursor extension error', 'cursor settings reset'
Rewrite the 'Use when' clause to be informative rather than circular: 'Use when users report Cursor IDE malfunctions, startup failures, performance issues, or need help interpreting Cursor-specific error messages'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'troubleshoot common Cursor IDE errors and issues' without listing any concrete actions or specific error types. It doesn't explain what troubleshooting steps or fixes are actually performed. | 1 / 3 |
Completeness | Has a weak 'what' (troubleshoot errors) and attempts a 'when' clause with trigger phrases, but the 'Use when working with cursor common errors functionality' is circular and uninformative. The trigger guidance exists but is poorly articulated. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords users might say ('cursor error', 'cursor not working', 'fix cursor'), but the triggers are repetitive and miss common variations like 'cursor crash', 'cursor freeze', 'cursor won't start', or specific error messages. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on Cursor IDE specifically which provides some distinction, but 'cursor' alone as a trigger is problematic as it could conflict with mouse cursor-related skills. The generic 'errors and issues' language reduces distinctiveness. | 2 / 3 |
Total | 7 / 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.