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 excellent trigger term coverage and clear distinctiveness. It explicitly states both what the skill does and when to use it. The main area for improvement is listing more specific concrete actions beyond 'install' and 'configure authentication' to fully describe the skill's capabilities.
Suggestions
Expand the capability list with more specific actions, e.g., 'download Cursor installer, configure license keys, set up SSO authentication, troubleshoot login issues' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor IDE) and two actions (install and configure authentication) with platform specifics (macOS, Linux, Windows), 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 platforms) and 'when' (explicit trigger terms listed with 'Triggers on' clause), satisfying both requirements. | 3 / 3 |
Trigger Term Quality | Explicitly lists six natural trigger terms including 'install cursor', 'setup cursor', 'cursor authentication', 'cursor login', 'cursor license', 'cursor download' — these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — Cursor IDE installation and authentication is a very specific niche unlikely to conflict with other skills. The trigger terms are all Cursor-specific. | 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 platform-specific commands and clear authentication steps. Its main weaknesses are verbosity (pricing tables, enterprise details, and migration nuances that inflate token cost without proportional value) and a monolithic structure that could benefit from splitting secondary content into referenced files. The troubleshooting table and post-install checklist are practical strengths.
Suggestions
Move the pricing table, enterprise considerations, and VS Code migration details into separate referenced files to reduce the main skill's token footprint and improve progressive disclosure.
Add explicit validation checkpoints after installation steps (e.g., 'Verify Cursor launches: run `cursor --version`') to strengthen the workflow with feedback loops.
Remove or drastically shorten the pricing table — this is volatile information that Claude can look up, and it wastes tokens on details users would verify at cursor.com/pricing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary detail like the full pricing table, enterprise considerations, and VS Code migration nuances that pad the content. The plan pricing and enterprise sections are information Claude could look up or that users would verify themselves. However, the installation commands and auth steps are reasonably tight. | 2 / 3 |
Actionability | Installation commands are concrete and copy-paste ready for all three platforms. The authentication steps are specific with numbered sequences, and troubleshooting provides concrete fixes. The settings file paths and manual VSIX installation steps are directly actionable. | 3 / 3 |
Workflow Clarity | The post-install checklist provides a good sequence, and the authentication flow is clearly numbered. However, there are no explicit validation checkpoints during installation (e.g., verify Cursor launches successfully before proceeding to auth) and no feedback loops for error recovery during the install process itself. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's monolithic — the VS Code migration details, enterprise considerations, and troubleshooting table could be split into separate referenced files. The Resources section links to external docs but no bundle files exist to offload detailed content. | 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
3a2d27d
- 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.