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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/cursor-pack/skills/cursor-multi-repo/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

A highly actionable, code-rich reference for Cursor multi-repo workflows with concrete commands and config examples. Its main weaknesses are repetitive content across sections and a failure to route detail into the existing reference files, leaving them orphaned.

Suggestions

Link the reference files from the body (e.g. 'See [monorepo-patterns.md](references/monorepo-patterns.md) for full rule examples') and move the duplicated detail there instead of inlining it.

Consolidate the repeated .cursorignore examples — 'Monorepo Patterns', 'Selective Indexing Strategies', and 'Performance Optimization' all cover the same exclusions; present them once and reference back.

Add a brief validation checkpoint for the config-heavy workflows (e.g. after writing .cursorignore, confirm `@Codebase` only returns the intended roots) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code/config blocks and assumes Claude's competence, but the 'Selective Indexing Strategies' and 'Performance Optimization' sections repeat .cursorignore patterns and tips already shown in 'Monorepo Patterns', so it could be tightened further.	2 / 3
Actionability	Provides copy-paste-ready commands (`cursor /path/to/monorepo`, `cursor mywork.code-workspace`), complete .code-workspace JSON, .cursorignore and .cursorrules YAML, and concrete file-structure trees — fully executable guidance.	3 / 3
Workflow Clarity	Workspace creation has a clear 1-2-3 sequence and 'Large Monorepo Tips' is a numbered list, but the skill is structured as a reference catalog rather than a guided multi-step workflow, with no validation checkpoints or feedback loops.	2 / 3
Progressive Disclosure	The body is well-sectioned into headers, but the five reference files in references/ (e.g. monorepo-patterns.md, errors.md) are never linked from the body and their content is duplicated inline, so references are present but not signaled and content that belongs in separate files is inline.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 description: it names a clear niche, lists concrete capability areas, and provides explicit trigger phrases a user would naturally say. The only weakness is the generic lead verb 'Work with' rather than enumerating concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and four capability areas ('multi-root workspaces, monorepo patterns, selective indexing, and cross-project context'), but the lead verb 'Work with' is generic rather than concrete actions like 'extract' or 'merge', so it falls short of the level-3 anchor.	2 / 3
Completeness	Explicitly answers both 'what' (the four capability areas) and 'when' via an explicit 'Triggers on ...' clause, matching the level-3 anchor for explicit triggers.	3 / 3
Trigger Term Quality	Lists natural phrases a user would actually say — 'cursor multi repo', 'cursor multiple projects', 'cursor monorepo', 'cursor workspace', 'multi-root workspace' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to Cursor multi-repo work with distinct, specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
Path: plugins/saas-packs/cursor-pack/skills/cursor-multi-repo/SKILL.md
Commit: c4eafaf

Reviewed: 1 day 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.