Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →asymmetric-al/turborepo
Turborepo monorepo build system guidance.
Passed 22 of 22 test cases with the skill, and 15 of 22 without it.
and 6 more in the full report
7 fixed15 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.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need our task inputs in 'apps/web' to invalidate cache when a shared configuration file at the repository root ('/shared-config.json') changes. A teammate wrote '"inputs": ["$TURBO_DEFAULT$", "../shared-config.json"]'. Is this path notation correct, and if not, how should it be written?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies relative path traversal using ../ outside the package as incorrect. | Passed | Passed |
| The task input uses $TURBO_ROOT$ to reference files at the repository root. | Missed | Passed |
The instructions your model reads when the skill loads.
Build system for JavaScript/TypeScript monorepos. Turborepo caches task outputs and runs tasks in parallel based on dependency graph.
Prefer package tasks over Root Tasks.
When creating tasks/scripts/pipelines, you MUST default to package tasks:
package.jsonturbo.jsonpackage.json only delegates via turbo run <task>DO NOT put task logic in root package.json when it can live in packages. This defeats Turborepo's parallelization.
// DO THIS: Scripts in each package
// apps/web/package.json
{ "scripts": { "build": "next build", "lint": "eslint .", "test": "vitest" } }
// apps/api/package.json
{ "scripts": { "build": "tsc", "lint": "eslint .", "test": "vitest" } }
// packages/ui/package.json
{ "scripts": { "build": "tsc", "lint": "eslint .", "test": "vitest" } }
// turbo.json - register tasks
{
"tasks": {
"build": { "dependsOn": ["^build"], "outputs": ["dist/**"] },
"lint": {},
"test": { "dependsOn": ["build"] }
}
}
test cases passed, vs 15 / 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.