Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cli-discover
Discover which CLI tools are installed, their versions, and authentication status
Passed 3 of 19 test cases with the skill, and 1 of 19 without it.
2 fixed1 passed either way19 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
When you need to discover what CLI tools are available on the system, use host_bash to check directly. Do not use sandboxed bash for discovery - it may not see host-installed CLIs or auth state, leading to false negatives.
which <name> # returns path if found, exits non-zero if missing
command -v <name> # alternative, works in all POSIX shells
<name> --version # most CLIs support this flag
Use a 5-second timeout to avoid hanging on unresponsive CLIs.
For CLIs that support authentication, check whether the user is logged in:
| CLI | Auth check command |
|---|---|
gh | gh auth status |
aws | aws sts get-caller-identity |
gcloud | gcloud auth list --filter=status:ACTIVE --format=value(account) |
az | az account show |
vercel | vercel whoami |
netlify | netlify status |
fly | fly auth whoami |
heroku | heroku auth:whoami |
railway | railway whoami |
When doing a broad discovery, check these categories:
gh, git, gitlabtest cases passed, vs 1 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.