cursor-multi-repo

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-multi-repo

Manage work with multiple repositories in Cursor. Triggers on "cursor multi repo", "cursor multiple projects", "cursor monorepo", "cursor workspace". Use when working with cursor multi repo functionality. Trigger with phrases like "cursor multi repo", "cursor repo", "cursor".

45%

Overall

Validation — 81%

Implementation — 35%

Activation — 32%

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 structural outline but lacks the concrete, executable guidance needed to be useful. The instructions are abstract descriptions rather than actionable steps, with no code examples, specific commands, or workspace file templates. Critical details are deferred to external files, leaving the main skill too thin to stand alone.

Suggestions

Add concrete code examples: include a sample .code-workspace file, example .cursorrules with inheritance patterns, and .cursorignore configurations

Replace abstract instructions with specific commands: e.g., 'Create workspace.code-workspace with: {"folders": [{"path": "./repo1"}, {"path": "./repo2"}]}'

Add validation steps: include how to verify cross-project context is working (e.g., test @-mention across repos, verify indexing status)

Remove or condense the Prerequisites section - Claude doesn't need to be told about 'understanding workspace concepts'

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary sections like 'Prerequisites' that explain concepts Claude already knows (workspace concepts, IDE support). The overview paragraph is somewhat padded.	2 / 3
Actionability	Instructions are vague and abstract with no concrete code, commands, or executable examples. Steps like 'Decide on multi-repo strategy' and 'Configure .cursorrules inheritance' provide no specific guidance on how to actually do these things.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack validation checkpoints and concrete details. There's no feedback loop for verifying the workspace is configured correctly, and steps are too high-level to be actionable.	2 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too sparse to serve as a useful overview. The skill offloads too much to external files without providing enough substance in the main document.	2 / 3
	Total	7 / 12 Passed

Activation

32%

This description suffers from vague capability statements and circular trigger guidance. The 'what' lacks concrete actions, and the 'when' essentially restates the title rather than describing actual user scenarios. The overly broad trigger term 'cursor' creates significant conflict risk with other Cursor-related skills.

Suggestions

Replace vague 'Manage work' with specific actions like 'Configure workspace settings for multiple repositories, switch between project contexts, set up cross-repo navigation'

Remove the overly generic 'cursor' trigger and add scenario-based triggers like 'when user needs to work across multiple codebases simultaneously' or 'when setting up a multi-project workspace'

Rewrite the 'Use when' clause to describe actual user scenarios instead of circular references, e.g., 'Use when the user wants to open multiple repositories in a single Cursor window or navigate between related projects'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Manage work with multiple repositories' without specifying concrete actions. It doesn't explain what managing actually entails (e.g., switching between repos, syncing, configuring workspaces).	1 / 3
Completeness	Has a weak 'what' (manage work with multiple repositories) and includes a 'Use when' clause, but the when clause is circular ('Use when working with cursor multi repo functionality') and doesn't provide meaningful guidance on actual use cases.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'cursor multi repo', 'cursor multiple projects', 'cursor monorepo', 'cursor workspace', but the final trigger 'cursor' alone is overly generic and would match too broadly. Missing natural variations users might say.	2 / 3
Distinctiveness Conflict Risk	The trigger term 'cursor' alone would conflict with any Cursor-related skill. The description is too generic about 'managing work' and could overlap with general Cursor skills, workspace management, or project organization skills.	1 / 3
	Total	6 / 12 Passed

Reviewed

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