varlock

Mask environment variables and validate secrets via the Varlock CLI.

75|17|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/smith-horn/skillsmith --skill varlock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: varlock
Source: https://github.com/smith-horn/skillsmith/tree/main/.claude/skills/varlock
Command: npx skills add https://github.com/smith-horn/skillsmith --skill varlock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secrets leakage in Claude Code sessions is a critical risk. This Skill provides secure-by-default environment variable management to mask and restrict secrets, preventing exposure in terminals, logs, and the model context.

Core Features & Use Cases

  • Schema-driven masking: Uses a .env.schema to mark sensitive variables and ensure values never appear in outputs.
  • Safe validation and access: varlock load validates presence and types without revealing secret values; supports masking in logs and reports.
  • Secure command execution: Use varlock run to inject validated vars into commands without printing secrets; supports integration with CI/CD and containers.
  • Real-world workflow: Protects API keys during local development and in automated deployment pipelines.

Quick Start

Install Varlock CLI: curl -sSfL https://varlock.dev/install.sh | sh -s -- --force-no-brew Add to PATH: export PATH="$HOME/.varlock/bin:$PATH" Verify: varlock --version Initialize project: varlock init Or create manually: touch .env.schema

Frequently Asked Questions about varlock

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

FAQPage Schema
How do I prevent secrets leakage in Claude Code sessions?

Prevent secrets leakage in Claude Code sessions by applying schema-driven masking to mark sensitive environment variables, ensuring their values never appear in terminal outputs, logs, or model context.

What is the best way to mask environment variables during local development?

The best way to mask environment variables during local development is using a .env.schema file to define sensitive variables, validating their presence and types without ever revealing the secret values in outputs.

How do I inject environment variables into CI/CD commands without printing secrets?

Inject environment variables into CI/CD commands without printing secrets by using a safe command execution tool that validates vars against a schema and masks them in logs and reports during deployment pipelines.

Can I validate secret types and presence without exposing the values in logs?

Yes, you can validate secret types and presence without exposing values by using schema-driven validation that loads and checks environment variables against a .env.schema, masking all sensitive data in generated reports.

Does schema-driven environment variable masking work with automated deployment pipelines?

Schema-driven environment variable masking works with automated deployment pipelines by enforcing safe command execution, injecting validated vars into containers and CI/CD workflows without printing secrets to terminal outputs.

When should I use schema-based secret rotation guidance?

Use schema-based secret rotation guidance during development and deployment workflows when secrets must be validated and consumed without exposure, enforcing secure rotation practices to prevent leakage across environments.