check-tools
SolidValidates development tool installations across Python, Node.js, Java, Go, Rust, C/C++, Git, and system utilities. Use when verifying environments or troubleshooting dependencies.
Install
Quality Score: 84/100
Skill Content
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
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.
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.
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).