env-validate

Name: env-validate
Availability: InStock
Author: victorp1leon

Validate and normalize .env configurations for missing variables, duplicate keys, and trailing whitespace.

Updated Mar 6, 2026

Search Tags:#automation #validation #configuration #environment #normalization #env #dotenv

Ready to run

npx skills add https://github.com/victorp1leon/openclaw-bakery --skill env-validate-victorp1leon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: env-validate
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/env-validate
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill env-validate-victorp1leon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and normalize .env configurations to ensure correct runtime variables and prevent deployment failures.

Core Features & Use Cases

Structural checks to catch duplicate keys, trailing whitespace, and empty required keys.
Per-mode validation of required keys for unit, smoke, and live flows with targeted normalization.
Re-run checks and report actionable issues to guide fixes before running bot flows.

Quick Start

Run a validation to detect duplicates, missing keys, and trailing whitespace in the .env file.

Frequently Asked Questions about env-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate .env files to prevent missing variables before running bot flows?▼

To validate .env files, run structural checks and per-mode validation to detect missing variables, duplicate keys, and trailing whitespace. This ensures correct runtime variables and prevents deployment failures before executing unit, smoke, or live bot flows.

What is .env normalization and how does it fix configuration issues?▼

.env normalization standardizes environment configurations by applying structural checks and mode-specific key validation. It identifies and reports actionable issues like duplicate keys and empty required values, guiding fixes to ensure correct runtime variables.

Can I run environment validation for different modes like unit, smoke, and live flows?▼

Yes, you can validate .env configurations for unit, smoke, and live flows. The validation performs per-mode checks of required keys, applying targeted normalization to detect missing variables and trailing whitespace specific to each runtime environment.

What's the best way to detect duplicate keys and trailing whitespace in a .env file?▼

The best way to detect duplicate keys and trailing whitespace is running automated structural checks on your .env file. These environment validation checks comprehensively report actionable issues, catching formatting errors that cause deployment failures.

Does .env validation require any external dependencies to check environment variables?▼

No external dependencies are required to validate .env configurations. The validation runs self-contained structural checks and per-mode key validation directly on your environment files to detect missing variables and formatting issues.

Why does my .env configuration fail when deploying automation bot flows?▼

Your .env configuration fails during bot flow deployment due to missing required variables, duplicate keys, or trailing whitespace. Running environment validation before deployment catches these structural issues and reports actionable fixes to ensure correct runtime variables.