The official plugin marketplace

When you want to know which plugins crouter ships in its official marketplace, or how to install one, read this page because it lists each plugin with what it adds and what it needs on your machine.

The official marketplace is a git repository, crouton-labs/crouter-official-marketplace, that holds 15 plugins for crtr. Some add commands (crtr exa-search, crtr capture), and the rest add markdown documents that agents are shown when they become relevant. Each plugin installs on its own.

Add the marketplace

The installer that the first crtr opens (and crtr sys setup reopens) offers to register the marketplace and to install capture and exa-search from it. To do it by hand:

crtr pkg market add https://github.com/crouton-labs/crouter-official-marketplace.git
crtr pkg market browse crouter-official-marketplace

pkg market add takes --ref (default main) and --scope (user or project; the default is project when a project is available, otherwise user). pkg market browse lists every plugin with its version and description, and marks the ones you already have installed.

Install a plugin

Install by the ref <marketplace>/<plugin>:

crtr pkg plugin install crouter-official-marketplace/tsym

--scope user or --scope project picks where it goes. A plugin that adds commands has them live on your next crtr invocation. If the plugin declares an executable it needs (for example grove for dev) and that executable is not on your PATH, the install still succeeds and prints a warning with the install hint.

Manage what you have installed:

crtr pkg plugin list                                        # installed plugins
crtr pkg plugin show tsym                                   # manifest and documents
crtr pkg market update                                      # refresh the marketplace; also updates installed plugins from it
crtr pkg plugin update --name tsym                          # refresh one plugin
crtr pkg plugin disable tsym                                # keep it installed but hide it
crtr pkg plugin remove tsym

Plugins that add commands

Plugin	What it adds	What it needs
`capture`	`crtr capture`, which forwards to the Capture CLI: CDP screenshots, rendered-geometry measurement, HAR, accessibility trees, JS execution and site libraries.	The Capture CLI: `npm install -g @crouton-kit/capture`.
`tsym`	`crtr tsym`, which forwards to the tsym CLI: read a TypeScript codebase by symbol (outline, inspect, show, type) from the compiler's own resolution. It also ships two documents: one tells explore agents to map TypeScript with tsym first, and one points to `crtr tsym -h` when an agent is about to grep for a symbol.	The tsym CLI: `npm install -g @crouton-kit/tsym`.
`exa-search`	`crtr exa-search` with three commands: `web` (ranked pages with excerpts), `answer` (one answer with citations) and `contents` (clean text from URLs you already have).	An Exa API key, from the `EXA_API_KEY` environment variable or `~/.crouter/exa.key`. A call without one fails before any request is sent.
`bird`	`crtr bird`, which forwards to the bird CLI: read tweets, threads, replies and search on X/Twitter, and post or reply. It signs in with your browser's X cookies (Arc, Firefox or Chrome), so `tweet` and `reply` post publicly as you.	The bird CLI, built from `CaptainCrouton89/bird` (needs `bun`). The plugin's install hint has the steps.
`github-asset`	`crtr github-asset attach <file> --pr <number>`, which uploads a local file through GitHub's attachment flow and prints its permanent `user-attachments` URL. Use it to put a video or screenshot in a pull request.	The Capture CLI (`crtr capture`), the GitHub CLI `gh` signed in, and a running browser with CDP enabled that is signed in to GitHub. The command never launches a browser.
`dev`	Development workflow documents (pull-request writing, planning, specs, code-craft preferences, runtime verification), a `spec/requirements` agent kind, `crtr human pr review` (review a branch's diff against its base beside a companion agent), a `dev` lesson track in `crtr sys tutorial`, `crtr dev` for a repository's own generated commands, and `crtr dev grove` plus a bare `dev` command that forward to Grove. It also installs lifecycle hooks that manage Grove instances for nodes: they refuse a second resident root inside an instance, label it with the node id, and finish the instance when that node closes.	Grove, for the Grove commands and hooks: install it, then run `grove setup` in the repository.

The capture, tsym and bird plugins pass every argument straight through to the external binary. crtr capture -h shows the Capture CLI's own help, and the same holds for the other two.

Plugins that add documents

These plugins add markdown documents and no commands. Once installed, agents are shown each document when its delivery rule matches (see Documents and preferences); you can also read them with crtr canvas read <plugin>/<document>.

Plugin	What it contains
`ai`	Playbooks for building on LLMs: prompt and agent-context design, agent-facing interfaces (CLIs and tools), human-facing agent UI and UX, multi-agent orchestration, structured output, evals and quality gates, and testing agent-written code. It also adds a rule that applies when you edit prompt files.
`claude-authoring`	Guides to writing Claude Code artifacts: `CLAUDE.md` files, hooks, rules, skills, commands, and scripts.
`knowledge-capture`	Four working modes for saving what you learn: `collaborate` (think with a peer, no artifacts), `interview` (structured Q&A saved as markdown), `epiphany` (advisors with conflicting lenses, for a breakthrough) and `learn` (distill a session into a knowledge document).
`design-discovery`	A Socratic interview, run through `crtr human`, that questions you about how a product or feature should feel before anything is built.
`web`	Frontend knowledge: visual direction for customer-facing pages, interface design for dashboards and tools, UX heuristics, an interactive design workflow, HTML mockups for design review, a UX-consultant role, and frontend debugging.
`cloudflare`	Working with Cloudflare from a shell: Wrangler setup and deploys, the REST API with `curl`, finding endpoints in the OpenAPI spec, and the `llms.txt` doc index.
`vercel`	Working with Vercel from a shell: the Vercel CLI for deploy, dev and logs, the REST API with a bearer token, and docs discovery through `llms.txt`.
`railway`	Working with Railway from a shell: the Railway CLI for deploy, logs and environments, the GraphQL API with a project or account token, and docs discovery through `llms.txt`.
`fly`	Working with Fly.io from a shell: `flyctl` for launch, deploy, status and logs, the Machines API with a bearer token, and docs discovery. The plugin is named `fly` because a plugin name cannot contain a dot.

The four hosting plugins (cloudflare, vercel, railway, fly) document how to install and sign in to each provider's own CLI; installing the plugin does not install that CLI or hold any credential.

Add a plugin to the marketplace

The marketplace repository's README describes how a plugin is laid out and how to propose one. To write a plugin that is hosted somewhere else, see the plugin authoring guide.