Vercel Agent Skills
vercel-labs/agent-skillsVercel's official 9-skill pack: React and Next.js performance rules, composition patterns, UI and writing review, React Native, deploy and cost audit.
Recommended
Broad access Depth 3/5
turborepo (Vercel) Claude skill
Vercel's tiny official Turborepo skill: it points the agent to the docs bundled in the installed turbo package instead of carrying its own guidance.
Our verdict Recommended
Very small but well-designed: it sends the agent to version-matched docs; install it only if you use Turborepo.
What turborepo (Vercel) does
The turborepo skill lives in the Turborepo repository, a Rust build system for JavaScript and TypeScript monorepos. The skill itself is about 1.2 KB. Its description makes the agent load it for turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure and CI workflows.
What it does is a single redirect. The skill says not to rely on it for framework guidance and instead to read the documentation that ships inside the installed turbo package, starting at node_modules/turbo/docs/README.md, a task index used to pick the smallest relevant page before changing configuration, package scripts or CI. If the package manager uses a non-flat node_modules layout or a workspace link, the agent resolves the package directory with a node require.resolve command first. If turbo is not installed, it should look at the package manager and existing version constraints before adding it, then use the bundled docs for that release.
The benefit is version matching: the agent reads documentation for the exact release in the project, not whatever it remembers from training. There are no references, scripts or tests in the skill folder, and the repository itself is a large, actively maintained monorepo with CI.
Good for
- Monorepos that use Turborepo, so the agent reads docs matching the installed version
- Agents that otherwise guess old turbo.json syntax
Not for
- Projects without Turborepo
- Offline or locked-down setups where turbo is not installed in node_modules
What's inside depth 1/5
A single 1.2 KB SKILL.md that redirects to docs bundled with the turbo package; no references, scripts or tests.
- Skills
- 1
- Reference docs
- 0
- Scripts
- 0
- Tests / evals
- 0
- Templates
- 0
- Avg SKILL.md
- 1.1 KB
Counted from the repository file tree. How we score depth.
Dependencies and costs
- The turbo package installed in the project (its bundled docs are the real content)
- Telemetry: none found in the skill
Security review
Review before installingThe installable skill is a single SKILL.md that points the agent at documentation shipped inside the installed turbo package and does not fetch anything itself. The repository around it is the full Turborepo source, which was mostly not available for review and includes a few binary test fixtures.
Worth knowing
- Relies on a CLI or package we could not reviewThe skill is a stub that tells the agent to read docs bundled in the installed turbo npm package (node_modules/turbo/docs/README.md) and to run node -p require.resolve to find it; those docs are not in the reviewed files.skills/turborepo/SKILL.md:14
- Contains compiled binariesThe repository contains three binary test fixtures (name-traversal.tar, windows-unsafe.tar, yarn-berry install-state.gz) that we could not read; they belong to the Turborepo source tests, not to the skill.crates/turborepo-cache/fixtures/name-traversal.tar
What we checked
The repository (6175 files) on Oct 29, 2026. Not a full review: 5989 of 6175 files were not downloaded (large repository; we reviewed the skill folders); it contains compiled binaries or archives we cannot read; it relies on code outside the repository: Turborepo docs bundled in the turbo npm package that the skill tells the agent to read; Three binary fixtures: crates/turborepo-cache/fixtures/name-traversal.tar, windows-unsafe.tar and lockfile-tests/fixtures/yarn-berry-resolution/.yarn/install-state.gz; The rest of the Turborepo monorepo (about 6,000 readable Rust, TypeScript and config files are not in the local copy).
NVIDIA SkillSpector static scan: 0 pattern hits. SkillSpector reported no hits. The skill file itself is a short Markdown stub with no commands beyond a node require.resolve lookup.
A review, not a certification. Skills change after we check them — read the files before installing.
License
MIT — commercial use allowed.
Can it run unattended?
Not really. It is a short documentation pointer, not a workflow.
Alternatives to turborepo (Vercel)
Nx AI Agent Skills
nrwl/nx-ai-agents-configOfficial skills, subagents and commands from the Nx team for working in Nx monorepos, including Nx Cloud CI monitoring and self-healing fixes.
Recommended
Broad access Depth 2/5
Vercel AI SDK skills
vercel/aiThe AI SDK repo's skills: one public ai-sdk skill for building with the SDK plus about a dozen maintainer-only skills for the monorepo.
With caveats
Check first Depth 2/5
FAQ
What is the Turborepo skill?
It is an official, very short agent skill in the Turborepo repo. It tells the agent to read the documentation bundled inside the installed turbo package whenever it touches turbo.json, pipelines, caching or CI.
How do I install the Turborepo skill?
It is listed on skills.sh, so npx skills add vercel/turborepo should install it. The skill depends on turbo being installed in the project, because the docs it reads live in node_modules/turbo/docs.
Is the Turborepo skill safe?
Yes as far as we could tell: it is a short markdown file with one local node command to find the package path, and no downloads or scripts.
Turborepo skill vs vercel-labs agent-skills: which one?
The Turborepo skill is a single-purpose pointer for monorepo build configuration. Vercel's agent-skills collection covers broader front-end topics such as React and web design guidelines, so they complement each other.
Sources: GitHub repository (stars, license, file tree, last push Oct 29, 2026); install counts from skills.sh via Best Skills (CC BY 4.0). Review based on the README and SKILL.md files as published.