[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPDH8JWH41KBHGKWH92EVP":3,"skill-same:01M7CPDH8JWH41KBHGKWH92EVP":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CPDH8JWH41KBHGKWH92EVP","varlock",null,"Secure-by-default environment variable management for Claude Code sessions.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fvarlock\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: varlock\ndescription: \"Secure-by-default environment variable management for Claude Code sessions.\"\nrisk: critical\nsource: \"https:\u002F\u002Fgithub.com\u002Fdmno-dev\u002Fvarlock\"\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## When to Use\n- You need to work with environment variables or secrets in a Claude Code session without exposing their values.\n- The task involves validating, loading, or auditing secrets while keeping them out of logs, diffs, and assistant context.\n- You want a secure-by-default workflow built around Varlock instead of direct `.env` inspection.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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## When to Use\n- You need to work with environment variables or secrets in a Claude Code session without exposing their values.\n- The task involves validating, loading, or auditing secrets while keeping them out of logs, diffs, and assistant context.\n- You want a secure-by-default workflow built around Varlock instead of direct `.env` inspection.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"version":26,"description":7},"critical","https:\u002F\u002Fgithub.com\u002Fdmno-dev\u002Fvarlock","1.0.0","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fvarlock",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill varlock",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill varlock",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill varlock","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fvarlock\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]