installing-cli-tools

# Installing CLI Tools ## Overview Use this skill to take a CLI from "not installed" to "usable and verified" without exposing credentials in chat, logs, shell history, or repo files. Treat installation and secret setup as separate phases. ## Workflow 1. Identify the exact CLI, target OS/architecture, intended use, and whether authentication is required. 2. Check current state with narrow commands such as `command -v tool`, `tool --version`, package-manager queries, and existing config file paths only when needed. 3. Research current official installation docs before acting unless the user supplied an exact trusted source. Prefer official docs, package registry pages, signed release notes, or the upstream GitHub release. 4. Choose the least surprising install method: - Existing project manager (`brew`, `npm`, `pipx`, `uv tool`, `cargo install`, `go install`) when official and maintained. - Vendor installer only when it is the official path and its behavior is understood. - Manual binary install only after verifying architecture, checksum/signature when available, permissions, and destination. 5. Install to a user-writable, reversible location when possible. Avoid `sudo` unless the install path truly requires it and the user has agreed. 6. Wire PATH/completions only as narrowly as needed. Never edit shell startup files to add secrets. 7. Configure authentication through a safe channel. 8. Verify with `tool --version`, `tool doctor` or equivalent, and a non-destruc...