LabscoMCP early access ↗
REPO PACKAGEOFFICIAL

vercel turborepo

vercel · publisher30,654 GitHub starsMIT · Listed as freegithub.com/vercel/turborepo

LABSCO SUMMARY

Summary

vercel/turborepo ships exactly one skill, and it reads like a real reference for the turbo CLI rather than a marketing wrapper around the docs site.

The single skill triggers on turbo.json, dependsOn, the turbo CLI, --filter and --affected, remote caching, environment variables, internal packages, and monorepo boundaries — its own frontmatter lists it as relevant whenever someone is configuring tasks or pipelines, creating packages, setting up a monorepo, sharing code between apps, running only changed or affected packages, debugging a cache miss, or just already has an apps/ and packages/ directory layout. That's the whole surface: one skill, with a command file and a references/ folder of best-practice notes alongside it.

The readme itself never mentions the skill at all — no install section, no npx skills add line, nothing distinguishing this page from the standard open-source project readme (badges, a link to turborepo.dev, contributing guidelines, a security-disclosure address). Whatever brings a reader to this skill isn't the repository's own documentation; everything above comes from the skill file's own frontmatter, not from anything Vercel has written about it publicly.

READ MORE

Who this is for.

Anyone running, or about to run, a JavaScript or TypeScript monorepo with Turborepo who wants an agent that already knows the difference between a cache hit and a cache miss instead of guessing at turbo.json syntax. It has nothing to say about anything outside Turborepo itself, and there's only the one skill to install.