Menu
Use when adding, removing, or renaming environment variables in the project. Ensures turbo.json stays in sync and naming conventions are followed.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when checking Vercel deployment status, investigating build failures, viewing build logs, listing environment variables, or managing the sg-tools and dck apps on Vercel.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Based on SOC occupation classification
| name | env-update |
| description | Use when adding, removing, or renaming environment variables in the project. Ensures turbo.json stays in sync and naming conventions are followed. |
turbo.json must stay in sync. Every env var used by any app must be declared in turbo.json under tasks.build.env. Turborepo uses this list to track build cache invalidation and Vercel will warn about missing entries.
NEXT_PUBLIC_ prefix means the variable is inlined into the client bundle at build time and visible to anyone. Only use it for values that are safe to expose publicly (e.g. brand slug, Sentry DSN, Turnstile site key). Never use it for API keys, secrets, or tokens. Do NOT add NEXT_PUBLIC_* vars to Vercel project settings - they are public, so they belong in each app's ``.env.production` in each app, not in Vercel's secret store.
Server-only variables (no NEXT_PUBLIC_ prefix) are only available in server components, server actions, route handlers, and next.config.ts. Use this for all secrets (API_URL, BREVO_API_KEY, PACMS_API_KEY, TURNSTILE_SECRET_KEY, SENTRY_AUTH_TOKEN). These must be set in Vercel project settings.
turbo.json tasks.build.env array (keep alphabetical order).env.local in each app that uses it (gitignored) and to Vercel project settings (use the prod-vercel skill in PACMS)NEXT_PUBLIC_*: add to ``.env.production` in each app - do NOT add to Vercel project settingsCLAUDE.md Environment Variables section if it's a key variableturbo.json tasks.build.env.env.local files and Vercel project settings (use the prod-vercel skill in PACMS)NEXT_PUBLIC_*: remove from ``.env.production` in each appCLAUDE.md if documented thereKeep this alphabetically sorted:
API_URL, BREVO_API_KEY, NEXT_PUBLIC_SENTRY_DSN, PACMS_API_KEY, SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, TURNSTILE_SECRET_KEY