Find a rig

On the Hub

Browse userig.xyz. The home page surfaces featured rigs; /use-cases groups them by purpose (research, ops, content, code review, …); /search lets you filter.

Every Hub page shows the rig's manifest (so you can see what it needs before installing) and a README rendered from the artifact.

From the CLI

rig hub search market

Returns matching author/name pairs with descriptions. The query is matched against name, author, and description. Examples:

rig hub search "competitive intelligence"
rig hub search news
rig hub search dylan/

The CLI hits the same endpoint as the website (GET /api/v1/packages?q=…).

What to look at before installing

A published rig is a snapshot of someone's workspace, plus a manifest. Before you install one you didn't write, glance at:

• The manifest — what env vars, MCP servers, tools, and plugins it expects. The Hub page shows this; from the CLI you can also rig inspect hub:author/name (see Inspect) without installing.
• Required tools — anything in [tools] that you don't have installed (e.g. uvx, a specific language runtime) you'll need to install yourself. Rig won't install language runtimes for you.
• Permissions — what Claude Code allow/deny rules the rig will write into your .claude/settings.json. Documented in [permissions].
• Install hooks — if [install].commands is non-empty, those are shell commands the rig will offer to run during rig install. Read them.

Next

• Install it.
• Source specifiers (where else rigs can come from).