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
AI specialists for every role at your company.
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.
Works with
- Claude Code
- Cursor
- Gemini CLI
- Codex CLI
- VS Code Copilot
- Kiro
- OpenCode
- RovoDev
Click to install
Cowork (desktop)
One link per plugin. Cowork opens and asks you to confirm. Pick the team you're on:
See all 50 plugins → Run in terminal Full install docs →
Claude Code (CLI)
Three lines and you're in. Replace sales with whichever team you're on.
$ claude plugin marketplace add GoldenBerry-SO/Pace
Registers 50 plugins.
$ claude plugin install sales@pace
> Prep me for the Acme call. Who's it for
Pick the team you're on.
Every role gets a starter set: the plugins to install, the workflows that fit a typical week, and one-click install in Cowork. Click your team to see the brief.
- SalesPrep calls, run pipeline reviews, draft outreach.
- MarketingPlan campaigns, draft content, enforce brand voice.
- EngineeringStacked-PR shipping, code review, diagnosis, TDD.
- DataSQL drafting, anomaly digests, dashboards.
- ProductUser-research synthesis, specs, competitive briefs.
- FinanceMonth-end runbook, variance, journal entries.
- LegalNDA triage, contract review, compliance.
- OperationsCross-team digests, vendor review, runbooks.
- PeopleRecruiting pipeline, interview prep, offer letters.
- Customer SupportTicket triage, response drafts, escalation.
- ProductivityTask management, daily updates, project memory.
- DesignDefers to impeccable for frontend craft.
For engineering
A disciplined toolkit for shipping software.
Engineers get 34 engineering skills covering the full week: a stacked-PR workflow that gives shipping a shape (spec → implement → review → topr → next), plus careful-review, TDD, diagnose, security-review, and the rest.
01
The Foundation
Three layers stacked on Claude: a plugin per role, MCP connectors to the tools your team already uses, and the /pace router on top for the commands that match how your team actually works.
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
Fifty plugins. Each one is scoped to a single role; install only what your team uses. 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. The sales plugin talks to your HubSpot. The data plugin queries your Snowflake. The marketing plugin 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.
4Just say what you need
Skills auto-trigger from natural language. Say "prep me for my call with Acme" and the sales call-prep skill fires. Say "write a query for monthly active users by plan tier" and data's query writer takes over. For your team's own commands, use the /pace router: /pace teach, /pace standup, whatever you've authored.
05
What's New
-
Hello, Pace.
First version out the door. A curated AI specialist for every role at your company, plus the
/pacerouter for the commands that are specific to how your team actually works. Fifty plugins in the marketplace, multi-harness install (Claude Code, Cursor, Gemini, Codex, and 8 more), open source under Apache 2.0.
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.
Want it done for you? We handle end-to-end setup for companies: install, connector authorization across your stack, role-specific configuration, and team enablement.
How long does setup take?
Solo: 10 minutes to install plugins, then 5-15 minutes per connector for OAuth (HubSpot, Slack, Snowflake, etc.). Most teams are productive the same day.
For a whole company: planning + authorization + connector mapping + training is closer to a week if you do it yourself. We roll this out as a service in 2-4 days, including command authoring tuned to your team's workflows and a training session.
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.
If your stack spans 10+ tools across the company, the authorization sprawl gets old fast. We handle connector setup as part of rolling Pace out across a team.
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.
Most companies don't write their own commands from scratch. We do this as a service: interview your team, codify how you actually work into /yourco commands, and hand back a fork that fits your operation. Train + enable, then maintain as your playbook evolves.
Can someone do this for us?
Yes. We offer end-to-end adoption for companies that want Pace working across their team without spending engineering time on rollout. A typical engagement covers:
- Install + connector authorization across your stack (HubSpot, Slack, Snowflake, Notion, your ATS, your CRM, whatever else)
- Per-role configuration: which plugins each team installs, which workflows fire automatically, which routines fit your calendar
- Command authoring:
/yourcorouter commands tuned to how your team actually ships, sells, closes, hires - Team training: a session per role plus a written playbook
- Ongoing support: monthly check-in, new commands as your playbook evolves, fixes when something breaks
Email hello@goldenberry.so for a scoping conversation.
What does it cost?
Pace itself 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 never charges and never paywalls plugins.
If you want us to roll Pace out for you (install, authorize, configure, author custom commands, train your team), that's a paid engagement, scoped to your team size and stack. Reach out for pricing.
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 cookbook.
Bring Pace to your company.
We help companies adopt Pace end-to-end: install + connector setup, command authoring tuned to your team's workflows, training, and ongoing enablement as your playbook grows.
Pace itself is Apache 2.0 and open source. see it on GitHub if you want to read the code or self-host.