Check Tools - Development Environment Validator
Reports which development tools are installed and at what version, grouped by
ecosystem. Default behavior reports every tool without failing validation —
suited to diverse PaaS/container environments where only a subset of
ecosystems is expected to be present.
When to use
- Verifying a container or environment has the tools a task needs
- Troubleshooting a build failure that might be a missing dependency
- Documenting system requirements
- Onboarding: confirming a dev environment is ready
Running it
# Fast check with exit code (0 = all required core tools present)
bash assets/check-tools.sh
# Development tools only
bash assets/environment-diagnostic.sh tools
# System info: hardware, mounts, processes
bash assets/environment-diagnostic.sh system
# Complete diagnostic (tools + system + package inventories), written to a file
bash assets/environment-diagnostic.sh full /path/to/report.txt
check-tools.sh exits non-zero only when a required core tool (python3,
pip, node, npm, java, gcc, git, curl, awk, grep, gzip, tar, make, sed) is
missing. Every other tool is reported (✅ found / ⚠️ optional and missing) but
does not fail the run.
Required vs. optional, by ecosystem
| Ecosystem |
Required |
Optional |
| Python |
python3, pip |
python, uv, poetry, black, mypy, pytest, ruff |
| Node.js |
node, npm |
nvm, yarn, pnpm, eslint, prettier, chromedriver |
| Java |
java |
mvn, gradle |
| Go |
— |
go |
| Rust |
— |
rustc, cargo |
| C/C++ |
gcc |
clang, cmake, ninja, conan |
| Utilities |
git, curl, awk, sed, grep, gzip, tar, make |
jq, rg, tmux, yq, vim, nano |
Full per-tool version-check commands and installation notes live in
references/tool-categories.md.
Files
assets/check-tools.sh — fast validation script (exit codes, quick checks)
assets/environment-diagnostic.sh — comprehensive diagnostic with
tools / system / full modes
references/tool-categories.md — detailed per-tool breakdown and
installation instructions
Extending
The required/optional split lives in assets/check-tools.sh
(check_required_tool / check_optional_tool calls), not in this file — to
change which tools are required, edit the script.
1---2name: check-tools3description: Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.4metadata:5 source: https://skillmd.com/skills/oaustegard/check-tools6 version: 1.2.07---89# Check Tools - Development Environment Validator1011Reports which development tools are installed and at what version, grouped by12ecosystem. Default behavior reports every tool without failing validation —13suited to diverse PaaS/container environments where only a subset of14ecosystems is expected to be present.1516## When to use1718- Verifying a container or environment has the tools a task needs19- Troubleshooting a build failure that might be a missing dependency20- Documenting system requirements21- Onboarding: confirming a dev environment is ready2223## Running it2425```bash26# Fast check with exit code (0 = all required core tools present)27bash assets/check-tools.sh2829# Development tools only30bash assets/environment-diagnostic.sh tools3132# System info: hardware, mounts, processes33bash assets/environment-diagnostic.sh system3435# Complete diagnostic (tools + system + package inventories), written to a file36bash assets/environment-diagnostic.sh full /path/to/report.txt37```3839`check-tools.sh` exits non-zero only when a **required** core tool (python3,40pip, node, npm, java, gcc, git, curl, awk, grep, gzip, tar, make, sed) is41missing. Every other tool is reported (✅ found / ⚠️ optional and missing) but42does not fail the run.4344## Required vs. optional, by ecosystem4546| Ecosystem | Required | Optional |47|-----------|----------|----------|48| Python | python3, pip | python, uv, poetry, black, mypy, pytest, ruff |49| Node.js | node, npm | nvm, yarn, pnpm, eslint, prettier, chromedriver |50| Java | java | mvn, gradle |51| Go | — | go |52| Rust | — | rustc, cargo |53| C/C++ | gcc | clang, cmake, ninja, conan |54| Utilities | git, curl, awk, sed, grep, gzip, tar, make | jq, rg, tmux, yq, vim, nano |5556Full per-tool version-check commands and installation notes live in57`references/tool-categories.md`.5859## Files6061- `assets/check-tools.sh` — fast validation script (exit codes, quick checks)62- `assets/environment-diagnostic.sh` — comprehensive diagnostic with63 `tools` / `system` / `full` modes64- `references/tool-categories.md` — detailed per-tool breakdown and65 installation instructions6667## Extending6869The required/optional split lives in `assets/check-tools.sh`70(`check_required_tool` / `check_optional_tool` calls), not in this file — to71change which tools are required, edit the script.