Development

CLI Tools

Automatic CLI tool management for coding agents. Detects missing tools from 'command not found' errors and installs via optimal package managers. 100+ tool catalog (ripgrep, fd, jq, docker, terraform, etc.), project environment auditing, batch updates across Python, Node, Rust, Go, PHP, Ruby.

Install

Choose a supported route below. Package contents, agent registration and runtime dependencies can differ between installers.

  1. Claude Code via this marketplace
    /plugin install cli-tools@netresearch-claude-code-marketplace

    First add the marketplace once in Claude Code: /plugin marketplace add netresearch/claude-code-marketplace. Then install the selected plugin. For setup and installation scopes, see Claude Code plugin setup A plugin can include several skills and additional components.

  2. npx interactive skill selection
    npx skills add https://github.com/netresearch/coding_agent_cli_toolset

    Requires Node.js 22.20+. Run from the target project, then choose the source skills and agents in the installer. Installs skill instructions. The audit and installer scripts live in the source repository and need separate setup: CLI setup and requirements Skill registration alone does not install Python, uv or the audited tools.

  3. composer skills:add PHP project, direct source
    composer skills:add netresearch/coding_agent_cli_toolset

    Install and activate netresearch/composer-agent-skill-plugin first; approve the selected source's skill registration. Registers instructions from the direct source. For the repository scripts and their runtime environment, follow CLI setup and requirements This route does not install the audited tools or their dependencies.

What you can do with it

  • Automatic CLI tool management for coding agents
  • Detects missing tools from 'command not found' errors and installs via optimal package managers
  • 100+ tool catalog (ripgrep, fd, jq, docker, terraform, etc.), project environment auditing, batch updates across Python, Node, Rust, Go, PHP, Ruby

What you get back

  • state: single-character/emoji indicator of status
  • tool: logical tool name
  • installed: local version display (auto-update and pin markers appear next to it)
  • latest_upstream: upstream version display
  • notes: detected installation method (e.g., uv tool, npm (user), apt/dpkg)
  • tool: logical tool name
  • installed: formatted local version display (may include timings)
  • installed_version: parsed semantic version of the local tool (when available)
  • latest_upstream: formatted upstream version display (may include timings)
  • latest_version: parsed semantic version of the upstream tool (when available)
  • installed_method: detected installation source (e.g., "uv tool", "npm (user)")
  • installed_path_resolved: realpath via which(1) (kept for backwards compatibility)
  • classification_reason: reason derived from classifying the which(1) path
  • installed_path_selected: path of the executable actually selected by the audit run
  • classification_reason_selected: reason string for the selected path's classification
  • upstream_method: source used for latest lookup (e.g., "github", "uv tool")
  • status: UP-TO-DATE, OUTDATED, NOT INSTALLED, or UNKNOWN

What it expects in your project

  • Python 3.14+
  • Network access to query GitHub/PyPI/crates.io/npm

Tags

  • development
  • productivity