agent-routing
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe…
Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.
$ npx -y skills add oaustegard/claude-skills --skill check-tools --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/check-toolsContext preview
The summary Claude sees to decide when to auto-load this skill.
Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.
name: check-tools description: Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies. metadata: version: 1.2.0
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.
# 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.
| 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`.
`tools` / `system` / `full` modes
installation instructions
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.
A collection of Claude skills distributed as a Claude Code plugin marketplace. Skills are primarily designed for the Claude.ai PaaS skill compute environment; mileage will vary if used as Claude Code Agent Skills.
Decide which model, effort level, and cascade shape each subagent gets, and how to keep improvement loops safe…
Cross-context adversarial review for deliverables before shipping. Use when producing blog posts, technical recommendations,…
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six…
Routes, triages, flags and rates a piece of text with a probability for every option: which department or queue a ticket goes to,…
Delegates work to a subagent or spawned session by writing only the task, while a PreToolUse hook pages the parent transcript…
Chooses how to launch subagents from Claude Code (the Agent tool, a Workflow script, or headless claude -p children) and runs a…