check-tools

Solid

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

Code & Development 146 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Check Tools - Development Environment Validator ## Core Philosophy Systematically verify tool presence and versions across major programming ecosystems. Provide actionable feedback about availability and validate complete toolchains with awareness of interdependencies (e.g., Node.js requires npm). ## Environment Compatibility This skill supports flexible validation modes: - **Strict mode**: Fail on missing core tools (python3, node, git, gcc) - **Lenient mode**: Report all tools but only warn on optional ones - **Custom mode**: Define required vs optional tools per project Default behavior reports all tools without failing validation, suitable for diverse PaaS environments. ## When to Use This Skill Trigger this skill when working on: - **Environment setup verification** - Validating that all required tools are installed - **Troubleshooting build failures** - Checking for missing dependencies or version mismatches - **Documentation generation** - Creating system requirements documentation - **CI/CD pipeline setup** - Ensuring container images have required tools - **Onboarding new developers** - Verifying development environment readiness - **Cross-platform development** - Checking tool availability across different operating systems - **Polyglot projects** - Validating toolchains for multiple programming languages ## Tool Categories ### 1. Python Ecosystem **Core Tools** (typically available): - `python3`, `python` - Python interpreters ✅ - `pip` - Package insta...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

toolcheck

Decide whether a specific software tool, GitHub repo, npm package, API, MCP server, plugin, or CLI is worth adopting, and answer in plain non-technical language with a fixed six-part card. Use this whenever the user is weighing up a named piece of software and asks anything like "is X any good", "should I use X", "is X worth it", "can I trust X", "X vs Y", "is this repo legit", "should I install this", "do I already have something like this", or pastes a GitHub / npm / product URL and asks what you think. Use it even when the user does not say the word "evaluate". Wanting to know if a named tool is a good idea is enough. Do not use it for general "what tool should I use for X" questions where no specific candidate has been named; that is open-ended research, not a fit check.

0 Updated 2 weeks ago
bhaor
AI & Automation Listed

security-tools

Quick local-environment verification for security analysis work. Runs the bundled `check.sh` script and reports whether the shell environment has the basics the security skills depend on. Invoke at the start of a security-focused session as a pre-flight.

1 Updated today
anttitevanlinna
Code & Development Listed

running-check-script

Single source of truth for running the package.json `check` script across lt-dev review and rebase workflows. Defines discovery (multi-package monorepo aware), the iterate-until-green auto-fix loop, the mandatory audit-finding fix escalation ladder, residual classification (Accepted vs Critical), test-duplication avoidance, and report formatting. Activates whenever an agent or command needs to validate runnability via `check` — currently used by `/lt-dev:review`, `code-reviewer`, `branch-rebaser`, and `test-reviewer`. NOT for general npm package maintenance (use maintaining-npm-packages). NOT for the rebase orchestration itself (use rebasing-branches).

0 Updated yesterday
lenneTech