Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →turborepo
Build system for JavaScript/TypeScript monorepos. Turborepo caches task outputs and runs tasks in parallel based on dependency graph.
Passed 22 of 22 test cases with the skill, and 13 of 22 without it.
and 10 more in the full report
9 fixed13 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/1/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our app's task definition inside turbo.json, we want our build task to depend on a root configuration file `shared-config.json`. A developer added `../shared-config.json` to the task's `inputs` array. Is this correct, and if not, how should it be configured?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies relative directory traversal using ../ in task inputs as incorrect | Passed | Passed |
| Uses $TURBO_ROOT$/shared-config.json to reference the root configuration file in task inputs | Missed | Passed |
The instructions your model reads when the skill loads.
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.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.