cli-discover

Discover installed CLI tools and verify their authentication status.

1.0k|158|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/vellum-ai/vellum-assistant --skill cli-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-discover
Source: https://github.com/vellum-ai/vellum-assistant/tree/main/skills/cli-discover
Command: npx skills add https://github.com/vellum-ai/vellum-assistant --skill cli-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you quickly identify which CLI tools are available on the host and determine their authentication status, reducing manual checks and surprises during setup.

Core Features & Use Cases

  • CLI existence and version discovery: Detect whether a CLI is installed and retrieve its version information.
  • Authentication status checks: Verify login state for common CLIs (e.g., GitHub, AWS, GCP) to ensure tools are ready for use.
  • Use Case: When setting up a new developer workstation, run discovery to compile a master list of available CLIs and their auth states for onboarding.

Quick Start

Run the discovery to list installed CLIs and their authentication status.

Frequently Asked Questions about cli-discover

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

FAQPage Schema
How do I discover installed CLI tools and check their authentication status on a host?

To discover installed CLI tools and check authentication status, you need shell access to run standard commands like 'which', '--version', and auth status checks for popular CLIs. This provides a master list of available tools and their login states.

Can I verify CLI versions and login states across CI environments and containers?

Yes, you can verify CLI versions and login states across CI environments and containers by running discovery checks. It requires access to a real shell to audit system tool availability and confirm authentication readiness.

What is the best way to audit system tool availability during developer workstation onboarding?

The best way to audit system tool availability during workstation onboarding is to run a CLI discovery process. It compiles a master list of installed tools, retrieves version information, and verifies login states for common CLIs.

Does checking CLI authentication status require any special dependencies or components?

Checking CLI authentication status requires no special dependencies or components. It only needs access to a real shell using standard system checks like 'command -v' and specific auth status commands for popular CLIs.

Why does CLI discovery fail to detect installed tools in my environment?

CLI discovery fails to detect installed tools if there is no access to a real shell. The process relies on executing standard checks such as 'which' or 'command -v' and running '<name> --version' to accurately find and verify tools.