Add a CLI

getcli is only useful if the catalog is accurate. This page explains how to submit a new manifest, what evidence reviewers expect, and why the bar is intentionally high.

How to submit a CLI

Create or update a manifest in manifests/ using the official repository as the source of truth.
Verify the commands, install paths, auth flow, and capability flags against the upstream docs or release notes.
Open a PR and fill out every field in the PR template. If a capability does not exist, say so explicitly.
Include evidence that another maintainer can reproduce the same result without guessing vendor-specific behavior.

Evidence required

Reviewers should be able to confirm the manifest from public sources, not only from the submitter's memory.

Source of truth

Link the official repository and the docs page that defines the CLI.

Install proof

Show the exact install commands for the supported channels and note any fallback.

Auth proof

Explain the browser-based path and the headless or CI path if one exists.

Capability proof

Document structured output, dry-run behavior, help output, and any skill support.

Why quality matters

Search quality

Bad manifests create bad registry results, which means broken discovery for users and agents.

Automation safety

The wrong auth or install advice causes agent runs to stall, prompt, or fail in CI.

Maintenance cost

High-quality manifests are easier to review, easier to update, and easier to trust later.

Required manifest fields

A strong submission should make these fields obvious in the PR and match the manifest data exactly.

Official repo: link the upstream repository and keep the owner explicit.
Install methods: list the default and any alternatives we should surface.
Auth path: include the interactive path and the headless or CI path if one exists.
Structured output: state whether --json exists and where it is used.
Dry run: state whether --dry-run or a preview mode exists.
Skills / support: note any official skill, extension, MCP, or agent integration.

Where to go next

If the manifest is ready, open a PR with the template filled out and link the relevant docs or release notes.

Browse the registry Review CLI guides Read the docs