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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable shortcut reference with concrete JSON and step-by-step customization guidance, but it is held back by redundancy (a duplicate cheat sheet and editor-shortcut tables that mirror a reference file) and by orphaned reference files that are never linked from the body.

Suggestions

Link the existing reference files from the body — e.g. add 'See [references/customizing-keybindings.md] for cursor.* commands' and 'See [references/standard-editor-shortcuts.md] for the full editor list' — so the bundle is actually discoverable.

Remove the inline 'Essential Editor Shortcuts' tables (or the print-friendly cheat sheet) since they duplicate references/standard-editor-shortcuts.md and the AI-shortcut table, keeping the body as a concise overview that points into references/.

Add an explicit verification step to the customization workflow, e.g. 'After binding, press the new combination to confirm it triggers the intended command.'

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, useful reference tables, but the 'Cheat Sheet (Print-Friendly)' duplicates the AI-shortcut table and the 'Essential Editor Shortcuts' tables duplicate content already in references/standard-editor-shortcuts.md, so it could be tightened — matching the score-2 'mostly efficient but includes some unnecessary content' anchor rather than the lean score-3 anchor.	2 / 3
Actionability	It provides copy-paste-ready keybindings.json JSON blocks (with keys, commands, and when clauses), concrete numbered UI steps for customization, and specific Vim-conflict resolutions, matching the score-3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 'Via UI' customization flow is a clear numbered sequence with a conflict-check branch ('If conflict detected, choose to override or cancel'), but there is no explicit verify/test step to confirm the new binding works, so it sits at the score-2 'steps listed but validation gaps' anchor rather than score 3.	2 / 3
Progressive Disclosure	Four bundle files exist in references/ (customizing-keybindings.md, errors.md, examples.md, standard-editor-shortcuts.md) but the body links to none of them; instead the body inlines a Customizing section and Editor Shortcuts tables that duplicate those reference files, matching the score-2 'references present but not clearly signaled; content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 is well-formed: it states a clear Cursor-specific purpose, uses third person, and supplies explicit natural trigger terms covering both what and when. Its only weakness is that 'Master ... shortcuts' is more of a goal statement than a list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Cursor keyboard shortcuts') and two actions ('Master ... shortcuts and customize keybindings for AI features and editor commands'), but 'Master' is a goal rather than a concrete action and the action list is not comprehensive, matching the score-2 anchor rather than the multi-action score-3 anchor.	2 / 3
Completeness	It answers both 'what' (master shortcuts and customize keybindings for AI features and editor commands) and 'when' via the explicit 'Triggers on ...' trigger guidance, satisfying the score-3 anchor and the rule that explicit trigger guidance keeps completeness uncapped.	3 / 3
Trigger Term Quality	The 'Triggers on' clause lists a strong set of natural terms a user would actually say — 'cursor shortcuts', 'cursor keybindings', 'cursor keyboard', 'cursor hotkeys', 'cursor commands', plus concrete combos 'Cmd+K', 'Cmd+L', 'Cmd+I' — matching the score-3 anchor of good coverage.	3 / 3
Distinctiveness Conflict Risk	The Cursor-specific niche and distinctive triggers (Cmd+K/L/I, 'cursor keybindings') make it unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.