How do I install the Environments Manager skill?

Run npx skillmds@latest add melvynx/environments-manager in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Environments Manager safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Environments Manager?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Environments Manager free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Environments Manager?

melvynx (@melvynx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Environments Manager by melvynx — Agent Skill

Name: Environments Manager
Author: melvynx

File contents

Ask before writing. Use the host's question UI. Shared logic lives in scripts/*.sh; IDE configs only point at those files. Read a matching examples/ file before writing, then adapt.

Ask what a fresh worktree should do (multi-select): copy ignored env files; install deps; isolate or seed a data backend; run codegen. Capture extra project steps in one follow-up.
Ask the backend. PostgreSQL → postgresql.md. Convex → convex.md. None → skip isolation. Any other backend: research official docs and an in-repo example; do not guess CLI flags; summarize before editing.
Ask which IDEs to wire (Claude Code, Cursor, Codex). Generate scripts/ once. Then load claude.md, cursor.md, and/or codex.md for linking config only.

Required files: scripts/worktree-up.sh, scripts/worktree-down.sh, scripts/dev.sh (all must end in .sh). Put them on the source checkout, not only the current worktree.

Resolve paths as WORKTREE_PATH="${CODEX_WORKTREE_PATH:-${CURSOR_WORKTREE_PATH:-$(pwd)}}" and SOURCE_PATH="${CODEX_SOURCE_TREE_PATH:-${ROOT_WORKTREE_PATH:-}}". Claude: use WorktreeCreate, never SessionStart; the wrapper adds the worktree then runs worktree-up.sh with ROOT_WORKTREE_PATH — see claude.md. Hook wrappers must survive a missing /dev/tty, a wrong default Node version, and CLI prompts.

worktree-up.sh is idempotent: set -euo pipefail, cd to the worktree, then the selected steps in order. Prefer .worktreeinclude for Claude env copy. Detect the lockfile for install. Read resource names from env/config or setup metadata; never invent them from branch names. Provide a reset escape hatch via <PROJECT>_RESET_<RESOURCE>=1.

worktree-down.sh cleans only resources this setup created. Missing tools: print one line and exit 0.

dev.sh picks a free port from ${DEV_PORT_START:-3910}. Never hardcode a port.

Never commit or log secrets. Never embed multi-line programs in IDE config. Never destroy or import production data unless the user set an override env var. Put this guard in any import/replay helper:

assert_non_prod_ref() {
  case "$1" in
    prod|prod:*|prod/*|production|production:*|production/*)
      echo "refusing prod source: $1" >&2; exit 1 ;;
    *prod*|*production*)
      [ "${ALLOW_PROD_SOURCE:-0}" = "1" ] || { echo "looks like prod: $1" >&2; exit 1; } ;;
  esac
}

Expose Dev, typecheck, unit tests, and lint through the IDE; add E2E only if cheap.

After writing: bash -n the three scripts, git status --short, and parse generated TOML/JSON when those files exist.

---name: environments-managerdescription: Set up per-worktree environments for Claude Code, Cursor, or Codex. Use for worktree-ready repos, IDE environment config, worktree-up/down scripts, or dev.sh wiring.---Ask before writing. Use the host's question UI. Shared logic lives in `scripts/*.sh`; IDE configs only point at those files. Read a matching `examples/` file before writing, then adapt.1. Ask what a fresh worktree should do (multi-select): copy ignored env files; install deps; isolate or seed a data backend; run codegen. Capture extra project steps in one follow-up.2. Ask the backend. PostgreSQL → [postgresql.md](references/postgresql.md). Convex → [convex.md](references/convex.md). None → skip isolation. Any other backend: research official docs and an in-repo example; do not guess CLI flags; summarize before editing.3. Ask which IDEs to wire (Claude Code, Cursor, Codex). Generate `scripts/` once. Then load [claude.md](references/claude.md), [cursor.md](references/cursor.md), and/or [codex.md](references/codex.md) for linking config only.Required files: `scripts/worktree-up.sh`, `scripts/worktree-down.sh`, `scripts/dev.sh` (all must end in `.sh`). Put them on the source checkout, not only the current worktree.Resolve paths as `WORKTREE_PATH="${CODEX_WORKTREE_PATH:-${CURSOR_WORKTREE_PATH:-$(pwd)}}"` and `SOURCE_PATH="${CODEX_SOURCE_TREE_PATH:-${ROOT_WORKTREE_PATH:-}}"`. Claude: use `WorktreeCreate`, never `SessionStart`; the wrapper adds the worktree then runs `worktree-up.sh` with `ROOT_WORKTREE_PATH` — see [claude.md](references/claude.md). Hook wrappers must survive a missing `/dev/tty`, a wrong default Node version, and CLI prompts.`worktree-up.sh` is idempotent: `set -euo pipefail`, cd to the worktree, then the selected steps in order. Prefer `.worktreeinclude` for Claude env copy. Detect the lockfile for install. Read resource names from env/config or setup metadata; never invent them from branch names. Provide a reset escape hatch via `<PROJECT>_RESET_<RESOURCE>=1`.`worktree-down.sh` cleans only resources this setup created. Missing tools: print one line and exit 0.`dev.sh` picks a free port from `${DEV_PORT_START:-3910}`. Never hardcode a port.Never commit or log secrets. Never embed multi-line programs in IDE config. Never destroy or import production data unless the user set an override env var. Put this guard in any import/replay helper:```bashassert_non_prod_ref() { case "$1" in prod|prod:*|prod/*|production|production:*|production/*) echo "refusing prod source: $1" >&2; exit 1 ;; *prod*|*production*) [ "${ALLOW_PROD_SOURCE:-0}" = "1" ] || { echo "looks like prod: $1" >&2; exit 1; } ;; esac}```Expose Dev, typecheck, unit tests, and lint through the IDE; add E2E only if cheap.After writing: `bash -n` the three scripts, `git status --short`, and parse generated TOML/JSON when those files exist.

Frequently asked questions

Environments Manager