agentleFS
Sign inStart free
oaustegardoaustegard/claude-skills/check-tools/SKILL.md

check-tools

Skill158 starsChanged 8 months agoMITView on GitHub

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.

The file

Create a free account to mount
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free