Skills for every role
A plugin per department: sales, marketing, finance, legal, engineering, data, customer support, product, HR, ops, design. Install only what your team uses. Each plugin's skills auto-trigger when the work matches.
50 pluginsPace
Superpower your company with AI specialists for every role.
Sales prep their calls. Engineers review their PRs. Finance closes the month. Marketing ships campaigns. Each role gets Claude with the right skills loaded, connected to the tools they actually use, tuned to how your team works.
One marketplace, every department. Install only what your team uses. Add your team's own commands on top with the /pace router.
Works with
- Cursor
- Claude Code
- Gemini CLI
- Codex CLI
- VS Code Copilot
- Kiro
- OpenCode
- Pi
- Qoder
- RovoDev
- Trae
01
The Foundation
Pace gives Claude the right toolkit for whatever you're working on. Pick the skills that match your role, connect the tools you already use, and Claude can do real work in your context.
Connected to your stack
Plugins talk to Slack, HubSpot, Snowflake, Notion, Linear, and the rest through MCP. Claude reads your actual data and writes back to your actual tools, not invented examples.
Your toolsYour team's way
The /pace router sits on top. Codify how your team ships, reviews, onboards, and operates. Sub-commands grow as your playbook crystallizes.
Register the marketplace once, then install the plugins your team actually uses. See get started →
02
The Catalog
Pick the plugins your team actually uses. Each one installs independently, brings its own skills, and stays sized for a specific role. The /pace router on top is for your team's own commands.
Your team's commands
Codify how your team ships, reviews, onboards, and operates. /pace teach sets up project context once. Build commands as your playbook crystallizes.
Sales
Prospect, prep calls, manage pipeline, draft outreach, build battlecards.
Marketing
Draft content, plan campaigns, enforce brand voice, brief on competitors, report performance.
Engineering
Standups, code review, architecture decisions, incident response, tech docs.
Data
Write SQL, visualize, validate analyses, ship dashboards. Snowflake, Databricks, BigQuery.
Finance
Journal entries, reconciliation, statements, variance analysis, close support.
Legal
Contract review, NDA triage, compliance, risk assessment, templated responses.
Product Management
Specs, roadmaps, user research synthesis, stakeholder updates, competitive landscape.
Customer Support
Triage, draft responses, escalate, research context, build the knowledge base.
Operations
Vendor management, process docs, change management, capacity planning, compliance.
Human Resources
Recruiting, onboarding, performance reviews, comp analysis, policy guidance.
Productivity
Manage tasks, plan the day, build memory of recurring work. Slack, Notion, Linear, Asana.
Enterprise Search
One query across email, chat, docs, wikis. Cuts the tool-switching tax.
Design (UX)
Critique, design system management, UX writing, a11y audits, research synthesis, dev handoff.
Small Business
Payroll planning, month-end close, weekly briefs, growth campaigns. Owner-operator workflows.
Partner-built
Apollo.io, Common Room, Slack, Zoom, brand-voice. Each authored by its vendor.
External marketplace
Vanta, Miro, PlanetScale, Figma, Adobe, Box, S&P Global, and more. Referenced by git URL.
Browse the full plugin catalog →
Plugins are authored by their listed owners; Pace curates and bundles them. Full attribution →
03
The Case
Without shared vocabulary, every team teaches their AI the same things in different words, and gets back outputs that drift from how the company actually works. Pace is the fix: codify the way once, use it everywhere.
-
One vocabulary, many functions
Engineering, product, ops, and marketing share commands instead of inventing private dialects. The agent stops guessing what each team means.
-
Same shape across harnesses
Cursor, Claude Code, Gemini CLI, Codex CLI, and 8 more: Pace installs the same skill into each. One process, one set of reviews, one company.
-
Defers to specialists
For frontend code design (typography, color, layout, motion, accessibility, dev handoff in code), Pace defers to impeccable: a deep
/impeccablerouter with sub-commands across the design lifecycle, plus an anti-pattern detector that catches AI-generated design slop. Apache 2.0, multi-harness, ships alongside Pace. See how they pair → -
Codified, not memorized
Your way of working stops living in tribal knowledge and starts living in
skill/reference/. New hires and new agents pick it up the same way. -
Ships code and artifacts, not advice
Each command produces an actual output: a PR review, a spec doc, a runbook entry. No vague suggestions.
-
Open and forkable
Apache 2.0. Fork it for your company, contribute commands back.
04
Get Started
1Register the marketplace
One command registers all 50 plugins with Claude. You only do this once per project.
$ claude plugin marketplace add GoldenBerry-SO/Pace2Install the plugins you need
Pick what your team actually uses. A salesperson installs sales. An engineer installs engineering + data. Everyone can install the pace router for company-specific commands.
$ claude plugin install pace@pace # company router
$ claude plugin install sales@pace # /sales:* commands
$ claude plugin install engineering@pace # /engineering:* commands
$ claude plugin install data@pace # /data:* commandsBrowse the full catalog at /plugins. For frontend code design, install impeccable alongside.
Or use the pace-tools CLI
A thin wrapper around claude plugin that handles marketplace registration + multi-plugin install in one command:
$ npx pace-tools marketplace add
$ npx pace-tools install sales engineering data
$ npx pace-tools list # browse the catalog
$ npx pace-tools teams # per-role starter setsRequires the claude CLI on PATH (it wraps claude plugin install).
3Connect your tools
This is what makes Pace useful. /sales:* talks to your HubSpot. /data:* queries your Snowflake. /marketing:* drafts in your Canva. Each plugin's .mcp.json declares which MCP servers it integrates with, and Claude prompts you to authorize the first time. A plugin without its connectors can still do web research and work from pasted context, but the connected version is the version that does real work on your real data.
4Use the commands
Type /pace <cmd> for your team's commands. Type /sales:call-prep, /data:write-query, /marketing:campaign-plan for namespaced department commands. Skills also auto-trigger from natural language, so "prep me for my call with Acme" finds /sales:call-prep on its own.
05
What's New
-
Marketplace pivot
Pace becomes a curated Claude Code marketplace. Bundles first-party and partner-built plugins, references 27 external plugins by git URL, and keeps the
/pacerouter as the company-specific layer on top. New/pluginspage lists the full catalog with attribution per plugin. -
Initial scaffold
The Pace skill router lands as a lean fork of impeccable's install machinery: multi-harness build, Astro site shell, CLI installer with impeccable handoff. Router starts empty; commands ship as they're authored.
Track work in progress on GitHub.
06
Frequently Asked Questions
What is Pace?
Pace is a curated marketplace of AI skills for AI coding agents like Claude Code. Install the plugins your team actually uses (sales, marketing, finance, engineering, data, and more) and Claude turns into a specialist for each role, connected to the tools your team already uses.
How is this different from just using Claude on its own?
Out of the box, Claude is a strong generalist. Pace makes it a strong specialist: each plugin loads the domain knowledge for a role (how a sales call gets prepped, how a marketing campaign gets planned, how a SQL query gets validated) and connects to the tools that role actually uses (HubSpot, Canva, Snowflake).
The result is the difference between "Claude can help with sales" and "Claude prepped my Acme call by pulling the HubSpot history and recent Slack mentions while I was on my morning coffee."
Which plugins should I install?
Install the one or two that match your role:
- Salespeople:
sales+productivity - Marketers:
marketing+brand-voice - Engineers:
engineering+data - PMs:
product-management+data - Anyone:
productivity+enterprise-searchwork cross-role
See /docs/teams for the per-role guide with workflows and tips.
How do I install it?
From inside your Claude Code project:
claude plugin marketplace add GoldenBerry-SO/Pace
claude plugin install sales@pacePlugins install independently. Pick what you need; skip what you don't.
Do I have to connect my tools?
No, but you should. Every plugin works standalone: it falls back to web search and whatever context you paste in. With connectors, Claude reads your real data directly: HubSpot accounts, Snowflake tables, Notion docs, Slack threads.
Authorization happens on first use, per tool, via OAuth in your browser. You don't manage API keys. See how connectors work for the full flow.
Is my data safe?
Pace doesn't see or store your data. Plugins talk to your tools through MCP, which means the connection runs between Claude Code on your machine and the vendor (Slack, HubSpot, etc.). Nothing flows through pace.tools or any Pace infrastructure.
You authorize each connector individually via OAuth. You can revoke access at any time from the vendor's account settings.
How do I update?
From any installed project:
claude plugin update --allThat pulls the latest version of each installed plugin. New plugins added to the marketplace become visible automatically; install the ones you want.
Can we customize plugins for our company's specific workflows?
Yes. Two paths, depending on scope:
- Light: swap a connector for one that matches your stack (e.g. Salesforce instead of HubSpot). Skills resolve to whatever you authorize.
- Deep: fork the Pace repo for your company, edit the plugins, rename the router from
/paceto/yourco, and write commands specific to your team's process. GoldenBerry offers training and enablement for this; see the "Use Pace at your company" section below.
What does it cost?
Pace is free and open source (Apache 2.0). The plugins are free too. Some connectors require paid accounts on the vendor side (Snowflake, HubSpot, etc.), but Pace itself never charges and never paywalls plugins.
What about design?
For frontend code design (CSS, typography, color tokens, layout, motion, accessibility, UX writing, design systems, dev handoff in code), Pace defers to impeccable. Impeccable is a separate Apache 2.0 skill kit with one /impeccable router and a deep set of design sub-commands; it runs in every harness Pace runs in (Claude Code, Cursor, Gemini, Codex, and 8 more).
Pace's catalog also includes the design plugin, which covers the policy layer: UX research synthesis, design-system management at the spec level, accessibility audits as workflows, and dev handoff at the brief level. Use both: Pace's /design sets the rules; impeccable enforces them in the codebase.
Install impeccable alongside Pace; the Pace CLI offers it during setup, and there's a full Design section in our use cases cookbook.
Use Pace at your company
Pace is open source. Fork it, rename the router, and write the commands that match how your company works.
Need help rolling Pace out to your team?
GoldenBerry offers training and enablement: install + connector setup, command authoring for your company's workflows, and ongoing support as your playbook grows.
Get in touch