Agent skill · AI & Agents

varlock

Secure-by-default environment variable management for Claude Code sessions.

Nick44,414★ · +328/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill varlock --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/varlock/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Varlock Security Skill Secure-by-default environment variable management for Claude Code sessions. > **Repository**: https://github.com/dmno-dev/varlock > **Documentation**: https://varlock.dev ## When to Use - You need to work with environment variables or secrets in a Claude Code session without exposing their values. - The task involves validating, loading, or auditing secrets while keeping them out of logs, diffs, and assistant context. - You want a secure-by-default workflow built around Varlock instead of direct `.env` inspection. ## Core Principle: Secrets Never Exposed When working with Claude, secrets must NEVER appear in: - Terminal output - Claude's input/output context - Log files or traces - Git commits or diffs - Error messages This skill ensures all sensitive data is properly protected. --- ## CRITICAL: Security Rules for Claude ### Rule 1: Never Echo Secrets ```bash # ❌ NEVER DO THIS - exposes secret to Claude's context echo $CLERK_SECRET_KEY cat .env | grep SECRET printenv | grep API # ✅ DO THIS - validates without exposing varlock load --quiet && echo "✓ Secrets validated" ``` ### Rule 2: Never Read .env Directly ```bash # ❌ NEVER DO THIS - exposes all secrets c

What's inside
Steps it walks through
  1. When to Use
  2. Core Principle: Secrets Never Exposed
  3. CRITICAL: Security Rules for Claude
  4. Rule 1: Never Echo Secrets
  5. Rule 2: Never Read .env Directly
  6. Rule 3: Use Varlock for Validation
  7. Rule 4: Never Include Secrets in Commands
  8. Quick Start
  9. Installation
  10. Initialize Project
  11. Schema File: .env.schema
  12. Basic Structure
  13. Security Annotations
  14. Type Annotations
Commands it runs
echo $CLERK_SECRET_KEY
cat .env | grep SECRET
printenv | grep API
varlock load --quiet && echo "✓ Secrets validated"
cat .env
less .env
Read tool on .env file
cat .env.schema
varlock load  # Shows masked values
test -n "$API_KEY" && echo "Key: $API_KEY"
More from agentic-awesome-skills
All skills →
About this skill
What does the varlock skill do?

Secure-by-default environment variable management for Claude Code sessions.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill varlock --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going