Turborepo skill
Vercel's skill for Turborepo monorepos: turbo.json setup, caching, filters and CI, driven by the docs bundled in the installed package
- 31,227 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill itself holds only instructions: it runs nothing and points the agent to the docs
- The turbo run commands an agent executes on its advice run your project's scripts
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/turborepoDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill itself holds only instructions: it runs nothing and points the agent to the docs
- The turbo run commands an agent executes on its advice run your project's scripts
This is third-party code. Review the repository files before installing.
What it does
The skill teaches an agent to configure and repair Turborepo repositories without leaning on the model's possibly stale knowledge. It triggers on requests about turbo.json, task pipelines, caching and Remote Cache, filtering, environment variables, package boundaries, monorepo structure and CI. SKILL.md itself is short and sends the agent to documentation that ships inside the turbo package and matches the installed version. The starting point is node_modules/turbo/docs/README.md, a task index from which the agent picks the narrowest page it needs. If the package is not at the root of node_modules, node -p "require.resolve('turbo/package.json')" finds it. If turbo is not installed yet, the agent first inspects the package manager and version constraints, then installs the package and reads its docs. According to the Turborepo docs, the skill covers configuration best practices, monorepo patterns, anti-patterns and performance techniques.
Who it is for. For JavaScript and TypeScript developers who run a Turborepo monorepo and ask an agent to adjust the task pipeline, caching or CI.
Good fit when
- turbo.json needs a task that depends on neighboring packages building first, with correct outputs
- CI builds are slow and the agent should pick filters and set up Remote Cache
- Environment variables enter task hashes in surprising ways and you need to find why the cache misses
- One package grows into two and you need to tidy package boundaries and the monorepo layout
- The project's turbo version is older than typical examples and the agent needs docs for that exact release
Not a fit when
- The project does not use Turborepo: the skill knows nothing about Nx, Lerna or other build tools
- You need advice on a specific framework: SKILL.md itself says not to rely on it for framework guidance
- You want a one-off answer without installing turbo: docs come from the package, and without it the skill only explains how to install it
Example request
Add a test task to turbo.json that runs after dependent packages build, and set up the cache so CI environment variables do not break itLimitations
The skill is only a pointer to documentation, so its value depends on the installed turbo version: docs are read from node_modules. Remote Cache needs a separate caching service account. The npx skills add command is not in the repository README; the documentation page on working with AI gives it. The skill updates with the repository, while docs always come from the turbo version installed in the project. If a monorepo has several apps with different turbo versions, the agent first needs to determine which package it is working with.
How to disable. Delete the turborepo folder from the agent's skills directory, for example with npx skills remove turborepo. A managed block in AGENTS.md, if one appeared, is removed by hand: the agentGuidance option in turbo.json does not erase it.
FAQ
How do I install the Turborepo skill in Claude Code?
Run npx skills add vercel/turborepo. That is the command from the Turborepo docs page on working with AI, and the installer asks which agents to add the skill for.
Where does the skill get its Turborepo knowledge?
From the documentation inside the turbo package, with no trip to the internet. Pages live in node_modules/turbo/docs, match the installed version and work offline, so the agent does not apply settings from another release.
What does the agentGuidance option in turbo.json do?
When set to true, turbo that detects an AI agent maintains a separate marked block in the repository-root AGENTS.md. The block points the agent to the installed package's docs and leaves the rest of the file alone. It is worth committing the block together with your work.
How do I search the docs from a terminal?
With turbo docs and a query, for example turbo docs "package configurations". It prints links to pages for your turbo version.
Can several agents work on one repository?
Yes, through git worktree: each agent gets its own directory with shared history. Turborepo shares the local cache across worktrees, so a second agent hits the cache after the first one builds. With Remote Cache the effect extends across machines.
Discussion
No questions or reviews yet.
Related
Skillsprek skill for agents
prek skill
The prek skill teaches an agent to set up Git hooks with prek, a Rust replacement for pre-commit: config, shims, priorities, built-in hooks and monorepos
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
The official Grafana skill set: PromQL, Loki, Tempo, Alloy, k6, dashboards and alerting for Claude Code, Cursor and Codex
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
A Terraform skill for Claude Code, Codex, Antigravity and Gemini CLI: cuts hallucinations and keeps code on HashiCorp's official practices
Cloudflare's official agent skills: Workers, Durable Objects, wrangler, Pages, storage and an MCP server
README in short
The repository README is short: Turborepo is called the build system for coding agents, with the project website as the starting point. Links to contributing, the community and the security policy follow. Guidance for agents sits on the AI page of the docs and in SKILL.md itself.
README badge
Original SKILL.md
---
name: turborepo
description: Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
---
# Turborepo
The complete Turborepo documentation ships inside the installed `turbo` package. Do not rely on this skill for framework guidance. Always read the bundled docs, which match the installed version exactly.
Start with:
```text
node_modules/turbo/docs/README.md
```
Use that task index to choose the smallest relevant documentation page. Read it before changing Turborepo configuration, package scripts, or CI workflows.
If the package manager uses a non-flat `node_modules` layout or a workspace link, resolve the package location first:
```sh
node -p "require.resolve('turbo/package.json')"
```
Then read `docs/README.md` relative to the resolved package directory.
If `turbo` is not installed, inspect the repository's package manager and existing version constraints before adding it. After installation, use the bundled docs rather than guidance for a different release.