system-environment-setup — Claude Code skill: reproducible dev
A skill that makes a repo runnable on any machine: pinned runtimes, local services, containers, bootstrap scripts and setup diagnosis.
npx skills add akillness/jeo-skills --skill system-environment-setup -a claude-codeWhat system-environment-setup does
The skill walks the agent through a fixed intake: classify the setup surface, pick exactly one operating mode, then produce an environment brief with the recommended mode, current state, stack, commands and files, parity gaps and watch-outs. Two references ship with it — references/operating-modes.md and references/scope-boundaries.md — and the skill points to them for unusual cases.
Tool access is narrow: Bash, Read, Write, Edit, Glob, Grep. Nothing beyond that is requested, so in repos with tight agent permissions it is worth checking that file writes are allowed at all.
Scope boundaries are drawn on purpose. Questions about .env layout, variable precedence and schema validation go to the sibling environment-setup; CI/CD and deployment go to deployment-automation; secret-store policy pairs with security-best-practices. When the task is a single package install with no environment decision behind it, the skill itself suggests reaching for a narrower tool.
What it helps with
- get a repo running on a fresh machine without tribal knowledge
- pin runtime and tool versions to stop cross-machine drift
- bring up local databases, caches and queues next to the app
- write a bootstrap script and a setup check
- find out why docs, scripts and actual runtime behaviour have drifted apart
Example prompts for the agent
- Make this repo runnable on a new machine: pin the versions and add a first-run setup script
- Choose between Docker Compose and a devcontainer for this project and explain the tradeoff
- Local setup no longer matches production — diagnose it and list the remaining parity gaps
How to install system-environment-setup
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill system-environment-setup -a claude-code2Manually: put the files in place
~/.claude/skills/system-environment-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/system-environment-setup/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill system-environment-setup -a codex2Manually: put the files in place
.agents/skills/system-environment-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill system-environment-setup -a cursor2Manually: put the files in place
.cursor/skills/system-environment-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akillness/jeo-skills system-environment-setup2Manually: put the files in place
.github/skills/system-environment-setup/SKILL.md1Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill system-environment-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/akillness/jeo-skills --path .agent-skills/system-environment-setupManually: put the files in place
.devin/skills/system-environment-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add akillness/jeo-skills --skill system-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 system-environment-setup
How do I install system-environment-setup in Claude?
Run npx skills add akillness/jeo-skills --skill system-environment-setup -a claude-code. The skill file then lands at ~/.claude/skills/system-environment-setup/SKILL.md.
What does system-environment-setup do?
It guides the agent through environment setup for a repository: mode selection, a reproducibility stack, the commands and files to create, and diagnosis of drift. Output is a brief in a fixed structure that names the parity gaps.
How is it different from environment-setup?
This is the broader skill — toolchains, containers, local services, onboarding. Narrower .env questions, variable precedence and schema validation are handed off to environment-setup.