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 for the Cursor keyboard shortcuts niche. The explicit 'Triggers on' clause with specific shortcut names is a strength. The main weakness is that the capability description could be more specific about what concrete actions the skill enables beyond the general 'master shortcuts and customize keybindings'.
Suggestions
Add more specific concrete actions, e.g., 'List default keybindings, customize shortcut mappings, troubleshoot conflicting bindings, explain AI-specific shortcuts like Cmd+K inline edit and Cmd+L chat.'
| 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 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 product-specific shortcut names (Cmd+K, Cmd+L, Cmd+I). Unlikely to conflict with general coding or 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 reference skill with strong actionability through concrete keybinding examples and clear customization workflows. 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 the standard editor shortcuts and removing the cheat sheet/enterprise sections would significantly improve token efficiency.
Suggestions
Remove or move the 'Essential Editor Shortcuts' section to a separate reference file — Claude already knows standard VS Code keybindings, and only Cursor-specific AI shortcuts add value.
Remove the ASCII cheat sheet section as it duplicates the AI Feature Shortcuts table above and wastes tokens.
Remove or significantly trim the Enterprise Considerations section — the points are generic and not actionable for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables, but includes some unnecessary sections like the ASCII cheat sheet (duplicates the tables above), Enterprise Considerations (generic/obvious), and the Resources section with external links. The standard editor shortcuts section is also largely redundant since Claude already knows VS Code shortcuts. | 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 (steps 1-5) with a conflict detection checkpoint at step 5. For a reference/lookup skill like keyboard shortcuts, the single-task nature means the clear table organization and step-by-step customization instructions are sufficient. No destructive operations require feedback loops. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's monolithic — the standard editor shortcuts and cheat sheet could be in separate reference files. For a skill this long (~150 lines of content), splitting the VS Code standard shortcuts and the cheat sheet into separate files would improve token efficiency. | 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
70e9fa4
- 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.