Agent skill
cli-tools
Agent Skill: CLI tool management. Use when commands fail with 'command not found', installing tools, or checking project environments. By Netresearch.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/cli-tools-netresearch-cli-tools-skill
SKILL.md
CLI Tools Skill
Manage CLI tool installation, environment auditing, and updates.
Capabilities
- Reactive: Auto-install missing tools on "command not found"
- Proactive: Audit project dependencies and tool versions
- Maintenance: Batch update all managed tools
Triggers
Reactive (auto-install):
bash: <tool>: command not found
Proactive (audit): "check environment", "what's missing", "update tools"
Workflows
Missing Tool Resolution
- Extract tool name from error
- Lookup in
references/binary_to_tool_map.md(e.g.,rg→ripgrep) - Install:
scripts/install_tool.sh <tool> install - Retry original command
Environment Audit
scripts/check_environment.sh audit .
Scripts
| Script | Purpose |
|---|---|
install_tool.sh |
Install/update/uninstall tools |
auto_update.sh |
Batch update package managers |
check_environment.sh |
Audit environment |
detect_project_type.sh |
Detect project type |
Catalog (74 tools)
Core CLI, Languages, Package Managers, DevOps, Linters, Security, Git Tools
References
references/binary_to_tool_map.md- Binary to catalog mappingreferences/project_type_requirements.md- Project type requirements
Contributing: https://github.com/netresearch/cli-tools-skill
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?