turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 strong skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that it focuses heavily on trigger conditions rather than describing concrete actions the skill performs (e.g., 'configures pipelines', 'optimizes caching', 'troubleshoots build issues'). The description effectively carves out a distinct niche for Turborepo-specific guidance.
Suggestions
Add concrete action verbs describing what the skill does (e.g., 'Configures task pipelines, optimizes caching strategies, troubleshoots build issues') rather than just listing trigger concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Turborepo monorepo build system) and mentions several concepts like task pipelines, caching, remote cache, CI optimization, but doesn't list concrete actions the skill performs - it focuses more on trigger conditions than capabilities. | 2 / 3 |
Completeness | Clearly answers both what (Turborepo monorepo build system guidance) and when (explicit 'Use when user:' clause with multiple specific trigger scenarios like configures tasks, creates packages, sets up monorepo, debugs cache). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'turbo.json', 'turbo CLI', '--filter', '--affected', 'apps/packages directories', 'monorepo', 'cache', 'dependsOn' - these are exactly what users working with Turborepo would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Turborepo-specific terminology (turbo.json, dependsOn, --filter, --affected, remote cache) that clearly separates it from generic monorepo or build tools - unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, comprehensive Turborepo skill with excellent actionability through concrete code examples and good progressive disclosure via decision trees and reference links. The main weaknesses are some redundancy in explaining key rules (like 'turbo run' vs 'turbo') and missing validation checkpoints for complex workflows like debugging cache issues or setting up CI pipelines.
Suggestions
Add explicit validation steps for cache debugging workflow (e.g., '1. Run --summarize, 2. Check hash inputs, 3. If X then Y')
Consolidate the 'turbo run vs turbo' guidance into a single authoritative section rather than repeating it in multiple places
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of code examples and decision trees, but includes some redundancy (e.g., the 'turbo run vs turbo' rule is explained multiple times) and could be tightened in places like the anti-patterns section which repeats similar concepts. | 2 / 3 |
Actionability | Excellent actionability with fully executable JSON configurations, concrete CLI commands, and copy-paste ready examples throughout. Every anti-pattern shows both wrong and correct approaches with real code. | 3 / 3 |
Workflow Clarity | Decision trees provide good navigation for common scenarios, but the skill lacks explicit validation/verification steps for multi-step processes like setting up a monorepo or debugging cache issues. No feedback loops for error recovery are provided. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview content, well-organized decision trees for quick navigation, and a comprehensive reference index pointing to one-level-deep documentation files. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
87%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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (915 lines); consider splitting into references/ and linking | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.