/vercel-env

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select vercel-env from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv vercel-env, /just-vibe vercel-env and /jv:vercel-env in Claude. See shortcut setup and context examples.

What the agent does

1. Derive required names from code and configuration, and map each to build-time or runtime usage and its intended environment and branch.
2. Compare with authorized metadata to report presence and scope without fetching secret values; identify missing or mis-scoped variables and explain rebuild or redeployment implications.

Inputs

• project, environment/branch scopes, and required variable names.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Presence, scope, and source of configuration names; values remain secret.

Writes

Inspect/plan: report names, scopes and gaps without reading or printing secret values; save requested artifacts only. Apply: add, update or remove only the requested variable in the resolved project and environment scope through a secure input channel, never echoing its value. Redeploying to pick up the change is a separate requested action.

Mode

Inspect; project, environment/branch scopes, and required variable names. Adding, changing or removing a requested variable uses apply mode.

Prerequisites

Exact team/project/environment and deployment/revision when applicable; read access to relevant configuration/logs. Verify installed CLI/API support and framework behavior during implementation. Never print environment values or infer promotion authorization from a preview request.

Expected output

• Redacted variable-name table with consumer, environment, branch scope, rebuild implications and proposed corrections.

How the work is checked

• A preview-only missing variable is distinguished from production; reports and commands never include secret values.

When to stop or clarify

• Mutation needs an explicit configuration request and secure input channel. Do not fetch values when metadata suffices or copy production secrets into previews.

Handling missing context

Infer

Read the linked project, team, framework, environment and deployment SHA from local config and supplied deployment evidence.

Assume

Diagnose locally with existing build scripts when deployment access is missing; do not infer a production target from a preview URL.

Ask

Resolve a missing deployment/team/environment before the dependent remote operation; names and scope suffice without exposing environment values.

Technical guidance

Evidence

Inventory required names across the default and any custom environments, and whether consumers read them during build, server runtime or browser execution.

Method

Compare development, preview, branch, production and any custom environment presence using names only; identify which changes require a rebuild/redeployment.

Pitfall

Public prefixes expose compiled values; changing a setting does not update already-built assets.

Check

Verify the expected consumer sees the correct environment using a non-secret sentinel or presence check without downloading or printing credentials.

Situational decisions

When a changed value is compiled into a static client bundle: Explain the required rebuild/deployment and inspect public exposure; editing a variable alone does not change an existing bundle.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring