Agent skill

Check Tools

by oaustegard in oaustegard/claude-skills

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities.

MITAuto-check passedDevelopment

Install Check Tools

skills CLI
$ npx skills add oaustegard/claude-skills --skill check-tools -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install oaustegard/claude-skills check-tools --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/oaustegard/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/check-tools .claude/skills/check-tools && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
check-tools
GitHub stars
150
Token cost
~641 tokens
SKILL.md length
232 words
Files
6 (incl. references, assets)
Skills in repo
66
Repo updated
First seen
Licence
MIT

At a glance

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities.

  • Verifying environments
  • SKILL.md covers When to use, Running it, Required vs. optional, by… and Files, plus 1 more section
  • Runs Shell scripts from its folder; calls bash
  • Troubleshooting dependencies

What it does

Check Tools is an agent skill from oaustegard/claude-skills. Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `CHANGELOG.md`, `README.md` and `assets/check-tools.sh`).

It sits in Development. It works with Python, Java, C++ and Git. The repository describes itself as: My collection of Claude skills. The licence is MIT.

When your agent uses it

  • Verifying environments
  • Troubleshooting dependencies

Example prompts

  • “Use the check-tools skill to validate development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities”
  • “/check-tools”

Requirements

  • Python 3
  • Node.js
  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit cf49d47. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Check Tools loads about 641 tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 232 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~641
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from oaustegard/claude-skills at commit cf49d47, republished under its MIT licence (© oaustegard). 232 words, ~641 tokens.

Download SKILL.mdSave it as .claude/skills/check-tools/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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

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

bash
# 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.

© oaustegard, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references, assets) in check-tools of oaustegard/claude-skills.

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

Open the folder on GitHubat commit cf49d47

Compare with similar skills

Check Tools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Check Tools compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Check Tools this skilloaustegard/claude-skills150—~641Automated safety check: PassMIT
Dbgtheodo-group/debug-that158—~2.5kAutomated safety check: PassMIT
Code Review Excellenceandrew-yangy/gru-ai155—~1.7kAutomated safety check: NotesMIT
Precheckayutaz/piper-plus230—~647Automated safety check: PassMIT
Run Testsayutaz/piper-plus230—~641Automated safety check: PassMIT
Sap Btp Business Application Studiosecondsky/sap-skills462—~2.7kAutomated safety check: PassGPL-3.0

Similar skills

  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    DevelopmentAuto-check: notes
  • Precheck

    ayutaz/piper-plus

    PR 作成前の lint + format + test 一括実行。引数で scope (python/rust/cs/go/js/cpp/all) を指定可能。未指定なら git diff から自動判定。

    230 GitHub stars~647 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Run Tests

    ayutaz/piper-plus

    piper-plus の各言語ランタイムのテストを実行します。引数 python/rust/cs/go/js/cpp/all で対象を選択。未指定なら git diff から自動判定。

    230 GitHub stars~641 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • This skill provides comprehensive guidance for SAP Business Application Studio (BAS), the cloud-based IDE on SAP BTP built on Code-OSS.

    462 GitHub stars~2.7k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed
  • SDK Implementation Guide

    macalbert/envilder

    Operational guide for implementing a new Envilder runtime SDK.

    138 GitHub stars~1.9k tokensUpdated 4 days ago
    Productivity & AutomationAuto-check passed

More from oaustegard/claude-skills

All 66 skills in this repo
  • Vega-Lite Interactive Charts

    oaustegard/claude-skills

    Builds interactive Vega-Lite charts from uploaded data: analyzes the fields, picks five to ten fitting chart types, and produces a React artifact with the data embedded inline.

    150 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Single-File HTML Composer

    oaustegard/claude-skills

    Builds self-contained single-file HTML pages such as reports, decks, postmortems, flowcharts and prototypes from a small spec using a bundled Python composer and templates.

    150 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • Declauding

    oaustegard/claude-skills

    Rewrites model-sounding prose into plain technical writing and checks that every claim survives, for PR text, docs, commit messages and similar drafts.

    150 GitHub stars~5.2k tokensUpdated yesterday
    Auto-check passed
  • Preact Developer

    oaustegard/claude-skills

    Guides building standards-based Preact apps with native-first choices, HTM syntax, import maps and vendored ESM, from single-file demos to larger builds.

    150 GitHub stars~4.6k tokensUpdated yesterday
    Auto-check passed
  • Bluesky Zeitgeist Sampler

    oaustegard/claude-skills

    Deprecated sampler that captures short windows of the Bluesky firehose, clusters trending terms and builds an HTML report; replaced by the browsing-bluesky skill.

    150 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Adversarial Review Before Shipping

    oaustegard/claude-skills

    Has a fresh-context adversary attack a blog post, recommendation, analysis brief or piece of code before you ship it, using a profile suited to that kind of artifact.

    150 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Check Tools

What does Check Tools do?

Validates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Check Tools is an agent skill from oaustegard/claude-skills.js, Java, Go, Rust, C/C++, Git, and system utilities.

When should I use Check Tools?

Check Tools fits situations like: verifying environments; troubleshooting dependencies.

How do I install Check Tools in Claude Code?

Run `npx skills add oaustegard/claude-skills --skill check-tools -a claude-code`. Or copy the skill folder (check-tools in oaustegard/claude-skills) into .claude/skills/check-tools in your project. Claude Code loads it when a task matches its description.

How do I install Check Tools in Codex?

Run `npx skills add oaustegard/claude-skills --skill check-tools -a codex`. Or copy the skill folder (check-tools in oaustegard/claude-skills) into .agents/skills/check-tools in your project. Codex loads it when a task matches its description.

Can I use Check Tools in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add oaustegard/claude-skills --skill check-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-tools, .gemini/skills/check-tools, .github/skills/check-tools and .opencode/skills/check-tools in your project.

What does Check Tools need to run?

Going by SKILL.md and its folder, Check Tools needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: Python 3; Node.js; A Bash shell.

Does Check Tools access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Check Tools safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Check Tools use?

Check Tools is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Check Tools use?

About 641 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.

What are the alternatives to Check Tools?

Skills that share tags, products or a category with Check Tools: Dbg (theodo-group/debug-that, 158 stars), Code Review Excellence (andrew-yangy/gru-ai, 155 stars), Precheck (ayutaz/piper-plus, 230 stars) and Run Tests (ayutaz/piper-plus, 230 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Check Tools?

oaustegard (a GitHub user) maintains it in oaustegard/claude-skills, which has 150 GitHub stars. The repository holds 66 skills in this directory. The repository was last updated on October 8, 2026.

Source: oaustegard/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.