cli-discover
cli-discover provides methods to detect installed command-line tools on a host system, retrieve their version information, and verify authentication status. Use this skill when you need to inventory available development tools, determine which cloud provider CLIs are authenticated, or check dependencies before executing automated workflows that require specific tools.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/cli-discover && cp -r /tmp/cli-discover/skills/cli-discover ~/.claude/skills/cli-discoverSKILL.md
# CLI Discovery 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. ## Checking if a CLI exists ```bash which <name> # returns path if found, exits non-zero if missing command -v <name> # alternative, works in all POSIX shells ``` ## Getting version info ```bash <name> --version # most CLIs support this flag ``` Use a 5-second timeout to avoid hanging on unresponsive CLIs. ## Auth-check commands 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` | ## Common CLIs worth checking When doing a broad discovery, check these categories: - **Version control & code hosting:** `gh`, `git`, `gitlab` - **Project management:** `linear`, `jira` - **Communication:** `slack` - **Cloud providers:** `aws`, `gcloud`, `az` - **Containers & infra:** `docker`, `kubectl`, `terraform` - **Runtimes & package managers:** `node`, `bun`, `deno`, `python3`, `pip3` - **HTTP clients:** `curl`, `httpie` - **Hosting & deploy:** `vercel`, `netlify`, `fly`, `heroku`, `railway` ## Output format Report findings in markdown: ```markdown ## Available CLIs - **git** (/usr/bin/git) - git version 2.x.x - **gh** (/usr/bin/gh) - gh version 2.x.x [authenticated: user@example.com] - **bun** (~/.bun/bin/bun) - 1.x.x ## Not found: jira, linear, slack ```
>
>
>
>
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.
Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.