OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add contentstack/contentstack-agent-skills --skill launch-sync-environment-variables-from-env-example
Fetch environment variables from a Contentstack Launch project, compare them with a local `.env.example` file, and patch the target environment to add any missing keys.
npx skills add contentstack/contentstack-agent-skills --skill launch-sync-environment-variables-from-env-example
Fetch environment variables from a Contentstack Launch project, compare them with a local .env.example file, and patch the target environment to add any missing keys.
Use when a Launch environment must match the keys defined in a local .env.example file.
Use to audit missing environment variables before a deployment.
Use to add missing variable names to a Launch environment without manually editing config.
A Launch environment can drift from the variables expected by a frontend project. This skill checks the environment against .env.example and updates Launch when keys are missing.
All keys present in .env.example exist in the target Launch environment.
Missing keys are added through the Launch Projects/Environments API.
The script reports what was missing and what was updated.
No secrets are printed in logs.
.env.example file.env.example.env.example..env.example and add any missing keys.Read and parse the local .env.example file.
Fetch the target Launch environment and its current variables.
Compare keys from the file against keys in Launch.
Build a minimal patch payload containing only missing keys.
Call PATCH /projects/{project_uid}/environments/{environment_uid}.
Report the changes and stop without exposing values.
Read the local .env.example file and extract variable names. Ignore comments, blank lines, and malformed entries.
Use the Launch API to get the target project and environment, then read the current environment variables.
Compare .env.example keys against Launch keys. Identify only missing keys unless the user explicitly asks to update existing values.
Call PATCH /projects/{project_uid}/environments/{environment_uid} with the minimal update needed to add missing keys.
Return a concise summary of missing keys, patched keys, and any errors. Never print secret values or tokens.
Use concise, machine-readable summaries. Do not print secret values from Launch or local files. Show missing keys and updated keys separately. Include the project UID and environment UID in the summary. If running in dry-run mode, clearly label that no changes were made.
Use the Launch API and Projects/Environments endpoints. Validate project and environment UIDs before patching. Avoid logging deployment tokens or environment secrets. Use the smallest possible PATCH payload. If the API returns validation errors, surface them without retrying blindly.
Never expose deployment tokens or environment secrets. Validate project and environment targets before patching. Do not print variable values in logs or output. Require explicit user intent before making any change. Prefer dry-run behavior unless the user asks to apply changes.
Treat any PATCH that changes Launch configuration as a destructive external action. Confirm the target project and environment before applying changes. Do not broaden the update beyond missing keys unless the user explicitly requests it.
Never reveal secret values from .env.example or Launch. Log only key names and counts. Redact tokens, API keys, and environment values in all output.
Read environment variables only as needed for authentication and target selection. Never echo env var values. Support loading from local .env.example for comparison only, not for secret disclosure.