Skip to content
Turborepo

Turborepo Skill

The official Turborepo skill from the vercel/turborepo repo: points an agent at the docs bundled inside the installed turbo package, so turbo.json, caching, filtering and CI changes follow the exact version in use.

GitHub Docs

Install

Install with the skills CLI

One command for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf and dozens of other agents. Needs Node.js; the skill is fetched straight from vercel/turborepo.

$ npx skills add vercel/turborepo --skill turborepo

Run it in a terminal. The CLI finds the agents installed on your machine, asks which ones to add the skill to, and whether to install it into the folder you ran it from or for all your projects.

Other ways to install

Copy the whole skill folder — SKILL.md and any scripts or references beside it — into ~/.claude/skills/turborepo/, where Claude Code picks it up in every project. Only git is needed.

tmp=$(mktemp -d) && \
  git clone --depth 1 --branch main https://github.com/vercel/turborepo.git "$tmp" && \
  mkdir -p ~/.claude/skills && \
  cp -R "$tmp"/skills/turborepo ~/.claude/skills/turborepo

No scripts or references next to it? Saving the SKILL.md alone as ~/.claude/skills/turborepo/SKILL.md works too.

Using another agent? Its personal skills folder
Codex
~/.agents/skills/
Cursor
~/.cursor/skills/
GitHub Copilot
~/.copilot/skills/
Gemini CLI
~/.gemini/skills/
Windsurf
~/.codeium/windsurf/skills/
OpenCode
~/.config/opencode/skills/

About

  • Reads the version-matched docs shipped in node_modules/turbo/docs
  • Starts from a task index and opens only the smallest relevant page
  • Resolves the package location for non-flat node_modules and workspace links
  • Checks the package manager and version constraints before installing turbo

The Turborepo skill lives in the main vercel/turborepo repository and is built around one idea: the complete Turborepo documentation now ships inside the installed turbo package, so an agent should read that instead of relying on training data or a skill full of copied guidance. The skill itself says not to rely on it for framework guidance; it is a pointer to the right source.

It triggers on the work monorepo maintainers actually do: editing turbo.json, task pipelines, local and Remote Cache behaviour, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure and CI workflows. The agent starts at node_modules/turbo/docs/README.md, a task index, picks the smallest relevant page and reads it before changing configuration, package scripts or CI.

Two practical details make it work across setups. When the package manager uses a non-flat node_modules layout or a workspace link, the agent resolves the real location first with node -p "require.resolve('turbo/package.json')" and reads the docs relative to it. When turbo is not installed at all, it inspects the repository's package manager and existing version constraints before adding it, then uses the docs of the version it installed rather than guidance for a different release.

The result is a short skill whose answers stay correct as Turborepo changes, because the documentation it reads is versioned with the code. It suits teams running JavaScript or TypeScript monorepos with Turborepo who want an agent to change pipeline or cache configuration safely. MIT-licensed, maintained by Vercel.

SKILL.md

The instructions your agent loads, as published by Vercel.

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:

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:

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.

Install
Featured

Deno's official foundational skill — project setup, package choices, configuration, and CLI commands done the current way.

Skill: Transformers.js

by Hugging Face

Run machine learning models directly in the browser or Node with Transformers.js — no inference server required.

Skill: AI SDK

by Vercel

New

Vercel's official skill for the AI SDK (the ai package): it makes the agent check the version-matched docs bundled in node_modules instead of memory, set up AI Gateway, list current model IDs and build agents with ToolLoopAgent.

Vercel's official skill for React component architecture — replace boolean prop proliferation with compound components, lifted state and explicit variants. Includes React 19 APIs.

Browse all skills →