More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Turborepo and Nx Config Check

    1

    This skill finds those and the other monorepo cache mistakes below before your next build, and tells you how to fix each one.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Turborepo and Nx Config Check

    Turborepo and Nx Config Check

    Example session with this skill installed

    Check this project with turborepo-nx-config-check.

    • Read your context and instructions
    • Compiled the turborepo and nx

    $ python3 scripts/check_monorepo.py examples/risky
    BLOCK nx-platform/nx.json:8 M03 CACHE_TOKEN_IN_FILE
    "secretAccessKey": "<redacted>"
    Why: A remote cache credential is written in a committed file: TURBO_TOKEN, TURBO_REMOTE_CACHE_SIGNATURE_KEY, NX_CLOUD_ACCESS_TOKEN or NX_CLOUD_AUTH_TOKEN in a CI file, Dockerfile or package.json script, a --token value, or the AWS secretAccessKey of the Nx S3 cache. CI tokens usually can write, so anyone who can read the repository (or the image layers) can read the build cache and upload artifacts that CI and teammates then restore.
    Safer: Keep the token in the CI secret store (${{ secrets.TURBO_TOKEN }}, a masked CI variable) or pass it as a Docker build secret, and revoke the committed one now. For the S3 cache use an SSO profile or the CI's AWS role instead of keys in nx.json.

    BLOCK nx-platform/nx.json:21 M02 SIDE_EFFECT_TASK_CACHED
    BLOCK turbo-shop/.github/workflows/release.yml:8 M03 CACHE_TOKEN_IN_FILE
    BLOCK turbo-shop/turbo.json:15 M01 SECRET_FILE_IN_CACHE_OUTPUTS
    BLOCK turbo-shop/turbo.json:21 M02 SIDE_EFFECT_TASK_CACHED
    REVIEW nx-platform/nx.json:3 M17 NX_CLOUD_TOKEN_IN_NX_JSON
    REVIEW nx-platform/nx.json:4 M18 NX_BUCKET_CACHE_DEPRECATED
    REVIEW nx-platform/package.json:10 M18 NX_BUCKET_CACHE_DEPRECATED
    REVIEW turbo-legacy/turbo.json:3 M15 TURBO_1_PIPELINE
    REVIEW turbo-shop/.github/workflows/release.yml:10 M19 CACHE_TOKEN_IN_COMMENT
    REVIEW turbo-shop/apps/web/src/env.ts:4 M12 ENV_VAR_NOT_DECLARED
    REVIEW turbo-shop/apps/web/src/env.ts:5 M12 ENV_VAR_NOT_DECLARED
    REVIEW turbo-shop/turbo.json:4 M13 LOOSE_ENV_MODE
    REVIEW turbo-shop/turbo.json:6 M14 SELF_HOSTED_CACHE_NOT_SIGNED
    REVIEW turbo-shop/turbo.json:10 M11 BUILD_WITHOUT_OUTPUTS
    REVIEW turbo-shop/turbo.json:19 M16 INPUTS_WITHOUT_TURBO_DEFAULT

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 10 files, 9 with Turborepo or Nx content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    or NX_CLOUD_AUTH_TOKEN in a CI file, Dockerfile or package.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    "outputs": ["dist/**", ".env.production"] copies your production secrets into every cache artifact, and a deploy task without "cache": false can be replayed from cache instead of run: Turborepo prints the old logs and reports success while nothing was deployed. This skill finds those and the other monorepo cache mistakes below before your next build, and tells you how to fix each one.

    Your agent runs a scanner on turbo.json and turbo.jsonc, nx.json, project.json, package.json files that use turbo, nx or lerna (scripts, dependencies and nx targets), CI workflows and Dockerfiles that run turbo or nx, and the JavaScript and TypeScript code of a Turborepo workspace (build output skipped). It reads JSON with comments, knows the current defaults (Turborepo caches every task and runs in strict env mode; Nx caches only targets marked "cache": true), merges package turbo.json files with the root one above them, knows the variables Turborepo passes to every task and the framework prefixes it infers, tells read-only tasks such as lint:migrations or release:notes from real deploys, and treats CI secret references and commented placeholders as what they are. It never runs turbo, nx or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • M01: .env files and other secret files (.pem, .key, .npmrc, SSH keys) in task outputs, where every cache copy and remote cache upload then holds them
    • M02: deploy, publish, release and migrate tasks that can be served from cache (no "cache": false in Turborepo, "cache": true or cacheableOperations in Nx); read-only tasks such as lint:migrations, migrations:check or release:notes are not reported
    • M03: TURBO_TOKEN, Nx Cloud tokens, the remote cache signature key or the Nx S3 cache secret key written in active lines of CI files, Dockerfiles, package.json scripts or nx.json

    REVIEW

    • M11: build tasks in the root turbo.json without outputs
    • M12: environment variables the code reads (also inside template literals) that no turbo.json declares, one finding per variable
    • M13: loose environment mode
    • M14: a self-hosted Turborepo remote cache (remoteCache.apiUrl, TURBO_API) without signature verification; the Vercel Remote Cache set up as the Turborepo docs show is not reported
    • M15: the Turborepo 1.x pipeline key
    • M16: task inputs without $TURBO_DEFAULT$
    • M17: an Nx Cloud access token in nx.json
    • M18: the deprecated Nx S3, GCS, Azure and shared-fs caches (CVE-2025-36852)
    • M19: a real-looking cache token in a commented-out CI or Dockerfile line (placeholders such as your-token are fine)

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and official source for each rule
    • Risky and safe example repositories (a Turborepo 2 shop, a Turborepo 1.x app and an Nx platform), and the real report the scanner produces on the risky ones

    Limits It reads each file as written: tasks that Nx plugins infer, settings kept in the Nx Cloud or Vercel dashboards (token scopes, workspace access levels) and the remote cache Vercel turns on for its own builds are not seen. Environment variables are matched across all turbo.json files of the scan, not per task, env access through helper functions is not followed, build output in folders that no outputs glob, main field or known name points to is read like source, and a .env file caught only by a broad output glob such as ** is not reported. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Static check of config and code text. Tasks inferred by Nx plugins, dashboard settings and secret files caught only by broad output globs are not checked. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Software
    nx-cloudNode.js@turbo/codemod

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example repositories include clearly fake, inert tokens and keys (not-a-real-..., NOTREAL-...) for the scanner to find. Nothing in them is run.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads turbo.json, nx.json, package.json, CI files and code as text. It never runs a task or touches a remote cache.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    New in DevOps & Cloud