CLI Reference#

The Loot Protocol CLI (loot) lets you discover, install, publish, and maintain extensions directly from your terminal.

Installation#

The CLI is a single self-contained binary. Install it one of three ways:

# Homebrew (macOS / Linux)
brew install lootprotocol/tap/loot

# Go install
go install github.com/lootprotocol/lootprotocol/cmd/loot@latest

Or download a prebuilt binary for your platform from the GitHub Releases page.

Verify the installation:

loot --version

Configuration#

The CLI stores its configuration at ~/.lootprotocol/config.json. This file holds your authentication tokens and API URL. You should not need to edit it manually.

Default API URL: https://lootprotocol.com/api

Command Overview#

loot login#

Authenticate with Loot Protocol using your GitHub account.

loot login

Opens your default browser and redirects you to the GitHub OAuth flow via Cognito. Once you authorize, the CLI stores your access and refresh tokens locally at ~/.lootprotocol/config.json. If you are already logged in, it prints your current identity and exits.

Notes:

• Authentication is required for learn, publish, uninstall, link-repo, and sync
• search and info work without authentication (the catalog is public)

loot logout#

Clear your stored credentials.

loot logout

Removes the tokens from ~/.lootprotocol/config.json. Run loot login again to re-authenticate.

loot search#

Search for extensions on the marketplace.

loot search <query> [options]

Arguments:

Options:

Examples:

loot search "code review"
loot search "testing" --category testing-qa --limit 5

Output:

┌──────────────────────┬─────────┬──────────────────────────────────────┬───────────┐
│ Name                 │ Type    │ Description                          │ Downloads │
├──────────────────────┼─────────┼──────────────────────────────────────┼───────────┤
│ code-review          │ skill   │ Thorough code review with best...    │ 1,204     │
│ test-author          │ skill   │ Writes behavior-focused tests for... │ 512       │
└──────────────────────┴─────────┴──────────────────────────────────────┴───────────┘
 
Showing 2 of 2 results.

loot info#

Show detailed information about a specific extension.

loot info <slug>

Arguments:

Example:

loot info code-review

Displays the extension's name, type, publisher, version, download count, category, tags, description, and install command.

loot validate#

Validate a skill package locally without publishing it. Runs the same validation logic the server uses, giving you fast feedback.

loot validate [path] [options]

Arguments:

Options:

Examples:

# Validate current directory (auto-detect type)
loot validate
 
# Validate a specific directory
loot validate ./my-skill
 
# Validate with an explicit type
loot validate ./my-skill --type skill

Notes:

• No authentication is required; validation runs entirely locally
• If a directory is provided, the CLI packages it as a .tar.gz in memory before validating

loot learn#

Download and install an extension. Aliased as loot install.

loot learn <slug> [options]

Arguments:

Options:

Examples:

loot learn code-review
loot learn @shamsheg/hello-world --cursor

Behavior:

The CLI downloads the skill archive (via an authenticated S3 pre-signed URL) and extracts it to the skills directory:

• Claude Code: ~/.claude/skills/<slug>
• Cursor: ~/.cursor/skills/<slug>

Notes:

• Authentication required. Run loot login first
• Restart your Claude Code (or Cursor) session after installing so it picks up the new extension

loot uninstall#

Remove an installed extension.

loot uninstall <slug> [options]

Arguments:

Options:

This deletes the installed skill directory.

loot list#

List the extensions you've installed. Aliased as loot ls.

loot list [options]

Options:

Examples:

loot list
loot list --type skill
loot list --json

loot publish#

Package and publish a skill to the marketplace.

The CLI publishes skills. MCP server support is coming soon. See the Publishing Guide.

loot publish [path] [options]

Arguments:

Options:

Behavior:

1. If the path is a directory, packages it as a .tar.gz archive
2. Runs local validation (same rules as the server)
3. If validation passes, prompts for metadata (display name, category, tags) -- unless --non-interactive is set
4. Uploads the archive and metadata to the API
5. The server re-validates and stores the package
6. Prints the extension URL and install command

Skip prompts with lootprotocol.json:

{
  "type": "skill",
  "displayName": "Code Review Assistant",
  "category": "development-tools",
  "tags": ["code-review", "quality", "best-practices"]
}

Notes:

• Authentication required. Run loot login first
• Any user who publishes automatically becomes a publisher
• Re-publishing from the same skill directory creates a new version; previous versions are retained

loot link-repo#

Link a GitHub repository to an extension so new releases publish automatically.

loot link-repo <extension-slug> <github-repo-url>

Example:

loot link-repo code-review https://github.com/janedev/code-review

Once linked, new releases in the repo are auto-published as new versions. Use loot sync to trigger a publish on demand.

Notes:

• Authentication required. You must own the extension.

loot sync#

Manually trigger a sync from an extension's linked GitHub repo.

loot sync <extension-slug>

Example:

loot sync code-review

The CLI kicks off the sync and polls until it completes, then prints the version that was published.

Notes:

• Authentication required. The extension must already be linked with loot link-repo.

Global Options#

These options are available on all commands:

loot --help
loot search --help

Exit Codes#