environment-setup — Claude Code skill: sort out .env and app config
A skill for app configuration: which values belong in .env, what gets committed, how to validate required variables, and where secrets stop being your problem.
npx skills add akillness/jeo-skills --skill environment-setup -a claude-codeWhat environment-setup does
This one handles application config, not whole-machine reproducibility. It starts by sorting your request into a category: env file layout, validation, secret handoff, public/private split, drift cleanup, or framework-specific rules. Then it picks exactly one mode for the run instead of trying to cover everything at once.
You get back an Environment Config Brief: the chosen mode and why it fits, the current config surface with the main risk, a recommended file layout, example bash checks, and a watch-outs list. Two reference files ship with it — references/env-patterns.md and references/scope-boundaries.md — worth opening on unusual cases. It can use Bash, Read, Write, Edit, Glob and Grep.
The boundaries are the point. When the real blocker is toolchains, Docker Compose, devcontainers or onboarding, it hands off to system-environment-setup; deployment and CI secret wiring go to deployment-automation, security architecture to security-best-practices. So don't expect Docker guidance here — that's a different skill's job.
What it helps with
- lay out
.env.exampleand.env.localso newcomers stop guessing values - check required environment variables before the app boots
- keep client-exposed values from leaking into the bundle
- collapse templates, CI variables and docs into one source of truth
- record where each secret comes from: local file, secret manager, CI or cloud
Example prompts for the agent
- Help me structure
.env.exampleand.env.localso new devs don't have to guess values - Add typed validation for required environment variables at app startup
- Our local, staging and CI configs have drifted apart — find the mismatches and leave one source of truth
How to install environment-setup
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill environment-setup -a claude-code2Manually: put the files in place
~/.claude/skills/environment-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/environment-setup/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill environment-setup -a codex2Manually: put the files in place
.agents/skills/environment-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill environment-setup -a cursor2Manually: put the files in place
.cursor/skills/environment-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills environment-setup2Manually: put the files in place
.github/skills/environment-setup/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill environment-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/environment-setupManually: put the files in place
.devin/skills/environment-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill environment-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about environment-setup
How do I install environment-setup in Claude Code?
Run npx skills add akillness/jeo-skills --skill environment-setup -a claude-code. The skill then lives at ~/.claude/skills/environment-setup/SKILL.md.
What does environment-setup do?
It organizes application configuration: env file structure and precedence, validation of required values, separation of public and private variables, secret handoff, and drift between environments.
How is environment-setup different from system-environment-setup?
This skill covers app-level config: env files, config layering, validation schemas, secret boundaries. system-environment-setup covers whole-machine reproducibility: toolchains, Docker, devcontainers, local services. Docker and onboarding work gets routed to the latter.
