cursor-keybindings
Manage master Cursor keyboard shortcuts and customize keybindings. Triggers on "cursor shortcuts", "cursor keybindings", "cursor keyboard", "cursor hotkeys", "cursor commands". Use when working with cursor keybindings functionality. Trigger with phrases like "cursor keybindings", "cursor keybindings", "cursor".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-keybindings71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately covers trigger terms and completeness with explicit 'Use when' guidance, but suffers from vague action verbs ('manage', 'customize') and contains redundant/sloppy phrasing ('cursor keybindings' repeated twice). The overly broad 'cursor' trigger term risks conflicts with other Cursor-related skills.
Suggestions
Replace vague verbs with specific actions: 'Add, remove, and modify keyboard shortcuts; resolve keybinding conflicts; export/import shortcut configurations'
Remove the redundant 'cursor keybindings' repetition and the overly broad 'cursor' trigger to reduce conflict risk with other Cursor skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor keyboard shortcuts/keybindings) and mentions two actions ('manage' and 'customize'), but lacks comprehensive concrete actions like 'add shortcuts', 'remove bindings', 'list conflicts', or 'export settings'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage master Cursor keyboard shortcuts and customize keybindings') and when ('Use when working with cursor keybindings functionality. Trigger with phrases like...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms users would say: 'cursor shortcuts', 'cursor keybindings', 'cursor keyboard', 'cursor hotkeys', 'cursor commands'. These are variations users would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to Cursor keybindings, but the generic trigger 'cursor' at the end could cause conflicts with other Cursor-related skills. The repeated 'cursor keybindings' in the trigger phrases suggests poor editing. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a basic framework for customizing Cursor keybindings but lacks the concrete, actionable content that would make it immediately useful. It relies heavily on external references without providing enough substance in the main skill file, and the instructions are too generic without specific shortcut examples or conflict resolution guidance.
Suggestions
Add a table or list of the most important Cursor-specific shortcuts (AI commands like Cmd+K, Cmd+L, etc.) with their default bindings
Include a concrete example of resolving a common keybinding conflict, such as Vim mode conflicts with Cursor AI shortcuts
Remove the 'Output' section which lists vague outcomes, and the 'Prerequisites' section explaining basic concepts Claude already knows
Add specific examples of keybindings.json entries for common customizations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary sections like 'Prerequisites' explaining modifier keys and 'Output' listing vague outcomes that don't add actionable value. The overview paragraph restates what the skill does rather than diving into useful content. | 2 / 3 |
Actionability | The instructions provide a basic step sequence but lack concrete examples of actual keybindings, specific commands to search for, or what conflicts look like. No executable code or specific shortcut examples are provided. | 2 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. Step 5 mentions 'resolve any conflicts shown' without explaining how to resolve them. No feedback loop for verifying the binding works correctly. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present but the main content is thin - it defers too much to external files without providing enough substance in the skill itself. The external resources section is appropriate. | 2 / 3 |
Total | 8 / 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 | |
- 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.