CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

92

1.21x
Quality

93%

Does it follow best practices?

Impact

96%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is highly actionable and well-structured for progressive disclosure, with extensive executable examples and clear routing into real reference files. The main weakness is mild redundancy where two core rules are restated across sections.

Suggestions

Consolidate the "turbo run vs turbo" guidance so the rule is stated once and the anti-pattern section cross-references it instead of repeating the full WRONG/CORRECT blocks.

Merge the "Root Scripts Bypassing Turbo" anti-pattern with the "Package Tasks, Not Root Tasks" section to avoid restating the package-vs-root delegation rule twice.

Consider moving some of the longer anti-pattern code examples (e.g., globalDependencies, repetitive task configuration) into the configuration references to trim the SKILL.md body.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely free of concepts Claude already knows, but the "turbo run vs turbo" rule and the "package tasks not root tasks" rule are each restated across multiple sections (e.g., "Secondary Rule" then again under "Critical Anti-Patterns"), adding tokens that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready turbo.json, package.json, and CI YAML examples throughout, with WRONG/CORRECT pairs, concrete CLI flags, and decision trees that route to specific reference files, covering the common cases fully.

5 / 5

Workflow Clarity

Multi-step fixes are clearly sequenced (e.g., the prebuild remediation steps and the "check what the task actually produces" procedure) and decision trees give unambiguous routing, but there are no explicit validate-then-retry feedback loops; the skill is config guidance rather than destructive/batch execution, so this is a minor gap rather than a cap.

4 / 5

Progressive Disclosure

A concise overview sits at the top, decision trees signal one-level-deep references to real bundle files (all referenced paths exist under references/), and a Reference Index table maps each file to its purpose, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is comprehensive and well-structured, explicitly answering both what the skill covers and when to use it with a rich set of natural trigger terms and a distinct Turborepo-specific niche. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Names the domain ("Turborepo monorepo build system") and lists multiple concrete capability areas (turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, boundaries) plus concrete user actions (configures tasks, creates packages, sets up monorepo, shares code, runs changed/affected packages, debugs cache), giving comprehensive coverage.

5 / 5

Completeness

Clearly answers both "what" (Turborepo monorepo build system guidance with an enumerated domain) and "when" via an explicit "Use when user: ..." clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms a user would say, including synonyms and file extensions: "turbo.json", "turbo CLI", "--filter", "--affected", "caching", "remote cache", "monorepo", "dependsOn", "CI optimization", "internal packages", and "boundaries".

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Turborepo-specific niche with distinct triggers (turbo.json, turbo CLI, --filter, --affected, dependsOn) and minimal overlap risk with other skills.

5 / 5

Total

20

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (952 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 24 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 35 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
vercel/turborepo
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.