cursor-team-setup
Set up Cursor for teams: plan selection, member management, shared rules, admin dashboard, and onboarding. Triggers on "cursor team", "cursor organization", "cursor business", "cursor enterprise setup", "cursor admin".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that concisely lists specific capabilities (plan selection, member management, shared rules, admin dashboard, onboarding) and provides explicit trigger terms. It uses third person voice appropriately and clearly carves out a distinct niche around Cursor team administration. The description is well-structured and would allow Claude to confidently select this skill when relevant.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: plan selection, member management, shared rules, admin dashboard, and onboarding. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (set up Cursor for teams with specific capabilities listed) and 'when' (explicit triggers listed with the 'Triggers on' clause serving as the equivalent of 'Use when'). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'cursor team', 'cursor organization', 'cursor business', 'cursor enterprise setup', 'cursor admin'. These cover common variations of how users would phrase team/org setup requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses specifically on Cursor team/organization setup and administration, which is a clear niche unlikely to conflict with other skills. The trigger terms are specific to this domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized administrative setup guide with clear workflows and useful checklists, but it's somewhat verbose for a skill file — including marketing-style plan comparisons, adoption metrics, and buddy system advice that don't directly help Claude execute tasks. The actionability is moderate since most steps are UI navigation rather than executable commands, which is inherent to the domain but could be improved with concrete configuration examples.
Suggestions
Move the detailed plan comparison table and enterprise considerations into a separate reference file (e.g., PLANS.md) and link to it, keeping only the decision-relevant differences in the main skill.
Add concrete examples of rule file contents (e.g., a sample project.mdc with frontmatter) and SSO configuration snippets to increase actionability.
Remove or significantly trim the buddy system section and adoption indicators — these are organizational advice rather than actionable instructions Claude can execute.
Cut explanatory text like 'Privacy Mode guarantees' bullet points that describe product features rather than instruct Claude on what to do.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some information Claude would already know or that is unnecessarily verbose, such as the detailed plan comparison table with pricing, the buddy system section, and adoption indicators. Some sections like 'Privacy Mode guarantees' explain concepts that are more marketing than actionable guidance. | 2 / 3 |
Actionability | The skill provides structured steps and checklists but lacks truly executable commands or code. Most guidance is navigational ('Go to settings > click X') rather than programmatic. The shared configuration section with file structures is helpful but the content is more descriptive than executable — there are no actual rule file contents or SSO configuration examples. | 2 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced (Steps 1-5) with logical progression from organization creation through privacy enforcement and model configuration. The onboarding checklist provides explicit verification checkpoints (e.g., 'Verify Privacy Mode is ON', 'Verify rules loaded'). The workflow is well-structured for a primarily administrative/setup task. | 3 / 3 |
Progressive Disclosure | The content is organized into clear sections with good headers, and external resource links are provided at the end. However, the document is quite long (~150 lines of substantive content) and could benefit from splitting detailed sections like the onboarding checklist, plan comparison, and enterprise considerations into separate referenced files rather than inlining everything. | 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
70e9fa4
- 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.