This wraps the Varlock CLI to keep secrets out of Claude's context during development sessions. It enforces rules like never echoing environment variables, never reading .env files directly, and always using masked validation output. You define a .env.schema with type annotations and sensitivity flags, then Varlock validates without exposing values in terminal output or logs. The skill includes patterns for safe secret rotation, CI/CD integration, and external sources like 1Password or AWS Secrets Manager. Honestly most useful if you're already paranoid about secrets leaking into LLM context windows or you're working in a compliance heavy environment where audit trails matter.
- skills.sh installs
- 267
- GitHub stars
- 33
- last updated
- Aug 21, 2026
Install
$ npx -y skills add wrsmith108/varlock-claude-skill --skill varlock --agent claude-codeInstalls into .claude/skills of the current project.
Files
Varlock Security Skill
Secure-by-default environment variable management for Claude Code sessions.
Repository: https://github.com/dmno-dev/varlock Documentation: https://varlock.dev
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
# ❌ 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
# ❌ NEVER DO THIS - exposes all secrets
cat .env
less .env
Read tool on .env file
# ✅ DO THIS - read schema (safe) not values
cat .env.schema
varlock load # Shows masked values
Rule 3: Use Varlock for Validation
# ❌ NEVER DO THIS - exposes secret in error
test -n "$API_KEY" && echo "Key: $API_KEY"
Sponsors
Details
- Repository
- github.com/wrsmith108/varlock-claude-skill
- Category
- Backend & APIs
- First seen
- Jun 3, 2026
