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".
68
83%
Does it follow best practices?
Impact
—
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 for the Cursor keyboard shortcuts domain. The explicit 'Triggers on' clause with specific key combinations and natural language variations makes it easy for Claude to select appropriately. The main weakness is that the capability description could be more specific about what concrete actions the skill enables beyond 'master' and 'customize'.
Suggestions
Replace the vague 'Master' with specific concrete actions like 'List, customize, and troubleshoot Cursor keyboard shortcuts' to improve specificity.
| 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 hotkeys'. | 2 / 3 |
Completeness | Clearly answers 'what' (master Cursor keyboard shortcuts and customize keybindings for AI features and editor commands) and 'when' (explicit triggers listed with 'Triggers on' clause covering multiple natural phrases and specific shortcuts). | 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 key combos 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 product-specific key combinations. Unlikely to conflict with general coding skills or other editor 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 keybinding reference with strong actionability through concrete 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). The skill would benefit from trimming standard editor knowledge and splitting detailed subsections into separate files.
Suggestions
Remove or significantly trim the 'Essential Editor Shortcuts' section — these are standard VS Code shortcuts Claude already knows, and they dilute the Cursor-specific value.
Remove the ASCII cheat sheet section as it duplicates the AI Feature Shortcuts tables above without adding new information.
Move Vim compatibility details and enterprise considerations into separate referenced files to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables, but includes some unnecessary sections like the '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 is largely redundant knowledge. | 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. 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 with conflict handling). The JSON customization path is also clear with a specific command to open the file. For a reference/lookup skill like keybindings, the single-task workflows present are unambiguous and well-structured. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's monolithic — the standard editor shortcuts, Vim compatibility details, and enterprise considerations could be split into separate reference files. For a skill with no bundle files, everything is inline when some content would benefit from being referenced externally. | 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
c81cea4
- 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.