env-management

Audit environment variables for missing, placeholder, or misconfigured API keys.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/KAFKA2306/yt3 --skill env-management-kafka2306
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: env-management
Source: https://github.com/KAFKA2306/yt3/tree/main/.agent/skills/env-management
Command: npx skills add https://github.com/KAFKA2306/yt3 --skill env-management-kafka2306

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Environment variables are a common source of silent failures when API keys or configuration values are missing, placeholdered, or misnamed; this Skill ensures those errors are detected before runtime to save debugging time and prevent credential leaks.

Core Features & Use Cases

  • Pre-flight Auditing: Count and verify required keys and connectivity to prepared external services before pipelines run.
  • Strict Validation Rules: Enforce presence of variables declared in source types, treat placeholders as missing, and fail fast with clear error messages.
  • Secrets Safety: Recommend explicit env-file loading, avoid logging secret values, and prescribe immediate rotation for leaked files.
  • Use Case: Run a pre-deployment check in CI to ensure GEMINI_API_KEY rotation is correctly configured and no placeholder values remain.

Quick Start

Run a pre-flight environment audit to verify required keys, detect placeholder values, and fail fast with clear missing-key messages.

Frequently Asked Questions about env-management

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

FAQPage Schema
How do I validate environment variables and detect missing API keys before runtime?▼

Pre-flight environment auditing validates required variables, treats placeholder tokens as missing, and fails fast with clear error messages to prevent silent runtime failures before executing API-dependent workflows.

What is the best way to check for placeholder environment variables in a CI/CD pipeline?▼

Strict validation rules enforce the presence of variables declared in source types, treating placeholder tokens as missing and failing fast with clear missing-key messages during pre-flight checks.

How does pre-flight environment variable validation handle secret values and dotenv loading?▼

Pre-flight validation prevents logging secret values, enforces explicit env-file or dotenv loading, and prescribes immediate rotation for leaked files to maintain credentials safety.

Can I use environment variable validation for GEMINI_API_KEY rotation checks?▼

Yes, environment variable validation supports GEMINI_API_KEY rotation semantics, verifying that newly configured keys are present and no placeholder values remain before deployment.

Why does my application fail authentication when environment variables are misconfigured?▼

Misconfigured API keys or placeholdered environment variables cause silent authentication failures; strict pre-flight auditing detects these missing or misnamed values before runtime to save debugging time.

When do I need to run an environment variable audit for API-dependent workflows?▼

Run an environment variable audit as a pre-deployment check in CI or before debugging authentication failures to verify required keys, detect placeholder values, and ensure external service connectivity.