cursor-keybindings
Master Cursor keyboard shortcuts and customize keybindings for AI features and editor commands. Triggers on "cursor shortcuts", "cursor keybindings", "cursor keyboard", "cursor hotkeys", "cursor commands", "Cmd+K", "Cmd+L", "Cmd+I".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 skill description with excellent trigger term coverage and clear distinctiveness. The main weakness is that the 'what' portion could be more specific about the concrete actions the skill enables (e.g., listing, customizing, resetting shortcuts). The explicit trigger terms compensate well for completeness.
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'List default shortcuts, customize keybindings, resolve shortcut conflicts, configure AI-specific hotkeys for Cursor editor.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Cursor keyboard shortcuts and keybindings) and mentions some actions ('customize keybindings for AI features and editor commands'), but doesn't list multiple specific concrete actions like 'rebind shortcuts', 'view default keybindings', 'configure AI command triggers'. | 2 / 3 |
Completeness | Clearly answers 'what' (master Cursor keyboard shortcuts and customize keybindings for AI features and editor commands) and 'when' via explicit trigger terms ('Triggers on...'). The trigger clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms users would actually say: 'cursor shortcuts', 'cursor keybindings', 'cursor keyboard', 'cursor hotkeys', 'cursor commands', and specific shortcut names like 'Cmd+K', 'Cmd+L', 'Cmd+I'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Cursor editor keyboard shortcuts and keybindings, with distinct trigger terms including specific shortcut names (Cmd+K, Cmd+L, Cmd+I). Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 well-structured reference skill with strong actionability through concrete keybinding tables and executable JSON examples. Its main weakness is including too much content that Claude already knows (standard VS Code shortcuts) and redundant sections (ASCII cheat sheet duplicating the tables). Trimming non-Cursor-specific content and the duplicate cheat sheet would significantly improve token efficiency.
Suggestions
Remove or drastically reduce the 'Essential Editor Shortcuts' section — these are standard VS Code shortcuts Claude already knows, and they consume significant tokens without adding Cursor-specific value.
Remove the ASCII cheat sheet section as it duplicates the AI Feature Shortcuts tables above.
Move Vim compatibility details and standard editor shortcuts to separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables, but includes some unnecessary sections like 'Enterprise Considerations' (vague and not actionable), the ASCII cheat sheet (duplicates the tables above), and standard VS Code shortcuts that Claude already knows. The essential editor shortcuts section adds significant bulk for information that isn't Cursor-specific. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready JSON examples for keybinding customization, specific key combinations in clear tables, and step-by-step UI instructions for customizing keybindings. The Vim compatibility section includes executable JSON with proper 'when' clauses. | 3 / 3 |
Workflow Clarity | The customization workflow via UI is clearly sequenced (5 steps including conflict detection). The JSON customization path is also clear with specific commands to open the file. For a reference/shortcut skill, the workflows present are well-structured and the single multi-step process includes a validation checkpoint (conflict detection in step 5). | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a monolithic file that could benefit from splitting the standard VS Code shortcuts and Vim compatibility into separate referenced files. The Resources section links to external docs but the inline content is quite long for a single SKILL.md. | 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
3a2d27d
- 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.