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".
58
68%
Does it follow best practices?
Impact
—
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 targets a clear niche (multi-repo workflows 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) would benefit from being framed as actionable capabilities rather than abstract topic areas.
Suggestions
Reframe topic areas as concrete actions, e.g., 'Configure multi-root workspaces, set up selective indexing for large monorepos, manage cross-project dependencies and context sharing.'
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 while trigger terms are listed, there is no explicit 'Use when...' clause that describes the situations or user needs that should activate this skill. The triggers are listed but framed as keyword matches rather than contextual guidance. | 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 good structural organization. Its main weaknesses are the lack of validation/verification steps (how to confirm indexing scope, rule inheritance behavior) and some content that could be trimmed or split into supporting files. The actionability is strong with executable configurations and commands throughout.
Suggestions
Add validation checkpoints: e.g., how to verify .cursorignore is working (check indexed file count), how to confirm rules are being applied (test with a prompt), and troubleshooting steps when cross-project references don't resolve.
Trim the 'Enterprise Considerations' section — points like 'Cursor cannot index repos the user cannot read' are obvious and don't add value for Claude.
Consider splitting detailed .cursorignore strategies and rules inheritance patterns into separate reference files to improve progressive disclosure and reduce the main file length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanations (e.g., 'Enterprise Considerations' section with obvious points like filesystem permissions, the pros/cons lists could be tighter). The 'Performance Optimization' section restates some earlier points. However, most content is practical and not overly verbose. | 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 guidance is specific and executable. | 3 / 3 |
Workflow Clarity | The workspace creation steps are clearly sequenced, and the selective indexing strategies provide clear progression. However, there are no validation checkpoints — for example, no way to verify indexing is working correctly, no steps to confirm .cursorignore is being respected, and no feedback loops for troubleshooting when cross-project references fail. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping, but it's a fairly long monolithic document with no references to supporting files. Some sections like 'Enterprise Considerations' and detailed indexing strategies could be split out. The external resource links at the end are helpful but the skill itself could benefit from better layering. | 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
8a9cd04
- 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.