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".
73
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-multi-repo/SKILL.mdQuality
Discovery
72%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 identifies a clear niche (multi-repo work in Cursor) with good trigger terms, but falls short on specificity of concrete actions and lacks an explicit 'Use when...' clause. The listed topics (multi-root workspaces, selective indexing, cross-project context) are more like feature areas than actionable capabilities.
Suggestions
Rewrite the capability list with concrete actions, e.g., 'Configure multi-root workspaces, set up selective indexing for large monorepos, share context across projects'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs help managing multiple repositories or projects within a single Cursor workspace, or asks about monorepo setup and cross-project navigation.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (multiple repositories in Cursor) and lists some actions/topics like 'multi-root workspaces, monorepo patterns, selective indexing, and cross-project context', but these read more like topic areas than concrete actions (e.g., 'configure multi-root workspaces' or 'set up selective indexing'). | 2 / 3 |
Completeness | The 'what' is partially addressed (work with multiple repositories, monorepo patterns, etc.) and trigger terms are listed, but there is no explicit 'Use when...' clause that describes the situations or user needs that should activate this skill. The triggers are listed but not framed as guidance for when to use the skill. | 2 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms that users would actually say: 'cursor multi repo', 'cursor multiple projects', 'cursor monorepo', 'cursor workspace', 'multi-root workspace'. These cover common variations of how users would phrase requests about this topic. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to a specific niche: multi-repo workflows in Cursor specifically. The trigger terms are distinct and unlikely to conflict with other skills, as they combine 'cursor' with multi-repo/workspace concepts. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill covering multi-repo workflows in Cursor with concrete examples and practical patterns. Its main weaknesses are the lack of validation/verification steps (how to confirm indexing scope, rule application) and the monolithic structure that could benefit from splitting detailed strategies into separate files. Some content is slightly redundant between sections (e.g., .cursorignore patterns appear in multiple places).
Suggestions
Add validation checkpoints: e.g., 'Verify indexing scope by searching @Codebase for a known symbol in an excluded package — it should not appear' or 'Check that rules are applied by asking Cursor to summarize active rules for a file.'
Consolidate the .cursorignore examples into a single reference section or separate file to reduce repetition between 'Hybrid: Focused + Selective .cursorignore', 'Selective Indexing Strategies', and 'Performance Optimization'.
Trim the Enterprise Considerations section — points like 'Cursor cannot index repos the user cannot read' and 'network mounts may be slow' are self-evident and don't add actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like 'Enterprise Considerations' with somewhat obvious points (filesystem permissions, network mounts being slow). The 'How Indexing Works with Multi-Root' bullet points and workspace creation steps are useful but could be tighter. Some sections like Performance Optimization repeat guidance already covered in Selective Indexing Strategies. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready examples throughout: workspace JSON files, .cursorignore configurations, CLI commands, rule file examples with proper YAML frontmatter, and specific @ reference syntax. The monorepo strategies include real file paths and practical gitignore patterns. | 3 / 3 |
Workflow Clarity | The workspace creation steps are clearly sequenced, and the three monorepo strategies are well-differentiated. However, there are no validation checkpoints — for example, no way to verify indexing is working correctly after setting up .cursorignore, no feedback loop for confirming rules are being applied, and no troubleshooting guidance if cross-project references fail. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a long monolithic document (~180 lines) with no references to supporting files. The selective indexing strategies, enterprise considerations, and rules inheritance sections could be split into separate reference files. The external resource links at the bottom are helpful but the skill itself could benefit from internal decomposition. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.