cursor-multi-repo

Work with multiple repositories in Cursor: multi-root workspaces, monorepo patterns, selective indexing, and cross-project context. Triggers on "cursor multi repo", "cursor multiple projects", "cursor monorepo", "cursor workspace", "multi-root workspace".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Concise, highly actionable content with clear sequences and concrete examples. The main weakness is progressive disclosure: bundle reference files exist but are never referenced from the body, and substantial inline content duplicates them rather than being split out.

Suggestions

Link the existing reference files from the body (e.g., add a '## References' section pointing to references/multi-root-workspace.md, references/monorepo-patterns.md, references/indexing-strategy.md, references/errors.md, references/examples.md) so the bundle is discoverable and one level deep.

Move the duplicated inline detail (workspace JSON, monorepo pattern trees, .cursorignore strategies) into the corresponding reference files and keep SKILL.md as a concise overview that points to them.

Add a short error-handling/validation pointer (e.g., 'If indexing is slow or a root is missing, see references/errors.md') to give the configuration workflows an explicit feedback path.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward — workspace JSON, .cursorignore blocks, and rules YAML carry the content with minimal prose explaining concepts Claude already knows; nearly every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready, executable guidance throughout: `cursor /path/to/monorepo`, `cursor mywork.code-workspace`, concrete .cursorignore and .code-workspace examples, and rule files with real syntax.	3 / 3
Workflow Clarity	Multi-step sequences are clearly numbered (e.g., the 3-step workspace creation) with pros/cons and strategy comparisons; the operations are configuration rather than destructive/batch work, so no validation checkpoint cap applies.	3 / 3
Progressive Disclosure	The body is a ~240-line monolith with well-organized sections, but none of the five provided reference files (errors.md, examples.md, indexing-strategy.md, monorepo-patterns.md, multi-root-workspace.md) are linked or signaled from the body, and inline content overlaps those files — matching the anchor where content that should be separate is inline and references are present but not clearly signaled.	2 / 3
	Total	11 / 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.

A strong, third-person description that states concrete capabilities and gives explicit, natural trigger phrases covering both what and when. No vague fluff or over-claims; concise for its scope.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "multi-root workspaces, monorepo patterns, selective indexing, and cross-project context" — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (working with multiple repos across four named areas) and when ("Triggers on ..."), satisfying the explicit-trigger requirement for full completeness.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually type ("cursor multi repo", "cursor multiple projects", "cursor monorepo", "cursor workspace", "multi-root workspace"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Cursor-specific multi-repo niche with dedicated trigger terms is clearly distinguishable and unlikely to fire for unrelated 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.