← ClaudeAtlas

bash-install-scriptlisted

Scaffold a self-contained, idempotent bash script that installs a tool/CLI/language/package. Use whenever the user wants an install or setup script written for some tool — phrasings like "write a bash installer for X", "add an install script for X", "scaffold a setup script for X", or "create an NN-install-*.sh script". Reach for this whenever the deliverable is a shell script whose job is to install something.
TomBorglum/wsl-cloud-init · ★ 0 · DevOps & Infrastructure · score 70
Install: claude install-skill TomBorglum/wsl-cloud-init
# bash-install-script Scaffold a new install script that installs one tool, following the conventions a robust install script shares: a strict header, fail-fast preconditions, an already-installed guard for idempotency, a clear root-vs-per-user execution context, and a self-contained install method. **One tool per script — always.** A bash install script installs exactly one tool; multi-tool scripts are not used. If you need to install another tool, give it its own `NN-install-<tool-name>.sh` script rather than bundling it here. The full convention list with annotated examples lives in `references/conventions.md` — read it before writing the script. ## Workflow 1. **Gather intent.** Confirm: - The tool name. - Its official install method: a curl-piped installer, an apt repository + key, a plain apt package, or a downloaded binary. Prefer the upstream-recommended method; when you need to confirm how a tool is installed, look it up via the Context7 MCP server (`resolve-library-id` → `query-docs`) rather than guessing. - That the method is **self-contained**: it installs only this tool, never a shared runtime (node/python/java) as a transient dependency. Prefer a native installer that bundles its runtime, or a standalone binary, over an `npm -g` / `pip` / `apt nodejs` style method. If the tool needs a runtime, that runtime is a separate concern (its own install script) — do not install it here. See `references/conventions.md`