# environment-setup

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 353 installs · ★ 50
- Author: akillness
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/akillness/jeo-skills/tree/HEAD/.agent-skills/environment-setup/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/environment-setup

## What it 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.

## Requirements
- Works with: Docker

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill environment-setup -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/environment-setup/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/environment-setup/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill environment-setup -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/environment-setup/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill environment-setup -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/environment-setup/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install akillness/jeo-skills environment-setup
```

2. **Manually: put the files in place**
- File: `.github/skills/environment-setup/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill environment-setup -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/environment-setup
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/environment-setup/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add akillness/jeo-skills --skill environment-setup -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/akillness/jeo-skills/tree/HEAD/.agent-skills/environment-setup/SKILL.md

## When to use it
- lay out `.env.example` and `.env.local` so 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
- Help me structure `.env.example` and `.env.local` so 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

## Similar
- [wizard](https://affpapa.org/en/nevibecode/skills/wizard.md) — skill · 553369 installs
- [hyperframes-cli](https://affpapa.org/en/nevibecode/skills/heygen-com-hyperframes-cli.md) — skill · 1300000 installs
- [setup-pre-commit](https://affpapa.org/en/nevibecode/skills/setup-pre-commit.md) — skill · 489289 installs
- [using-git-worktrees](https://affpapa.org/en/nevibecode/skills/using-git-worktrees.md) — skill · 217153 installs
- [finishing-a-development-branch](https://affpapa.org/en/nevibecode/skills/finishing-a-development-branch.md) — skill · 214439 installs
- [orca-cli](https://affpapa.org/en/nevibecode/skills/orca-cli.md) — skill · 353600 installs

From the same set: [akillness/jeo-skills](https://affpapa.org/en/nevibecode/by/akillness/jeo-skills.md) — 29 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md