mcpField
C
check-tools

check-tools

github.com/oaustegardDevelopment15745 installsUpdated 1d ago
Repository

About check-tools

check-tools is a development environment validation skill for developers and teams checking whether an environment has the tools a task requires. It reports installed tools and versions by ecosystem, while only missing required core tools cause validation to fail.

Key features

  1. 01Check installed development tools
  2. 02Report tool versions by ecosystem
  3. 03Separate required and optional tools
  4. 04Run tools, system, or full diagnostics

Use cases

  1. 01Verify dependencies in a container
  2. 02Troubleshoot builds with missing tools
  3. 03Document system requirements
  4. 04Confirm a development environment is ready

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/oaustegard/claude-skills --skill check-tools

After installing, type/check-toolsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CHANGELOG.md
README.md
assets/
check-tools.sh
environment-diagnostic.sh
references/
tool-categories.md

Details

From the project README

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

EcosystemRequiredOptional
Pythonpython3, pippython, uv, poetry, black, mypy, pytest, ruff
Node.jsnode, npmnvm, yarn, pnpm, eslint, prettier, chromedriver
Javajavamvn, gradle
Go—go
Rust—rustc, cargo
C/C++gccclang, cmake, ninja, conan
Utilitiesgit, curl, awk, sed, grep, gzip, tar, makejq, 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.

Comments

Markdown supported