What problem does it solve? Managing environment variables and secrets across projects often leads to leaked credentials in logs, terminals, or AI agent context, plus drift between .env files and actual code usage. This Skill guides secure env var management with varlock so secrets stay masked and schemas stay the single source of truth. ## Core Features & Use Cases - Schema-driven config: Create and edit .env.schema files with @decorator syntax for types, validation, sensitivity, and documentation, replacing fragile .env.example files. - Secret-safe workflows: Load and validate env vars with sensitive values redacted, encrypt local secrets with hardware-backed encryption, and reference external providers like 1Password, AWS, or Vault via plugins. - Framework integration and migration: Wire varlock into Next.js, Vite, Astro, and other frameworks, or migrate existing projects away from dotenv. - Use Case: A developer asks the AI to add a new API key to their project. The Skill ensures the key is declared in .env.schema as @sensitive, the actual value is set by the user locally or via a secret provider, and validation runs with varlock load --agent without ever exposing the secret. ## Quick Start Ask the AI to set up varlock in your project by running varlock init --agent and generating a .env.schema from your existing .env files.