varlock

Validate and inject environment variables using schema-driven encrypted files.

1|Updated Jul 22, 2026
One-click install
npx skills add https://github.com/wyattjoh/skills --skill varlock-wyattjoh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: varlock
Source: https://github.com/wyattjoh/skills/tree/main/skills/varlock
Command: npx skills add https://github.com/wyattjoh/skills --skill varlock-wyattjoh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing environment variables is often insecure, error-prone, and difficult to audit. This skill provides a robust, schema-driven system to validate, encrypt, and inject environment variables, ensuring secrets are never leaked to AI agents or logs.

Core Features & Use Cases

  • Schema Validation: Enforce types, requirements, and sensitivity rules via a committed .env.schema file.
  • Secure Secret Handling: Encrypt sensitive values locally and redact them automatically from logs and agent outputs.
  • Workflow Integration: Inject validated variables into any command-line process or application runtime with built-in support for multi-environment configurations.

Quick Start

Run the varlock init command in your project root to automatically scan your environment files and generate a secure schema.

Frequently Asked Questions about varlock

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

FAQPage Schema
How do I prevent environment variables from leaking to AI agents and logs?

Prevent environment variable leakage by using a schema-driven system to encrypt sensitive values and automatically redact them from logs and agent outputs. This approach validates configurations locally before injection to ensure secrets remain secure.

How do I validate environment variables across development, staging, and production?

Validate environment variables across multiple environments by layering encrypted value files and enforcing strict type definitions via a committed schema. This prevents configuration drift by requiring local binaries to inject validated variables into application runtimes.

Do I need a local binary installed to manage secrets with schema validation?

Yes, managing secrets with schema validation requires installing a local varlock binary. This binary performs security audits, encrypts values locally, and generates type-safe accessors to inject validated variables into command-line processes.

What is the best way to enforce strict type definitions for environment configuration?

Enforce strict type definitions for environment configuration by committing a schema file that dictates types, requirements, and sensitivity rules. Running an initialization command scans existing files to automatically generate this secure schema.

How do I generate type-safe accessors for application environment variables?

Generate type-safe accessors for application environment variables by using a local binary to read the schema definitions. This binary processes the strict types and encrypted values to produce secure accessors for application code.