cursor-install-auth

Install Cursor IDE and configure authentication across macOS, Linux, and Windows. Triggers on "install cursor", "setup cursor", "cursor authentication", "cursor login", "cursor license", "cursor download".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 highly actionable with concrete, copy-paste-ready commands and good sectioning, but it is held back by implicit validation checkpoints and a failure to use the existing reference bundle, instead inlining content that belongs in references/.

Suggestions

Add explicit validation checkpoints to the install and sign-in workflows (e.g. run `cursor --version` after install; confirm the plan appears at cursor.com/settings after sign-in) with a fix-and-retry loop for failures.

Replace the inline Troubleshooting and Examples content with links to the existing references/errors.md and references/examples.md, or move the inline tables into those files to achieve one-level-deep progressive disclosure.

Trim the Plan/pricing table and incidental prose ('recommended for developers', 'First launch may require') to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, tables, and checklists and no padding about what an IDE is, but the full Plan/pricing table and minor prose ('GitHub (recommended for developers)', 'First launch may require') could be trimmed, matching anchor 2 rather than the lean anchor 3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (brew install --cask cursor, curl -fSL ... -o cursor.AppImage, sudo dpkg -i cursor.deb), exact settings paths, and precise keybindings (Cmd+Shift+P), matching the anchor-3 example.	3 / 3
Workflow Clarity	Steps are clearly listed (numbered sign-in flow, post-install checklist), but validation checkpoints are only implicit and there is no error-recovery feedback loop for the install/auth process, matching anchor 2 rather than the explicit-validation anchor 3.	2 / 3
Progressive Disclosure	The body is well-sectioned but inlines content (e.g. the Troubleshooting table) that duplicates references/errors.md without ever linking to the provided reference files, so references are present but not clearly signaled, matching anchor 2.	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 strong: it states concrete actions, provides six natural trigger phrases, and explicitly answers both what and when in third person. Its only weakness is that the action list is somewhat narrow rather than comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('Install Cursor IDE and configure authentication') with concrete actions across three platforms, but lists only two actions rather than a comprehensive set, matching anchor 2 rather than the multi-action anchor 3.	2 / 3
Completeness	Explicitly states what it does ('Install Cursor IDE and configure authentication across macOS, Linux, and Windows') and when to use it via the explicit 'Triggers on' clause, satisfying the what-AND-when anchor 3 rather than being capped at 2.	3 / 3
Trigger Term Quality	Includes six natural phrases a user would actually say ('install cursor', 'setup cursor', 'cursor authentication', 'cursor login', 'cursor license', 'cursor download'), giving good coverage and matching the anchor-3 example.	3 / 3
Distinctiveness Conflict Risk	The Cursor-specific scope and triggers ('cursor login', 'cursor license') form a clear niche unlikely to overlap with other skills, matching the distinct-triggers anchor 3.	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.