env-check
Skill1 starsChanged 9 months agoMITView on GitHub
Validate environment configuration and check required variables are set. Use when setting up projects, debugging configuration issues, or verifying deployment readiness.
- Reads credentials
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 144
Create .env from .env.example:
- Very specific: line 158
Use .env.local for personal settings
- Very specific: line 163
Use .env.ci or environment variables
- Distinctive: line 166
Never store production secrets in files
- Distinctive: line 167
Use secret management (AWS Secrets Manager, Vault, etc.)
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Environment Configuration Checker
Validate environment files and ensure all required variables are properly configured.
Arguments
$ARGUMENTS: Environment name -local,development,staging,production(optional - defaults to local)
Environment File Patterns
| Pattern | Priority | Usage |
.env.local | Highest | Local overrides (never committed) |
.env.development | High | Development environment |
.env.staging | Medium | Staging environment |
.env.production | Medium | Production environment |
.env | Low | Default/fallback values |
.env.example | Reference | Template with all variables |
Checks Performed
1. File Existence
# Check which env files exist
ls -la .env* 2>/dev/null
# Check for .env.example (required for documentation)
if [ ! -f ".env.example" ]; then
echo "WARNING: No .env.example file found"
fi2. Required Variables
Common Required Variables:
| Variable | Projects | Purpose |
DATABASE_URL | PostgreSQL projects | Database connection |
MONGODB_URI | MongoDB projects | MongoDB connection |
JWT_SECRET | All backends | Token signing |
AUTH0_* | Auth0 projects | Authentication |
NEXT_PUBLIC_API_URL | Next.js | API endpoint |
PORT | All backends | Server port |
Project-Specific Variables:
| Project | Required Variables |
| eruditiontx-services-mvp | MONGODB_URI, JWT_SECRET_KEY, JWT_ALGORITHM, JWT_ACCESS_TOKEN_EXPIRE_MINUTES |
| mathmatterstx-services | MONGODB_URI, JWT_SECRET_KEY, MINIO_* (for storage) |
| notaryo.ph | DATABASE_URL, NEXTAUTH_SECRET, NEXTAUTH_URL |
| bocs-turbo | Per-app configuration |
3. Variable Format Validation
# Check for empty values
grep -E "^[A-Z_]+=\s*$" .env
# Check for placeholder values
grep -E "(your_|changeme|TODO|FIXME|xxx)" .env
# Check URL format
grep -E "^.*_URL=" .env | while read line; do
value=$(echo $line | cut -d'=' -f2)
if [[ ! $value =~ ^https?:// ]]; then
echo "WARNING: Invalid URL format: $line"
fi
done4. Security Checks
# Check if secrets are not placeholder values
grep -E "(SECRET|KEY|PASSWORD)" .env | while read line; do
value=$(echo $line | cut -d'=' -f2)
if [[ ${#value} -lt 16 ]]; then
echo "WARNING: Secret appears too short: $(echo $line | cut -d'=' -f1)"
fi
done
# Check .gitignore includes .env files
grep -q "\.env" .gitignore || echo "WARNING: .env not in .gitignore"5. Compare with Example
# Get variables from .env.example
example_vars=$(grep -E "^[A-Z_]+=" .env.example | cut -d'=' -f1 | sort)
# Get variables from current .env
current_vars=$(grep -E "^[A-Z_]+=" .env 2>/dev/null | cut -d'=' -f1 | sort)
# Find missing variables
comm -23 <(echo "$example_vars") <(echo "$current_vars")Output Format
Environment Check: [project-name]
Environment: [local/development/staging/production]
Files Found:
.env.example (reference)
.env.local (active)
.env.development (available)
Required Variables:
DATABASE_URL SET
JWT_SECRET SET
API_KEY MISSING
Validation:
Empty values: 0
Placeholder values: 1 (API_KEY)
Invalid URLs: 0
Security:
Secrets length: OK
.gitignore: OK
Missing from .env (found in .env.example):
- STRIPE_SECRET_KEY
- SENDGRID_API_KEY
Recommendations:
1. Set API_KEY to a valid value
2. Add STRIPE_SECRET_KEY to .env.localAuto-Setup Mode
Create .env from .env.example:
# Copy example to local
cp .env.example .env.local
# Prompt user to fill in required values
echo "Please update the following variables in .env.local:"
grep -E "^[A-Z_]+=(|your_|changeme)" .env.example | cut -d'=' -f1Environment-Specific Tips
Local Development
- Use
.env.localfor personal settings - Never commit
.env.local
CI/CD
- Set variables in GitHub Secrets or CI platform
- Use
.env.cior environment variables
Production
- Never store production secrets in files
- Use secret management (AWS Secrets Manager, Vault, etc.)
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- ericboy0224/learn-docker-and-k8s★ 472same name
- uniskela/adhd-hub★ 5same name
- NinjaSln-labs/agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository125 other files it gives its agents.
- skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-native-skills/AGENTS.mdAGENTS.md
- address-sanitizerSkill
- aflppSkill
- algorand-vulnerability-scannerSkill
- algorithmic-artSkill
- ask-questions-if-underspecifiedSkill
- atherisSkill
- audit-context-buildingSkill
- audit-prep-assistantSkill
- autonomous-skillSkill
- aws-skillsSkill
- better-authSkill
- brainstormingSkill
- brand-guidelinesSkill
- burpsuite-project-parserSkill
- cairo-vulnerability-scannerSkill
- canvas-designSkill
- cargo-fuzzSkill
- changelog-generatorSkill
- claude-in-chrome-troubleshootingSkill
- cloudflare-skillsSkill
- code-maturity-assessorSkill
- codeqlSkill
- codex-skillSkill
- constant-time-analysisSkill
- constant-time-testingSkill
- cosmos-vulnerability-scannerSkill
- coverage-analysisSkill
- d3js-visualizationSkill
- db-resetSkill
- deep-researchSkill
- deploySkill
- dev-startSkill
- differential-reviewSkill
- dispatching-parallel-agentsSkill
- doc-coauthoringSkill
- doc-generateSkill
- documentationSkill
- docxSkill
- dwarf-expertSkill
- entry-point-analyzerSkill
- executing-plansSkill
- expo-skillsSkill
- finishing-a-development-branchSkill
- firebase-apk-scannerSkill
- fix-reviewSkill
- frontend-designSkill
- fuzzing-dictionarySkill
- fuzzing-obstaclesSkill
- git-automationSkill
- google-design-mdSkill
- guidelines-advisorSkill
- harness-writingSkill
- health-checkSkill
- huggingface-skillsSkill
- insecure-defaultsSkill
- internal-commsSkill
- interpreting-culture-indexSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

