Agent skill · luongnv89
dev-machine-setup
Set up or tune any dev machine, fresh or drifted, on macOS, Linux, or Windows: report what's missing, install only that, then fix PATH, duplicate runtimes, and shell config. Don't use for Dockerfiles, CI images, or single package installs.
What it needs
About 7k tokens when loaded.
What this skill does
Dev Machine Setup Bring any machine to a clean, ready-to-develop state — a factory laptop, a half-configured work box, or a daily driver that has drifted. Never a fresh-install-only script: phase 1 builds a gap report of what is missing and misconfigured, and every later phase acts only on that report. Gap-driven is the whole design. Each phase self-skips when its slice of the report is empty, so a re-run on an already-good machine installs nothing and still verifies — idempotent by construction. Self-contained: no external scripts repo is cloned. The shell config the skill deploys ships in assets/. This is an orchestrator. Per-OS command tables and per-phase detail live in references/, so only the current platform loads and the token budget stays on the machine in front of you. Modes Mode comes from the user's intent, not from machine state — a machine with gaps is not permission to fill them when the user only asked for a tune-up. Mode Selected by Runs ------ ------------- ------ setup (default) "set up this machine", "install my dev environment", "get this laptop ready" Phases 0 → 6 tune "just optimize what's there", "don't install anything, fix my setup", "why is claude not found" Phases 0, 1, 5, 6 only Tie-break: setup wins whenever the request mentions missing pieces at all — "verify what's missing and optimize it" is setup. Choose tune only when the ask is limited to what is already installed; still unsure once the gap report is on screen, ask once, before phase 3. tune skips phases 3 and 4 entirely — never bulk-install what the user did not ask for. Phase 5 may still install a package when that is the approved fix for a finding (e.g. uv for python-externally-managed). Approvals Read references/approvals.md before phase 2 — it holds the rules every phase runs under, in full. The four that must be in your head from the start: Additive — installs something absent. Nothing working can break. Batch-approvable per phase. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills luongnv89/dev-machine-setup