cli-tools

Detect missing CLI tools and install them via multiple package managers.

51|13|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/netresearch/claude-code-marketplace --skill cli-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-tools
Source: https://github.com/netresearch/claude-code-marketplace/tree/main/skills/cli-tools
Command: npx skills add https://github.com/netresearch/claude-code-marketplace --skill cli-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates automatic CLI tool management by detecting missing tools, choosing optimal installation methods, auditing environments, and batch-updating toolchains across multiple package managers. It reduces friction and keeps development environments consistent.

Core Features & Use Cases

  • Reactive Tool Resolution: Detects missing commands and installs them on demand to keep workflows smooth.
  • Proactive Environment Auditing: Scans project setups and reports missing or outdated tools.
  • Maintenance & Upgrades: Applies bulk updates to all tracked tools, ensuring tools stay current.
  • Use Case: On a new project, run a quick audit to ensure essential tools like ripgrep, fd, and jq are present and up-to-date.

Quick Start

Run the CLI Tools installation workflow for a sample project:

  • Install common tools with: ./scripts/install_tool.sh ripgrep
  • Audit your environment: ./scripts/check_environment.sh audit .

Frequently Asked Questions about cli-tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically detect and install missing CLI tools in my development environment?

This Skill detects missing commands and installs them on demand using catalog-driven methods across package managers like npm, pip, brew, apt, cargo, and uv. Run the audit workflow to identify gaps, then execute reactive installation to restore availability without manual setup.

Can I audit my project for missing or outdated tools across multiple package managers?

Yes, the proactive environment auditing feature scans your project setup, reports missing or outdated tools tracked in its 74+ tool catalog, and works across npm, pip, brew, apt, cargo, uv, and GitHub release binaries to give you a complete environment health report.

What's the best way to batch-update all CLI tools in my development toolchain?

Use the maintenance workflow to apply bulk updates across all tracked tools via their respective package managers. The Skill handles reconciliation and optimal method selection, keeping your entire toolchain current without manual per-tool updates.

How does tool installation work when multiple package managers are available?

The Skill applies a reconciliation workflow that detects your project type and environment, then chooses the optimal installation method from available managers—GitHub releases, uv, cargo, npm, apt, brew, or pip—based on tool availability and PATH handling requirements.

Can I use this Skill in automated workflows or coding agent environments?

Yes, it's designed for reactive missing-tool resolution and proactive auditing in coding agent workflows. Dependencies on jq and curl enable integration into automation pipelines for consistent environment setup across systems and batch operations.

Does this work for tools distributed as GitHub release binaries, or only package managers?

It supports both: GitHub release binaries are handled alongside traditional package managers like npm, pip, brew, apt, and cargo, giving you unified tool management regardless of how each tool is distributed.