cli-discover

Discover installed CLIs, versions, and authentication status via command inspection.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill cli-discover-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-discover
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/cli-discover
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill cli-discover-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly determine which command-line tools are installed on your system, what versions they are, and whether you are currently authenticated so you don’t waste time trying commands that will fail.

Core Features & Use Cases

  • Install discovery: Identifies whether a CLI exists using which or command -v, avoiding false negatives from sandboxed bash.
  • Version detection: Retrieves version information via the tool’s standard --version flag with a short timeout to prevent hangs.
  • Authentication status checks: Runs provider-specific login checks (e.g., gh auth status, aws sts get-caller-identity, gcloud auth list, az account show) to report who you’re authenticated as.

Quick Start

Ask the agent to discover installed CLIs, report their versions, and include authentication status for tools like gh, aws, gcloud, and az.

Frequently Asked Questions about cli-discover

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

FAQPage Schema
How do I check CLI authentication status for cloud providers before running automation?

Checking CLI authentication status involves running provider-specific login commands like `gh auth status` or `aws sts get-caller-identity` to report your current authenticated identity and prevent failed automation attempts.

What is the best way to discover installed command-line interfaces and their versions?

Discovering installed command-line interfaces uses `which` or `command -v` to identify if a CLI exists, then probes for version information via the tool's standard `--version` flag with a short timeout to prevent hangs.

Why does my bash script fail to find a CLI that I know is installed?

Your bash script may fail to find a CLI due to sandboxed bash environments causing false negatives. Using host-level command inspection with `which` or `command -v` accurately determines tool availability.

Can I check login status for multiple infrastructure CLIs at once?

You can check login status for multiple infrastructure CLIs by running deterministic auth-check commands per tool, such as `gcloud auth list` and `az account show`, to verify who you are authenticated as across providers.

Does this approach work for checking tool availability in sandboxed environments?

Yes, checking tool availability in sandboxed environments works by using host-level command inspection with `which` or `command -v` to avoid false negatives and accurately detect installed command-line interfaces.