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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-install-auth/SKILL.mdQuality
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 explicit trigger terms and a clear scope focused on Cursor IDE installation and authentication. The 'what' could be slightly more detailed with additional concrete actions (e.g., license activation, troubleshooting), but the trigger terms and distinctiveness are strong. Overall, it effectively communicates when and why Claude should select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor IDE) and two actions (install and configure authentication) across specific platforms, but doesn't list more granular actions like downloading, license activation, or troubleshooting steps. | 2 / 3 |
Completeness | Clearly answers 'what' (install Cursor IDE and configure authentication across macOS, Linux, and Windows) and 'when' (explicit trigger terms listed with 'Triggers on' clause serving as the 'Use when' equivalent). | 3 / 3 |
Trigger Term Quality | Explicitly lists six natural trigger terms including common variations like 'install cursor', 'setup cursor', 'cursor authentication', 'cursor login', 'cursor license', and 'cursor download' — these are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Cursor IDE installation and authentication is unlikely to conflict with other skills. The trigger terms are all Cursor-specific and wouldn't overlap with general IDE or editor skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete commands and clear platform coverage. Its main weaknesses are verbosity — the pricing table, VS Code migration details, and enterprise section inflate the token cost without proportional value — and the lack of integrated validation checkpoints in the install-to-auth workflow. Splitting secondary content into referenced files would significantly improve both conciseness and progressive disclosure.
Suggestions
Move the pricing table, VS Code migration details, and enterprise considerations into separate referenced files (e.g., PRICING.md, MIGRATION.md, ENTERPRISE.md) to keep the main skill lean.
Integrate validation steps directly into the workflow — e.g., after installation, verify with `cursor --version`; after sign-in, confirm plan status at cursor.com/settings before proceeding.
Remove the pricing table entirely or reduce to a one-liner ('See cursor.com/pricing for current plans') since pricing is time-sensitive and Claude can direct users to the source.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary detail like the full pricing table (which changes over time and Claude doesn't need memorized), the VS Code migration section is quite lengthy, and the enterprise considerations section adds bulk for a niche use case. However, most sections are reasonably efficient with tables and checklists. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready commands for all platforms (brew, curl, dpkg), specific file paths, exact menu navigation steps for authentication, and actionable troubleshooting fixes. The checklist and VSIX installation steps are fully executable. | 3 / 3 |
Workflow Clarity | The authentication flow is clearly sequenced (steps 1-6), and the post-install checklist provides a good overview. However, there are no explicit validation checkpoints — for example, no step to verify the installation succeeded before proceeding to authentication, and no feedback loop if sign-in fails (troubleshooting is separate, not integrated into the workflow). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, and links to external resources at the bottom. However, the VS Code migration details, enterprise considerations, and full pricing table could be split into separate reference files rather than inlined, making the main skill leaner. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.