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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 content is highly actionable with concrete UI paths and commands, but it is held back by inline reference material and a failure to use the available bundle files for progressive disclosure, plus missing feedback loops on riskier admin operations.

Suggestions

Reference the existing bundle files (e.g., link member-management.md and team-configuration.md from the relevant sections) and move detailed reference material like the plan comparison table and onboarding checklist into them, keeping SKILL.md as a concise overview.

Add explicit validation feedback loops for riskier admin operations (member removal, model restriction, privacy enforcement) — e.g., verify seat count changed, confirm restricted models are disabled in a test user's client.

Tighten the inline ASCII dashboard diagram and plan table, or move them to references/team-plans-overview.md, to reduce token load in the main skill body.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows and stays task-focused, but it inlines substantial reference material (full plan table, dashboard ASCII art, onboarding checklist) that could be tightened or offloaded rather than every token earning its place.	2 / 3
Actionability	Provides concrete, executable guidance — UI paths like 'Admin Dashboard > Privacy > Enable "Enforce Privacy Mode"', commands like `cursor /path/to/project`, shortcuts `Cmd+L`/`Cmd+K`/`Cmd+I`, and concrete `.cursor/rules/` file paths — rather than abstract direction.	3 / 3
Workflow Clarity	The team setup workflow is clearly sequenced into Steps 1-5 with some checkpoints (Privacy Mode enforcement verification, onboarding verify steps), but riskier admin/batch operations like member removal and model restriction lack explicit validate-fix-retry feedback loops.	2 / 3
Progressive Disclosure	The body is well-organized into sections, but six bundle files exist in references/ (member-management, team-configuration, team-workflows, errors, examples, team-plans-overview) and none are referenced or signaled in the body, while their subject matter is delivered inline instead of via one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is strong across all dimensions: it names concrete capabilities, provides natural trigger terms, explicitly covers both what and when, and occupies a distinct niche unlikely to cause skill conflicts.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'plan selection, member management, shared rules, admin dashboard, and onboarding' — rather than vague language, matching the anchor for naming several specific capabilities.	3 / 3
Completeness	Explicitly answers both what it does ('Set up Cursor for teams...') and when to use it ('Triggers on...'), with explicit trigger guidance rather than implied timing.	3 / 3
Trigger Term Quality	Includes natural phrases users would say — 'cursor team', 'cursor organization', 'cursor business', 'cursor enterprise setup', 'cursor admin' — giving good coverage of likely user phrasings.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Cursor team/organization admin) with distinct, product-specific triggers that are unlikely to conflict with generic skills.	3 / 3
	Total	12 / 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.