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".
80
77%
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
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with explicit trigger terms and a clear 'when' clause. Its main weakness is that the capabilities listed are more like topic areas than concrete actions, which slightly reduces specificity. Overall, it would perform well in skill selection among a large set of skills.
Suggestions
Rephrase topic areas as concrete actions, e.g., 'Configure multi-root workspaces, set up selective indexing, manage cross-project context' instead of listing them as noun phrases.
| 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 | Clearly answers both 'what' (work with multiple repositories in Cursor covering multi-root workspaces, monorepo patterns, selective indexing, cross-project context) and 'when' (explicit 'Triggers on' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'cursor multi repo', 'cursor multiple projects', 'cursor monorepo', 'cursor workspace', 'multi-root workspace'. These cover common variations a user would naturally say when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Cursor' + 'multi repo/monorepo/workspace' creates a clear niche that is unlikely to conflict with other skills. The trigger terms are specific enough to avoid false matches. | 3 / 3 |
Total | 11 / 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 clear organization. Its main strengths are the executable configurations (.cursorignore, workspace files, rule files) and the practical strategy comparisons with pros/cons. Weaknesses include some verbosity in peripheral sections, lack of validation/verification steps, and content length that could benefit from splitting into referenced sub-files.
Suggestions
Add validation steps: e.g., 'Verify indexing scope by searching @Codebase for a known symbol in an excluded package — it should not appear' after .cursorignore setup.
Move 'Selective Indexing Strategies', 'Performance Optimization', and 'Enterprise Considerations' into a separate ADVANCED.md or INDEXING.md file, keeping only brief summaries with links in the main skill.
| 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 some explanatory text could be tighter. However, most content earns its place. | 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 immediately usable. | 3 / 3 |
Workflow Clarity | The workspace creation steps are clearly sequenced, and the monorepo strategies are well-organized with pros/cons. However, there are no validation checkpoints — for example, no way to verify indexing is working correctly after setting up .cursorignore, or to confirm rules are being applied as expected. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, and includes external resource links at the bottom. However, at ~180 lines, some sections (like selective indexing strategies and performance optimization) could be split into separate reference files. The monorepo patterns and rules inheritance sections are quite detailed for an overview document. | 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
3e83543
- 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.