turborepo

Guide for implementing Turborepo - a high-performance build system for JavaScript and TypeScript monorepos. Use when setting up monorepos, optimizing build performance, implementing task pipelines, configuring caching strategies, or orchestrating tasks across multiple packages.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/turborepo/SKILL.md

Quality

Content

53%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 but functions as a monolithic reference manual rather than a lean skill: verbose, inlining material that should live in separate reference files, and lacking validation feedback loops for destructive/batch operations.

Suggestions

Split exhaustive reference material (framework integration, CI/Docker templates, full pipeline property catalog, troubleshooting) into files under references/ and replace the inline blocks with one-level-deep links, keeping SKILL.md as a concise overview.

Trim conceptual padding ('Turborepo is a high-performance build system... written in Rust', restated 'When to Use' list) since the description already covers it and Claude knows the domain.

Add explicit validate/verify checkpoints and feedback loops around destructive and batch operations such as turbo prune --docker, --force rebuilds, and cache clearing.

Dimension	Reasoning	Score
Conciseness	A ~1200-line reference dump that restates concepts Claude already knows and inlines exhaustive configuration catalogs (every outputMode, every filter pattern, full CI/Docker YAML, per-framework blocks); noticeably verbose with multiple padded/redundant sections.	2 / 5
Actionability	Provides extensive copy-paste-ready commands and complete JSON/YAML/Dockerfile snippets covering the common cases (install, create-turbo, turbo.json, filtering, caching, CI, prune) — fully executable guidance.	5 / 5
Workflow Clarity	Sectioned progression exists but it is a reference catalog rather than a guided workflow, and destructive/batch operations (turbo prune --docker, rm -rf cache, --force) lack validation checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all reference material (API details, framework/CI examples, troubleshooting) is inlined into a single monolithic file with only external URLs, matching the 'content that belongs in separate files is inlined' anchor despite good header structure.	2 / 5
	Total	12 / 20 Passed

Description

92%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.

A strong, third-person description that states concrete capabilities and gives explicit, multi-trigger usage guidance for a well-scoped niche. The only gap is slightly thinner synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and lists five concrete actions — 'setting up monorepos, optimizing build performance, implementing task pipelines, configuring caching strategies, or orchestrating tasks' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (high-performance build system for JS/TS monorepos) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users say ('monorepos', 'build performance', 'task pipelines', 'caching', 'orchestrating tasks') but misses common synonyms and migration-related phrasings like Lerna/Nx.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Turborepo for JS/TS monorepos) with distinct triggers; minimal risk of firing for non-monorepo or non-JS/TS work.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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 (1202 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: einverne/dotfiles
Path: claude/skills/turborepo/SKILL.md
Commit: 7d18cf4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.