cursor-team-setup

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-team-setup

Configure set up Cursor for teams and organizations. Triggers on "cursor team", "cursor organization", "cursor business", "cursor enterprise setup". Use when working with cursor team setup functionality. Trigger with phrases like "cursor team setup", "cursor setup", "cursor".

48%

Overall

Validation — 81%

Implementation — 35%

Activation — 40%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Implementation

35%

This skill provides a high-level checklist for Cursor team setup but lacks the concrete, actionable guidance needed to be useful. The instructions read like a table of contents rather than executable steps, and critical details about how to actually perform each task are missing. The structure is reasonable but the content is too abstract to provide real value.

Suggestions

Replace abstract instructions with concrete steps - e.g., show the actual UI flow or API calls for inviting members, include a sample .cursorrules file for teams

Add validation checkpoints after critical steps - e.g., 'Verify: Each invited member should receive an email within 5 minutes. Check pending invites at cursor.com/settings/team/invites'

Include at least one concrete example inline rather than deferring entirely to examples.md - show a minimal team setup scenario with specific role assignments

Remove the Overview section and integrate any essential context directly into the instructions

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary framing ('This skill guides you through...') and the Overview section explains what the skill does rather than diving into actionable content. The prerequisites and output sections add some padding.	2 / 3
Actionability	Instructions are extremely vague with no concrete guidance - 'Configure team plan and billing' and 'Set up shared .cursorrules' provide no actual steps, commands, or examples. There's no executable content, just abstract task descriptions.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack any validation checkpoints or feedback loops. For a setup process involving billing and access control, there should be verification steps (e.g., 'Verify invites were received', 'Test member access').	2 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin - it defers to examples and error handling without providing enough substance in the skill itself. The external resources are just links without context.	2 / 3
	Total	7 / 12 Passed

Activation

40%

This description suffers from vague capability statements and overly broad trigger terms. While it attempts to define a niche (team/organization setup), the lack of specific actions and the inclusion of generic triggers like 'cursor' undermine its effectiveness for skill selection. The circular 'Use when' clause doesn't provide meaningful guidance.

Suggestions

Add specific concrete actions like 'manage team seats, configure SSO/SAML, set organization permissions, invite team members, manage billing for teams'

Remove the overly generic 'cursor' and 'cursor setup' triggers which would conflict with other Cursor skills; keep only team/organization-specific triggers

Rewrite the 'Use when' clause to be more specific: 'Use when users need to manage Cursor team accounts, organization settings, enterprise deployment, or multi-user licensing'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Configure set up' without listing concrete actions. It doesn't specify what configuration or setup actually involves (e.g., managing seats, setting permissions, configuring SSO).	1 / 3
Completeness	Has a weak 'what' (configure/set up Cursor for teams) and includes a 'Use when' clause, but the trigger guidance is circular ('Use when working with cursor team setup functionality') and doesn't add meaningful selection criteria beyond restating the title.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'cursor team', 'cursor organization', 'cursor business', 'cursor enterprise setup', but the final trigger 'cursor' is overly generic and would match any Cursor-related query. Missing natural variations like 'add team members', 'organization settings'.	2 / 3
Distinctiveness Conflict Risk	The team/organization/business/enterprise terms provide some distinction, but the generic 'cursor' and 'cursor setup' triggers would conflict with any other Cursor-related skills. Could easily overlap with general Cursor configuration or individual setup skills.	2 / 3
	Total	7 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.