Shareable demos

Three terminal demos that explain getcli in one screenshot.

These are the stories that travel well: an agent bootstrapping itself, a single install surface across ecosystems, and a doctor command that catches a broken machine before the workflow falls apart.

Demo 01

Agent boots itself

Start with a blank shell, discover the missing tool, install it, and verify the environment without hand-holding.

$ getcli doctor
Doctor: environment
  path: configured
  installers: brew, npm, pnpm, cargo, uv, bun
  status: OK

$ getcli search github
github  GitHub CLI
  official repo: github.com/cli/cli
  install channels: brew, npm, binary

$ getcli install github --yes
Installing github ...
Done.

$ getcli doctor github
Doctor: github
  status: OK

Why it works

This is the story that sells getcli fastest: discover, install, verify, continue.

Demo 02

Cross-ecosystem install

One command surface across brew, npm, cargo, and direct binary installs. Agents do not have to remember vendor-specific syntax.

$ getcli install stripe --yes
Selected channel: npm
Installing @stripe/stripe-cli ...
Done.

$ getcli install terraform --yes
Selected channel: direct binary
Downloading terraform ...
Done.

$ getcli install feishu --yes
Selected channel: npm
Installing @larksuite/cli ...
Done.

Why it works

One interface, many ecosystems. That is easier to automate and easier to explain.

Demo 03

Doctor catches bad env

When the machine is broken, getcli tells you exactly what is missing before the agent burns time on a bad assumption.

$ PATH=/tmp/empty getcli doctor
Doctor: environment
  path: missing
  installers:
    - brew: no
    - npm: no
    - pnpm: no
    - cargo: no
    - uv: no
    - bun: no
  status: action required

$ getcli doctor github --json
{
  "status": "missing",
  "reason": "github CLI not installed"
}

Why it works

This is the reliability demo: it surfaces bad state early instead of failing downstream.

Use these demos everywhere

They are short enough for a README, clear enough for a launch post, and concrete enough for an agent to understand without guessing.

Browse CLI guides See the rubric