Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill turborepo-caching82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
turbo.json pipeline setup
Schema declaration
100%
100%
Global env file deps
0%
100%
Global env vars
100%
100%
Build upstream dep
100%
100%
Build output patterns
100%
100%
Cache exclusion pattern
100%
100%
Test local-only dep
100%
100%
Coverage caching
100%
100%
Dev no-cache
100%
100%
Dev persistent flag
100%
100%
Clean no-cache
100%
100%
Workspace globs
100%
100%
Private root
100%
100%
Package manager field
100%
100%
Without context: $0.2852 · 8m 13s · 15 turns · 113 in / 3,728 out tokens
With context: $0.6755 · 10m 56s · 27 turns · 495 in / 7,653 out tokens
CI remote caching workflow
TURBO_TOKEN from secrets
100%
100%
TURBO_TEAM from vars
100%
100%
Cache env at workflow level
100%
100%
Build filter changed packages
100%
100%
Test filter changed packages
100%
100%
Node version 20
100%
100%
npm ci install
100%
100%
Push trigger on main
100%
100%
Pull request trigger
100%
100%
npm cache enabled
100%
100%
Without context: $0.2014 · 5m 57s · 8 turns · 65 in / 3,398 out tokens
With context: $0.2951 · 6m 19s · 14 turns · 139 in / 2,720 out tokens
self-hosted cache server
GET artifact endpoint
100%
100%
PUT artifact endpoint
100%
100%
HEAD artifact endpoint
100%
100%
Team-based path isolation
100%
100%
PUT response format
100%
100%
remoteCache signature disabled
100%
100%
CLI flags for self-hosted cache
100%
100%
Express framework
100%
100%
teamId fallback
0%
100%
404 on missing artifact
100%
100%
Without context: $0.3051 · 11m 9s · 13 turns · 146 in / 4,938 out tokens
With context: $0.5014 · 10m 53s · 23 turns · 421 in / 5,264 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.