Better tools for
the agent you use.

Install the CLI

The CLI ships on npm as chops-sh and installs the chops command. No account required for public skills.

Prefer not to install anything? Every command below also works as npx chops-sh <command> — that’s the form skill pages use, and the right one for agents and CI.

Find by intent

Describe the outcome you want — Chops combines semantic and keyword relevance, so “make my queries faster” finds a skill described as “database query optimization.” Returns the top 10 matches.

Add the skill

Use the slug from a result (owner/repo@skill). Chops downloads the pinned package, checks its SHA-256 digest against the registry manifest, and only then links it into your agents. You’ll be asked to confirm first — pass --yes to skip.

Teams & private skills

Some skills shouldn’t be public — deploy runbooks, internal APIs, house style. Chops hosts those privately: @me/<name> for just you, @<team>/<name> for your team. Private skills are encrypted at rest and never appear in the public index or search.

Sign in without leaving the terminal — a one-time email code, no password, no browser:

Publish a skill directory privately (add --team to share it):

Create a team and invite teammates by email. Invites can be accepted from the browser or entirely in-terminal with chops team join:

Teammates install with the same verified flow as public skills — digest checked, linked into every agent:

Manage members, pending invites, and your team’s skill list at chops.sh/app/teams. Teams are free while in preview.

Commands & flags

The full surface — small on purpose.

How an install works

Five steps, each one inspectable afterwards:

1. The registry returns a manifest: your slug, the pinned content SHA, and the package’s SHA-256 digest.
2. The tarball is downloaded and rejected outright if its digest doesn’t match the manifest.
3. Contents unpack once into ~/.chops/store/<owner>/<repo>/<skill>@<sha>/.
4. That store path is symlinked into each selected agent directory (junctions on Windows).
5. The install is recorded in ~/.chops/chops.lock.

Published versions are immutable — packages are content-addressed and mirrored by the registry, so a force-pushed source repo can’t change what you already installed.

For coding agents

Chops is built to be driven by your agent, not just for it. Two rules: always --json, always --yes.

find --json returns each result’s slug, description, publisher, agent compatibility, stars, installs, last-published date, and pinned SHA — everything needed to explain a choice before installing. add --json returns { ok, slug, sha, store, links }. Failures print a JSON error and exit non-zero.

Headless: curl only

The entire read path is plain HTTP — an LLM (or anyone) can find and install skills with nothing installed. Search, read the manifest, download the tarball, check the digest, unpack:

The digest must equal the manifest’s sha256 — discard the download if it doesn’t. Tarballs are immutable and content-addressed. The API also documents itself: curl api.chops.sh returns an endpoint map, and api.chops.sh/llms.txt serves this whole workflow as plain text an agent can read directly.

Public registry API

Everything the CLI uses is a plain, unauthenticated HTTP API at https://api.chops.sh — build on it directly if you prefer.

Use it everywhere

Chops maintains one local copy and links it into supported agent directories — install once, available in every session.