[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C3HREVZEFGPKJNTY1ESFG":3,"skill-same:01M73C3HREVZEFGPKJNTY1ESFG":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M73C3HREVZEFGPKJNTY1ESFG","varlock",null,"Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminals, logs, traces, or Claude's context. Trigger phrases include \"environment variables\",...","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fvarlock\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: varlock\ndescription: Secure environment variable management with Varlock. Use when handling secrets, API keys, credentials, or any sensitive configuration. Ensures secrets are never exposed in terminals, logs, traces, or Claude's context. Trigger phrases include \"environment variables\",...\nversion: 1.0.0\n---\n\n\u003C!-- security-allowlist: curl-pipe-bash -->\n\n# Varlock Security Skill\n\nSecure-by-default environment variable management for Claude Code sessions.\n\n> **Repository**: https:\u002F\u002Fgithub.com\u002Fdmno-dev\u002Fvarlock\n> **Documentation**: https:\u002F\u002Fvarlock.dev\n\n## Core Principle: Secrets Never Exposed\n\nWhen working with Claude, secrets must NEVER appear in:\n- Terminal output\n- Claude's input\u002Foutput context\n- Log files or traces\n- Git commits or diffs\n- Error messages\n\nThis skill ensures all sensitive data is properly protected.\n\n---\n\n## CRITICAL: Security Rules for Claude\n\n### Rule 1: Never Echo Secrets\n\n```bash\n# ❌ NEVER DO THIS - exposes secret to Claude's context\necho $CLERK_SECRET_KEY\ncat .env | grep SECRET\nprintenv | grep API\n\n# ✅ DO THIS - validates without exposing\nvarlock load --quiet && echo \"✓ Secrets validated\"\n```\n\n### Rule 2: Never Read .env Directly\n\n```bash\n# ❌ NEVER DO THIS - exposes all secrets\ncat .env\nless .env\nRead tool on .env file\n\n# ✅ DO THIS - read schema (safe) not values\ncat .env.schema\nvarlock load  # Shows masked values\n```\n\n### Rule 3: Use Varlock for Validation\n\n```bash\n# ❌ NEVER DO THIS - exposes secret in error\ntest -n \"$API_KEY\" && echo \"Key: $API_KEY\"\n\n# ✅ DO THIS - Varlock validates and masks\nvarlock load\n# Output shows: API_KEY 🔐sensitive └ ▒▒▒▒▒\n```\n\n### Rule 4: Never Include Secrets in Commands\n\n```bash\n# ❌ NEVER DO THIS - secret in command history\ncurl -H \"Authorization: Bearer sk_live_xxx\" https:\u002F\u002Fapi.example.com\n\n# ✅ DO THIS - use environment variable\ncurl -H \"Authorization: Bearer $API_KEY\" https:\u002F\u002Fapi.example.com\n# Or better: varlock run -- curl ...\n```\n\n---\n\n## Quick Start\n\n### Installation\n\n```bash\n# Install Varlock CLI\ncurl -sSfL https:\u002F\u002Fvarlock.dev\u002Finstall.sh | sh -s -- --force-no-brew\n\n# Add to PATH (add to ~\u002F.zshrc or ~\u002F.bashrc)\nexport PATH=\"$HOME\u002F.varlock\u002Fbin:$PATH\"\n\n# Verify\nvarlock --version\n```\n\n### Initialize Project\n\n```bash\n# Create .env.schema from existing .env\nvarlock init\n\n# Or create manually\ntouch .env.schema\n```\n\n---\n\n## Schema File: .env.schema\n\nThe schema defines types, validation, and sensitivity for each variable.\n\n### Basic Structure\n\n```bash\n# Global defaults\n# @defaultSensitive=true @defaultRequired=infer\n\n# Application\n# @type=enum(development,staging,production) @sensitive=false\nNODE_ENV=development\n\n# @type=port @sensitive=false\nPORT=3000\n\n# Database - SENSITIVE\n# @type=url @required\nDATABASE_URL=\n\n# @type=string @required @sensitive\nDATABASE_PASSWORD=\n\n# API Keys - SENSITIVE\n# @type=string(startsWith=sk_) @required @sensitive\nSTRIPE_SECRET_KEY=\n\n# @type=string(startsWith=pk_) @sensitive=false\nSTRIPE_PUBLISHABLE_KEY=\n```\n\n### Security Annotations\n\n| Annotation | Effect | Use For |\n|------------|--------|---------|\n| `@sensitive` | Redacted in all output | API keys, passwords, tokens |\n| `@sensitive=false` | Shown in logs | Public keys, non-secret config |\n| `@defaultSensitive=true` | All vars sensitive by default | High-security projects |\n\n### Type Annotations\n\n| Type | Validates | Example |\n|------|-----------|---------|\n| `string` | Any string | `@type=string` |\n| `string(startsWith=X)` | Prefix validation | `@type=string(startsWith=sk_)` |\n| `string(contains=X)` | Substring validation | `@type=string(contains=+clerk_test)` |\n| `url` | Valid URL | `@type=url` |\n| `port` | 1-65535 | `@type=port` |\n| `boolean` | true\u002Ffalse | `@type=boolean` |\n| `enum(a,b,c)` | One of values | `@type=enum(dev,prod)` |\n\n---\n\n## Safe Commands for Claude\n\n### Validating Environment\n\n```bash\n# Check all variables (safe - masks sensitive values)\nvarlock load\n\n# Quiet mode (no output on success)\nvarlock load --quiet\n\n# Check specific environment\nvarlock load --env=production\n```\n\n### Running Commands with Secrets\n\n```bash\n# Inject validated env into command\nvarlock run -- npm start\nvarlock run -- node script.js\nvarlock run -- pytest\n\n# Secrets are available to the command but never printed\n```\n\n### Checking Schema (Safe)\n\n```bash\n# Schema is safe to read - contains no values\ncat .env.schema\n\n# List expected variables\ngrep \"^[A-Z]\" .env.schema\n```\n\n---\n\n## Common Patterns\n\n### Pattern 1: Validate Before Operations\n\n```bash\n# Always validate environment first\nvarlock load --quiet || {\n  echo \"❌ Environment validation failed\"\n  exit 1\n}\n\n# Then proceed with operation\nnpm run build\n```\n\n### Pattern 2: Safe Secret Rotation\n\n```bash\n# 1. Update secret in external source (1Password, AWS, etc.)\n# 2. Update .env file manually (don't use Claude for this)\n# 3. Validate new value works\nvarlock load\n\n# 4. If using GitHub Secrets, sync (values not shown)\n.\u002Fscripts\u002Fupdate-github-secrets.sh\n```\n\n### Pattern 3: CI\u002FCD Integration\n\n```yaml\n# GitHub Actions - secrets from GitHub Secrets\n- name: Validate environment\n  env:\n    DATABASE_URL: ${{ secrets.DATABASE_URL }}\n    API_KEY: ${{ secrets.API_KEY }}\n  run: varlock load --quiet\n```\n\n### Pattern 4: Docker Integration\n\n```dockerfile\n# Install Varlock in container\nRUN curl -sSfL https:\u002F\u002Fvarlock.dev\u002Finstall.sh | sh -s -- --force-no-brew \\\n    && ln -s \u002Froot\u002F.varlock\u002Fbin\u002Fvarlock \u002Fusr\u002Flocal\u002Fbin\u002Fvarlock\n\n# Validate at container start\nCMD [\"varlock\", \"run\", \"--\", \"npm\", \"start\"]\n```\n\n---\n\n## Handling Secret-Related Tasks\n\n### When User Asks to \"Check if API key is set\"\n\n```bash\n# ✅ Safe approach\nvarlock load 2>&1 | grep \"API_KEY\"\n# Shows: ✅ API_KEY 🔐sensitive └ ▒▒▒▒▒\n\n# ❌ Never do\necho $API_KEY\n```\n\n### When User Asks to \"Debug authentication\"\n\n```bash\n# ✅ Safe approach - check presence and format\nvarlock load  # Validates types and required fields\n\n# Check if key has correct prefix (without showing value)\nvarlock load 2>&1 | grep -E \"(CLERK|AUTH)\"\n\n# ❌ Never do\nprintenv | grep KEY\n```\n\n### When User Asks to \"Update a secret\"\n\n```\nClaude should respond:\n\"I cannot directly modify secrets for security reasons. Please:\n1. Update the value in your .env file manually\n2. Or update in your secrets manager (1Password, AWS, etc.)\n3. Then run `varlock load` to validate\n\nI can help you update the .env.schema if you need to add new variables.\"\n```\n\n### When User Asks to \"Show me the .env file\"\n\n```\nClaude should respond:\n\"I won't read .env files directly as they contain secrets. Instead:\n- Run `varlock load` to see masked values\n- Run `cat .env.schema` to see the schema (safe)\n- I can help you modify .env.schema if needed\"\n```\n\n---\n\n## External Secret Sources\n\n### 1Password Integration\n\n```bash\n# In .env.schema\n# @type=string @sensitive\nAPI_KEY=exec('op read \"op:\u002F\u002Fvault\u002Fitem\u002Ffield\"')\n```\n\n### AWS Secrets Manager\n\n```bash\n# In .env.schema\n# @type=string @sensitive\nDB_PASSWORD=exec('aws secretsmanager get-secret-value --secret-id prod\u002Fdb')\n```\n\n### Environment-Specific Values\n\n```bash\n# In .env.schema\n# @type=url\nAPI_URL=env('API_URL_${NODE_ENV}', 'http:\u002F\u002Flocalhost:3000')\n```\n\n---\n\n## Troubleshooting\n\n### \"varlock: command not found\"\n\n```bash\n# Check installation\nls ~\u002F.varlock\u002Fbin\u002Fvarlock\n\n# Add to PATH\nexport PATH=\"$HOME\u002F.varlock\u002Fbin:$PATH\"\n\n# Or use full path\n~\u002F.varlock\u002Fbin\u002Fvarlock load\n```\n\n### \"Schema validation failed\"\n\n```bash\n# Check which variables are missing\u002Finvalid\nvarlock load  # Shows detailed errors\n\n# Common fixes:\n# - Add missing required variables to .env\n# - Fix type mismatches (port must be number)\n# - Check string prefixes match schema\n```\n\n### \"Sensitive value exposed in logs\"\n\n```bash\n# 1. Rotate the exposed secret immediately\n# 2. Check .env.schema has @sensitive annotation\n# 3. Ensure using varlock commands, not echo\u002Fcat\n\n# Add missing sensitivity:\n# Before: API_KEY=\n# After:  # @type=string @sensitive\n#         API_KEY=\n```\n\n---\n\n## npm Scripts\n\nAdd these to your package.json:\n\n```json\n{\n  \"scripts\": {\n    \"env:validate\": \"varlock load\",\n    \"env:check\": \"varlock load --quiet || echo 'Environment validation failed'\",\n    \"prestart\": \"varlock load --quiet\",\n    \"start\": \"varlock run -- node server.js\"\n  }\n}\n```\n\n---\n\n## Security Checklist for New Projects\n\n- [ ] Install Varlock CLI\n- [ ] Create `.env.schema` with all variables defined\n- [ ] Mark all secrets with `@sensitive` annotation\n- [ ] Add `@defaultSensitive=true` to schema header\n- [ ] Add `.env` to `.gitignore`\n- [ ] Commit `.env.schema` to version control\n- [ ] Add `npm run env:validate` to CI\u002FCD\n- [ ] Document secret rotation procedure\n- [ ] Never use `cat .env` or `echo $SECRET` in Claude sessions\n\n---\n\n## Quick Reference Card\n\n| Task | Safe Command |\n|------|-------------|\n| Validate all env vars | `varlock load` |\n| Quiet validation | `varlock load --quiet` |\n| Run with env | `varlock run -- \u003Ccmd>` |\n| View schema | `cat .env.schema` |\n| Check specific var | `varlock load \\| grep VAR_NAME` |\n\n| Never Do | Why |\n|----------|-----|\n| `cat .env` | Exposes all secrets |\n| `echo $SECRET` | Exposes to Claude context |\n| `printenv \\| grep` | Exposes matching secrets |\n| Read .env with tools | Secrets in Claude's context |\n| Hardcode in commands | In shell history |\n\n---\n\n## Integration with Other Skills\n\n### Clerk Skill\n- Test user passwords are `@sensitive`\n- Test emails are `@sensitive=false` (contain +clerk_test, not secret)\n- See: `~\u002F.claude\u002Fskills\u002Fclerk\u002FSKILL.md`\n\n### Docker Skill\n- Mount `.env` file, never copy secrets to image\n- Use `varlock run` as entrypoint\n- See: `~\u002F.claude\u002Fskills\u002Fdocker\u002FSKILL.md`\n\n---\n\n*Last updated: December 22, 2025*\n*Secure-by-default environment management for Claude Code*\n","\u003C!-- security-allowlist: curl-pipe-bash -->\n\n# Varlock Security Skill\n\nSecure-by-default environment variable management for Claude Code sessions.\n\n> **Repository**: https:\u002F\u002Fgithub.com\u002Fdmno-dev\u002Fvarlock\n> **Documentation**: https:\u002F\u002Fvarlock.dev\n\n## Core Principle: Secrets Never Exposed\n\nWhen working with Claude, secrets must NEVER appear in:\n- Terminal output\n- Claude's input\u002Foutput context\n- Log files or traces\n- Git commits or diffs\n- Error messages\n\nThis skill ensures all sensitive data is properly protected.\n\n---\n\n## CRITICAL: Security Rules for Claude\n\n### Rule 1: Never Echo Secrets\n\n```bash\n# ❌ NEVER DO THIS - exposes secret to Claude's context\necho $CLERK_SECRET_KEY\ncat .env | grep SECRET\nprintenv | grep API\n\n# ✅ DO THIS - validates without exposing\nvarlock load --quiet && echo \"✓ Secrets validated\"\n```\n\n### Rule 2: Never Read .env Directly\n\n```bash\n# ❌ NEVER DO THIS - exposes all secrets\ncat .env\nless .env\nRead tool on .env file\n\n# ✅ DO THIS - read schema (safe) not values\ncat .env.schema\nvarlock load  # Shows masked values\n```\n\n### Rule 3: Use Varlock for Validation\n\n```bash\n# ❌ NEVER DO THIS - exposes secret in error\ntest -n \"$API_KEY\" && echo \"Key: $API_KEY\"\n\n# ✅ DO THIS - Varlock validates and masks\nvarlock load\n# Output shows: API_KEY 🔐sensitive └ ▒▒▒▒▒\n```\n\n### Rule 4: Never Include Secrets in Commands\n\n```bash\n# ❌ NEVER DO THIS - secret in command history\ncurl -H \"Authorization: Bearer sk_live_xxx\" https:\u002F\u002Fapi.example.com\n\n# ✅ DO THIS - use environment variable\ncurl -H \"Authorization: Bearer $API_KEY\" https:\u002F\u002Fapi.example.com\n# Or better: varlock run -- curl ...\n```\n\n---\n\n## Quick Start\n\n### Installation\n\n```bash\n# Install Varlock CLI\ncurl -sSfL https:\u002F\u002Fvarlock.dev\u002Finstall.sh | sh -s -- --force-no-brew\n\n# Add to PATH (add to ~\u002F.zshrc or ~\u002F.bashrc)\nexport PATH=\"$HOME\u002F.varlock\u002Fbin:$PATH\"\n\n# Verify\nvarlock --version\n```\n\n### Initialize Project\n\n```bash\n# Create .env.schema from existing .env\nvarlock init\n\n# Or create manually\ntouch .env.schema\n```\n\n---\n\n## Schema File: .env.schema\n\nThe schema defines types, validation, and sensitivity for each variable.\n\n### Basic Structure\n\n```bash\n# Global defaults\n# @defaultSensitive=true @defaultRequired=infer\n\n# Application\n# @type=enum(development,staging,production) @sensitive=false\nNODE_ENV=development\n\n# @type=port @sensitive=false\nPORT=3000\n\n# Database - SENSITIVE\n# @type=url @required\nDATABASE_URL=\n\n# @type=string @required @sensitive\nDATABASE_PASSWORD=\n\n# API Keys - SENSITIVE\n# @type=string(startsWith=sk_) @required @sensitive\nSTRIPE_SECRET_KEY=\n\n# @type=string(startsWith=pk_) @sensitive=false\nSTRIPE_PUBLISHABLE_KEY=\n```\n\n### Security Annotations\n\n| Annotation | Effect | Use For |\n|------------|--------|---------|\n| `@sensitive` | Redacted in all output | API keys, passwords, tokens |\n| `@sensitive=false` | Shown in logs | Public keys, non-secret config |\n| `@defaultSensitive=true` | All vars sensitive by default | High-security projects |\n\n### Type Annotations\n\n| Type | Validates | Example |\n|------|-----------|---------|\n| `string` | Any string | `@type=string` |\n| `string(startsWith=X)` | Prefix validation | `@type=string(startsWith=sk_)` |\n| `string(contains=X)` | Substring validation | `@type=string(contains=+clerk_test)` |\n| `url` | Valid URL | `@type=url` |\n| `port` | 1-65535 | `@type=port` |\n| `boolean` | true\u002Ffalse | `@type=boolean` |\n| `enum(a,b,c)` | One of values | `@type=enum(dev,prod)` |\n\n---\n\n## Safe Commands for Claude\n\n### Validating Environment\n\n```bash\n# Check all variables (safe - masks sensitive values)\nvarlock load\n\n# Quiet mode (no output on success)\nvarlock load --quiet\n\n# Check specific environment\nvarlock load --env=production\n```\n\n### Running Commands with Secrets\n\n```bash\n# Inject validated env into command\nvarlock run -- npm start\nvarlock run -- node script.js\nvarlock run -- pytest\n\n# Secrets are available to the command but never printed\n```\n\n### Checking Schema (Safe)\n\n```bash\n# Schema is safe to read - contains no values\ncat .env.schema\n\n# List expected variables\ngrep \"^[A-Z]\" .env.schema\n```\n\n---\n\n## Common Patterns\n\n### Pattern 1: Validate Before Operations\n\n```bash\n# Always validate environment first\nvarlock load --quiet || {\n  echo \"❌ Environment validation failed\"\n  exit 1\n}\n\n# Then proceed with operation\nnpm run build\n```\n\n### Pattern 2: Safe Secret Rotation\n\n```bash\n# 1. Update secret in external source (1Password, AWS, etc.)\n# 2. Update .env file manually (don't use Claude for this)\n# 3. Validate new value works\nvarlock load\n\n# 4. If using GitHub Secrets, sync (values not shown)\n.\u002Fscripts\u002Fupdate-github-secrets.sh\n```\n\n### Pattern 3: CI\u002FCD Integration\n\n```yaml\n# GitHub Actions - secrets from GitHub Secrets\n- name: Validate environment\n  env:\n    DATABASE_URL: ${{ secrets.DATABASE_URL }}\n    API_KEY: ${{ secrets.API_KEY }}\n  run: varlock load --quiet\n```\n\n### Pattern 4: Docker Integration\n\n```dockerfile\n# Install Varlock in container\nRUN curl -sSfL https:\u002F\u002Fvarlock.dev\u002Finstall.sh | sh -s -- --force-no-brew \\\n    && ln -s \u002Froot\u002F.varlock\u002Fbin\u002Fvarlock \u002Fusr\u002Flocal\u002Fbin\u002Fvarlock\n\n# Validate at container start\nCMD [\"varlock\", \"run\", \"--\", \"npm\", \"start\"]\n```\n\n---\n\n## Handling Secret-Related Tasks\n\n### When User Asks to \"Check if API key is set\"\n\n```bash\n# ✅ Safe approach\nvarlock load 2>&1 | grep \"API_KEY\"\n# Shows: ✅ API_KEY 🔐sensitive └ ▒▒▒▒▒\n\n# ❌ Never do\necho $API_KEY\n```\n\n### When User Asks to \"Debug authentication\"\n\n```bash\n# ✅ Safe approach - check presence and format\nvarlock load  # Validates types and required fields\n\n# Check if key has correct prefix (without showing value)\nvarlock load 2>&1 | grep -E \"(CLERK|AUTH)\"\n\n# ❌ Never do\nprintenv | grep KEY\n```\n\n### When User Asks to \"Update a secret\"\n\n```\nClaude should respond:\n\"I cannot directly modify secrets for security reasons. Please:\n1. Update the value in your .env file manually\n2. Or update in your secrets manager (1Password, AWS, etc.)\n3. Then run `varlock load` to validate\n\nI can help you update the .env.schema if you need to add new variables.\"\n```\n\n### When User Asks to \"Show me the .env file\"\n\n```\nClaude should respond:\n\"I won't read .env files directly as they contain secrets. Instead:\n- Run `varlock load` to see masked values\n- Run `cat .env.schema` to see the schema (safe)\n- I can help you modify .env.schema if needed\"\n```\n\n---\n\n## External Secret Sources\n\n### 1Password Integration\n\n```bash\n# In .env.schema\n# @type=string @sensitive\nAPI_KEY=exec('op read \"op:\u002F\u002Fvault\u002Fitem\u002Ffield\"')\n```\n\n### AWS Secrets Manager\n\n```bash\n# In .env.schema\n# @type=string @sensitive\nDB_PASSWORD=exec('aws secretsmanager get-secret-value --secret-id prod\u002Fdb')\n```\n\n### Environment-Specific Values\n\n```bash\n# In .env.schema\n# @type=url\nAPI_URL=env('API_URL_${NODE_ENV}', 'http:\u002F\u002Flocalhost:3000')\n```\n\n---\n\n## Troubleshooting\n\n### \"varlock: command not found\"\n\n```bash\n# Check installation\nls ~\u002F.varlock\u002Fbin\u002Fvarlock\n\n# Add to PATH\nexport PATH=\"$HOME\u002F.varlock\u002Fbin:$PATH\"\n\n# Or use full path\n~\u002F.varlock\u002Fbin\u002Fvarlock load\n```\n\n### \"Schema validation failed\"\n\n```bash\n# Check which variables are missing\u002Finvalid\nvarlock load  # Shows detailed errors\n\n# Common fixes:\n# - Add missing required variables to .env\n# - Fix type mismatches (port must be number)\n# - Check string prefixes match schema\n```\n\n### \"Sensitive value exposed in logs\"\n\n```bash\n# 1. Rotate the exposed secret immediately\n# 2. Check .env.schema has @sensitive annotation\n# 3. Ensure using varlock commands, not echo\u002Fcat\n\n# Add missing sensitivity:\n# Before: API_KEY=\n# After:  # @type=string @sensitive\n#         API_KEY=\n```\n\n---\n\n## npm Scripts\n\nAdd these to your package.json:\n\n```json\n{\n  \"scripts\": {\n    \"env:validate\": \"varlock load\",\n    \"env:check\": \"varlock load --quiet || echo 'Environment validation failed'\",\n    \"prestart\": \"varlock load --quiet\",\n    \"start\": \"varlock run -- node server.js\"\n  }\n}\n```\n\n---\n\n## Security Checklist for New Projects\n\n- [ ] Install Varlock CLI\n- [ ] Create `.env.schema` with all variables defined\n- [ ] Mark all secrets with `@sensitive` annotation\n- [ ] Add `@defaultSensitive=true` to schema header\n- [ ] Add `.env` to `.gitignore`\n- [ ] Commit `.env.schema` to version control\n- [ ] Add `npm run env:validate` to CI\u002FCD\n- [ ] Document secret rotation procedure\n- [ ] Never use `cat .env` or `echo $SECRET` in Claude sessions\n\n---\n\n## Quick Reference Card\n\n| Task | Safe Command |\n|------|-------------|\n| Validate all env vars | `varlock load` |\n| Quiet validation | `varlock load --quiet` |\n| Run with env | `varlock run -- \u003Ccmd>` |\n| View schema | `cat .env.schema` |\n| Check specific var | `varlock load \\| grep VAR_NAME` |\n\n| Never Do | Why |\n|----------|-----|\n| `cat .env` | Exposes all secrets |\n| `echo $SECRET` | Exposes to Claude context |\n| `printenv \\| grep` | Exposes matching secrets |\n| Read .env with tools | Secrets in Claude's context |\n| Hardcode in commands | In shell history |\n\n---\n\n## Integration with Other Skills\n\n### Clerk Skill\n- Test user passwords are `@sensitive`\n- Test emails are `@sensitive=false` (contain +clerk_test, not secret)\n- See: `~\u002F.claude\u002Fskills\u002Fclerk\u002FSKILL.md`\n\n### Docker Skill\n- Mount `.env` file, never copy secrets to image\n- Use `varlock run` as entrypoint\n- See: `~\u002F.claude\u002Fskills\u002Fdocker\u002FSKILL.md`\n\n---\n\n*Last updated: December 22, 2025*\n*Secure-by-default environment management for Claude Code*\n",{"name":5,"version":24,"description":7},"1.0.0","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fvarlock","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add kalash33\u002Fkstack --skill varlock",{"tool":39,"command":40},"bunx","bunx skills add kalash33\u002Fkstack --skill varlock",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill varlock","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fvarlock\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]