Validates current environment variables against .env.example requirements
Scanned 6/1/2026
Install via CLI
openskills install berkcangumusisik/claude-code-practices---
name: env-check
description: Validates current environment variables against .env.example requirements
user-invocable: true
allowed-tools: Bash Read
effort: low
---
## Environment Variable Check
1. Read requirements:
```bash
cat .env.example 2>/dev/null || cat .env.template 2>/dev/null
```
2. Check which are set in the current environment:
```bash
while IFS='=' read -r key _; do
[[ "$key" =~ ^#|^$ ]] && continue
if [[ -z "${!key}" ]]; then
echo "MISSING: $key"
else
echo " SET: $key"
fi
done < .env.example
```
3. Additional checks:
- DATABASE_URL: can it actually connect?
- API keys: correct format (prefix check)?
- URLs: valid format?
4. Output:
```
Environment Check:
✅ DATABASE_URL
✅ JWT_SECRET
❌ STRIPE_SECRET_KEY ← MISSING (required for payments)
⚠️ REDIS_URL ← Missing (optional, caching disabled)
Result: 1 required var missing - app will fail to start.
```
5. Suggest how to obtain missing variables.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...