Env setup
Skill Tibsfox/gsd-skill-creator/project-claude/skills/env-setup
Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.From its SKILL.md
npx -y skills add Tibsfox/gsd-skill-creator --skill env-setupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.4 KB, 287 tokens by cl100k_base, as published. Nobody here has run it
Environment Configuration
Non-Negotiable Rules
| Rule | Why |
|---|---|
| NEVER commit .env to git | Secrets persist in history forever |
| NEVER log secret values | Logs stored in plain text, forwarded |
| NEVER hardcode secrets | Source code is widely shared |
| ALWAYS use .env.example | Documents vars without exposing values |
| ALWAYS add .env* to .gitignore FIRST | Prevents accidental commit |
| ALWAYS validate config at startup | Fail fast, not hours into production |
.gitignore (add before creating .env)
.env
.env.*
!.env.example
*.pem
*.key
credentials.json
Naming Conventions
- UPPER_SNAKE_CASE:
DATABASE_URL,JWT_SECRET - Prefix by service:
DB_,REDIS_,AWS_ - Booleans:
ENABLE_CACHE=true(not 1/yes) - Feature flags:
FEATURE_*
Key Patterns
- No defaults for secrets — force explicit configuration
- Validate at startup with Zod/Joi/Pydantic, not at first use
- Unique secrets per environment — one leak shouldn't compromise all
- Rotate leaked secrets immediately — check git history, audit access logs
- Process env always wins — CI/CD overrides file-based config
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.