From dev
List environment variable keys without exposing their values. Use when the user wants to see what environment variables are available, check if a specific environment variable exists, or list environment variables matching a pattern. IMPORTANT - This skill only reads keys (names), never values.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev:read-env-keyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
List environment variable keys without exposing their values. This skill provides safe access to environment variable names only.
List environment variable keys without exposing their values. This skill provides safe access to environment variable names only.
Current environment variable keys:
!env | cut -d= -f1 | sort
Use shell commands to list environment variable keys:
env | cut -d= -f1 | sort
To filter keys by pattern (case-insensitive):
env | cut -d= -f1 | grep -i <pattern> | sort
Examples:
env | cut -d= -f1 | grep -i GIT | sort - List all keys containing "GIT"env | cut -d= -f1 | grep -i GITHUB | sort - List all keys containing "GITHUB"env | cut -d= -f1 | grep -i TOKEN | sort - List all keys containing "TOKEN"To check if a specific environment variable key exists:
if [ -n "${KEY_NAME+x}" ]; then echo "✓ KEY_NAME exists"; else echo "✗ KEY_NAME does not exist"; fi
Or using printenv:
if printenv KEY_NAME > /dev/null 2>&1; then echo "✓ KEY_NAME exists"; else echo "✗ KEY_NAME does not exist"; fi
Examples:
if [ -n "${CODEMATE_GITHUB_TOKEN+x}" ]; then echo "✓ CODEMATE_GITHUB_TOKEN exists"; else echo "✗ CODEMATE_GITHUB_TOKEN does not exist"; fiif printenv API_KEY > /dev/null 2>&1; then echo "✓ API_KEY exists"; else echo "✗ API_KEY does not exist"; fiThis skill is designed to ONLY read environment variable keys (names), never their values. This prevents accidental exposure of sensitive information like tokens, passwords, or API keys.
npx claudepluginhub boringhappy/codemate --plugin devScans project code for environment variables (Python os.getenv/os.environ, Node.js process.env, .env refs), generates documented .env.example templates, ensures .gitignore excludes .env files, outputs var list with acquisition instructions.
Analyzes environment variables in code, generates .env.example templates, validates configurations and types, documents variables with examples, and provides naming and security best practices.
Checks ~/.bashrc for credentials, API keys, passwords, and configuration values as the primary source before asking the user or looking elsewhere. Useful for security and preventing missing environment variables.