sickn33/antigravity-awesome-skills/varlock

# ❌ 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"

# ❌ 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

# ❌ NEVER DO THIS - exposes secret in error
test -n "$API_KEY" && echo "Key: $API_KEY"
 
# ✅ DO THIS - Varlock validates and masks
varlock load
# Output shows: API_KEY 🔐sensitive └ ▒▒▒▒▒

# ❌ NEVER DO THIS - secret in command history
curl -H "Authorization: Bearer sk_live_xxx" https://api.example.com
 
# ✅ DO THIS - use environment variable
# Expanding a secret into curl arguments can expose it to process inspection.
# Prefer an application/HTTP client that reads credentials internally from the environment.
# Or better: varlock run -- curl ...

# Install Varlock CLI
tmpdir="$(mktemp -d)"
trap 'rm -rf "$tmpdir"' EXIT
curl -sSfL https://varlock.dev/install.sh -o "$tmpdir/varlock-install.sh"
cat "$tmpdir/varlock-install.sh"  # review the full installer before executing
sh "$tmpdir/varlock-install.sh" --force-no-brew
 
# Add to PATH (add to ~/.zshrc or ~/.bashrc)
export PATH="$HOME/.varlock/bin:$PATH"
 
# Verify
varlock --version

# Create .env.schema from existing .env
varlock init
 
# Or create manually
touch .env.schema

# Global defaults
# @defaultSensitive=true @defaultRequired=infer
 
# Application
# @type=enum(development,staging,production) @sensitive=false
NODE_ENV=development
 
# @type=port @sensitive=false
PORT=3000
 
# Database - SENSITIVE
# @type=url @required
DATABASE_URL=
 
# @type=string @required @sensitive
DATABASE_PASSWORD=
 
# API Keys - SENSITIVE
# @type=string(startsWith=sk_) @required @sensitive
STRIPE_SECRET_KEY=
 
# @type=string(startsWith=pk_) @sensitive=false
STRIPE_PUBLISHABLE_KEY=

# Check all variables (safe - masks sensitive values)
varlock load
 
# Quiet mode (no output on success)
varlock load --quiet
 
# Check specific environment
varlock load --env=production

# Inject validated env into command
varlock run -- npm start
varlock run -- node script.js
varlock run -- pytest
 
# Child commands receive secrets and may print them; audit their logging and disable tracing

# Schema is safe to read - contains no values
cat .env.schema
 
# List expected variables
grep "^[A-Z]" .env.schema

# Always validate environment first
varlock load --quiet || {
  echo "❌ Environment validation failed"
  exit 1
}
 
# Then proceed with operation
npm run build

# 1. Update secret in external source (1Password, AWS, etc.)
# 2. Update .env file manually (don't use Claude for this)
# 3. Validate new value works
varlock load
 
# 4. If using GitHub Secrets, sync (values not shown)
./scripts/update-github-secrets.sh

# GitHub Actions - secrets from GitHub Secrets
- name: Validate environment
  env:
    DATABASE_URL: ${{ secrets.DATABASE_URL }}
    API_KEY: ${{ secrets.API_KEY }}
  run: varlock load --quiet

# Install Varlock in container
RUN tmpdir="$(mktemp -d)" \
    && curl -sSfL https://varlock.dev/install.sh -o "$tmpdir/varlock-install.sh" \
    && cat "$tmpdir/varlock-install.sh" \
    && sh "$tmpdir/varlock-install.sh" --force-no-brew \
    && rm -rf "$tmpdir" \
    && ln -s /root/.varlock/bin/varlock /usr/local/bin/varlock
 
# Validate at container start
CMD ["varlock", "run", "--", "npm", "start"]

# ✅ Safe approach
varlock load 2>&1 | grep "API_KEY"
# Shows: ✅ API_KEY 🔐sensitive └ ▒▒▒▒▒
 
# ❌ Never do
echo $API_KEY

# ✅ Safe approach - check presence and format
varlock load  # Validates types and required fields
 
# Check if key has correct prefix (without showing value)
varlock load 2>&1 | grep -E "(CLERK|AUTH)"
 
# ❌ Never do
printenv | grep KEY

Claude should respond:
"I cannot directly modify secrets for security reasons. Please:
1. Update the value in your .env file manually
2. Or update in your secrets manager (1Password, AWS, etc.)
3. Then run `varlock load` to validate
 
I can help you update the .env.schema if you need to add new variables."

Claude should respond:
"I won't read .env files directly as they contain secrets. Instead:
- Run `varlock load` to see masked values
- Run `cat .env.schema` to see the schema (safe)
- I can help you modify .env.schema if needed"

# In .env.schema
# @type=string @sensitive
API_KEY=exec('op read "op://vault/item/field"')

# In .env.schema
# @type=string @sensitive
DB_PASSWORD=exec('aws secretsmanager get-secret-value --secret-id prod/db --query SecretString --output text')

# In .env.schema
# @type=url
API_URL=env('API_URL_${NODE_ENV}', 'http://localhost:3000')

# Check installation
ls ~/.varlock/bin/varlock
 
# Add to PATH
export PATH="$HOME/.varlock/bin:$PATH"
 
# Or use full path
~/.varlock/bin/varlock load

# Check which variables are missing/invalid
varlock load  # Shows detailed errors
 
# Common fixes:
# - Add missing required variables to .env
# - Fix type mismatches (port must be number)
# - Check string prefixes match schema

# 1. Rotate the exposed secret immediately
# 2. Check .env.schema has @sensitive annotation
# 3. Ensure using varlock commands, not echo/cat
 
# Add missing sensitivity:
# Before: API_KEY=
# After:  # @type=string @sensitive
#         API_KEY=

{
  "scripts": {
    "env:validate": "varlock load",
    "env:check": "varlock load --quiet",
    "prestart": "varlock load --quiet",
    "start": "varlock run -- node server.js"
  }
}