Get started

Install Pace

Pace ships AI specialists for every role at your company. Two install paths, both first-class: Cowork (the Claude desktop app) for click-to-install, and the Claude Code CLI for terminal-driven flows. Same plugins, same end state, different surface.

Click to install

Cowork (desktop)

One link per plugin. Cowork opens, asks you to confirm. No terminal, no commands. Right path if you don't write code for a living.

Show me ↓ Run in terminal

Claude Code (CLI)

Three commands: register the marketplace, install the plugins your team uses, connect tools on first run. Right path if you live in the terminal.

Show me ↓

Cowork (click-to-install)

Cowork is the Claude desktop app: a graphical interface to the same plugin ecosystem Claude Code uses in the terminal. Same plugins, same end state, different surface. In Cowork you click a link instead of typing a command.

1. Install Cowork

Download from claude.com/product/cowork and sign in with your Anthropic account.

2. Click an install link per plugin

Each plugin has a deep link that opens Cowork and adds the Pace marketplace plus the plugin in a single step.

# Pattern
https://claude.ai/desktop/customize/plugins/new?marketplace=GoldenBerry-SO/Pace&plugin=<name>

# Examples
https://claude.ai/desktop/customize/plugins/new?marketplace=GoldenBerry-SO/Pace&plugin=sales
https://claude.ai/desktop/customize/plugins/new?marketplace=GoldenBerry-SO/Pace&plugin=marketing
https://claude.ai/desktop/customize/plugins/new?marketplace=GoldenBerry-SO/Pace&plugin=engineering

Cowork prompts you to confirm the install. Want a curated set per role? The team guides have one-click install buttons for sales, marketing, engineering, finance, and the rest.

Restart Cowork after the last install. The MCP servers (Slack, HubSpot, Notion, etc.) only register cleanly on a fresh app start. Quit the app completely (Cmd+Q on macOS), then reopen it. If your / menu doesn't show the new commands, this is almost always the fix.

3. Authorize connectors when prompted

The first time a skill needs an external tool (Slack, HubSpot, Notion, etc.), Cowork opens an OAuth window. Sign in once per service, approve the scope, and the connector stays authorized for every plugin that uses it.

Rolling Pace out to a non-technical team. Install Cowork on each user's machine and send them a shortlist of deep links for the plugins they need. Each person authorizes connectors against their own accounts, so HR sees only HR's HubSpot, sales sees only sales's HubSpot, and so on.

Claude Code (terminal)

If you live in the terminal, three commands get you the same end state Cowork does. No config files to edit, no API keys to manage.

1. Register the marketplace

One-time per machine. Tells Claude Code where to find Pace's catalog.

claude plugin marketplace add GoldenBerry-SO/Pace

Claude Code clones the GitHub repo and reads its marketplace.json. The marketplace registers as pace; you install plugins with the @pace suffix.

2. Install the plugins your team uses

Install one plugin per team or function. The router (pace) is optional but recommended; it's where your company-specific commands go.

# The router (company commands like /pace teach)
claude plugin install pace@pace

# Department plugins (install only what you use)
claude plugin install sales@pace
claude plugin install engineering@pace
claude plugin install data@pace
claude plugin install marketing@pace

Not sure which to install? See Picking plugins below, or jump to the team guides for role-based recommendations.

3. Connect your tools (on first use)

Plugins ship with connectors but they're not authorized yet. The first time you run a skill that needs Slack, HubSpot, Notion, or any other MCP server, Claude opens an OAuth flow in your browser. Sign in, approve, and the token is saved for next time.

For the full connector model (OAuth, self-hosted URLs, local stdio servers), see Connectors & MCP.

Picking plugins

Pace ships 50 plugins. Most teams install three to six. Two ways to pick:

By role

The team guides have starter sets for sales, marketing, engineering, data, product, design, finance, legal, operations, people, customer support, and productivity. Each guide lists the plugins to install and a sample week of commands.

By plugin

The plugin catalog shows every plugin with its skills, connectors, and intended audience. Browse it like an app store.

Installing more plugins isn't free: each one adds skills to your / menu and bytes to the agent's context. Start with the few that map to your weekly work and add more as you find gaps.

The `pace-tools` CLI

Pace ships a small Node CLI you can run with npx. It's a thin wrapper around claude plugin, useful when you want to install many plugins at once or script the setup for an onboarding flow.

# One-time: register the Pace marketplace with Claude Code
npx pace-tools marketplace add

# Install one or more plugins
npx pace-tools install sales
npx pace-tools install engineering data

# Browse the full catalog
npx pace-tools list

# See per-role starter sets
npx pace-tools teams
npx pace-tools teams sales

# What's installed?
npx pace-tools status

# Remove a plugin
npx pace-tools uninstall sales

Requires Claude Code. The CLI wraps claude plugin install, so the claude binary must be on PATH. If you only use Cowork, install through the deep links above instead.

Updating

Claude Code

Refresh the marketplace; reinstall plugins to pick up the new versions:

claude plugin marketplace update pace
claude plugin install <name>@pace      # reinstalls; picks up new version

Cowork

Cowork pulls plugin updates from the marketplace whenever you reopen the app or re-run a plugin install link. The exact in-app update UI is app-version dependent; see Cowork's docs for the current flow.

Pace CLI

npx pace-tools status     # what's installed + which marketplaces are registered

Re-run npx pace-tools install <name> after a marketplace refresh to upgrade a plugin.

Verifying it worked

Open a chat in Claude Code or Cowork and type /. You should see commands prefixed by the plugins you installed: /sales:call-prep, /engineering:standup, /pace:teach, etc. Type one and the corresponding skill takes over.

Connectors stay declared but not authorized until the first skill that needs them runs. That's by design: authorization is just-in-time, so a fresh install doesn't barrage you with OAuth windows you don't need yet.

Stuck? Open an issue at github.com/GoldenBerry-SO/Pace.