Loading

How to customize plugins in Claude

Customize Anthropic's pre-built plugins with your team's tools, processes, and expertise so every skill runs from your context.

6 minClaude

In Claude, a plugin bundles the skills and connectors for a role into a single package. Anthropic publishes pre-built plugins for roles like Sales, Finance, Legal, and Marketing, each with skills for that role's common workflows.

Out of the box, those skills are generic templates. Customizing a plugin rewrites them with your team's tools, standards, and reference material, so the same skills produce work that matches how your team does it. Browse all plugins →

If you're new to Claude, /setup-claude walks you through setting up your first plugin and connectors. See Get started in three steps.

Start a customize session

Open your plugins, select the plugin, and choose Edit with Claude from its menu.

Loading

Claude looks through your connected tools — Slack, email, Drive — for signs of which systems your team uses, then asks you questions to confirm what it found and fill in what it couldn't. Once you answer, Claude rewrites the plugin's skills to reference your tools, adds the matching connectors, and packages the result for you to save.

The questions depend on the plugin and what's already in your workspace, so treat the session as a conversation — answer what's asked, and add anything else Claude should know about how your team works.

What to give Claude

Claude will ask which tools you use, and leave room for anything else. The tool answers wire the plugin to the right connectors; the anything else is where you describe how your team actually works.

  • Your tools. Pre-built skills reference tools generically — the CRM, the data warehouse. Naming yours maps each skill to the right connector, so /variance-analysis queries Snowflake and /call-prep reads from Salesforce without asking. If a connector you name isn't enabled yet, Claude lists it for you to connect later.
  • How your team works. The defaults and standards a new teammate would need to know — what you call things, what counts as done, when something gets escalated. The role examples below show what this looks like for each plugin.
  • Reference documents. Point Claude at examples of finished work — last quarter's close package, a brand guide, a redline that landed, your memo template. Claude reads them and writes the relevant patterns into the plugin's skills, so future output matches your formats.

Review what Claude built

When the session finishes, Claude shows a summary of what changed and the plugin as a file card in the conversation. A plugin is a folder of plain-text instruction files, and you can click through any of them to read exactly what a skill will do.

Click Save plugin to add it to your account. From here, editing is the same as customizing: open a session with the plugin and tell Claude what to change.

Keep improving it

You don't need to cover everything in the first pass. Run a skill, and when you spot something to adjust — a step to add, a format to match more closely — tell Claude in the same session: add this to the plugin so it's right next time. Claude updates the skill, and you save the plugin again to keep the change.

To see what's still generic, start another customize session and ask: what placeholders are left in this plugin?

Examples by role

Each role below shows the same three inputs — tools, how the team works, reference documents — and what the plugin's skills do once they're in place.

Sales

Connect: your CRM (like HubSpot or Salesforce) and call-recording tool.

Share: your qualification framework, deal stages, and competitive positioning.

Reference: proposals and outreach that landed well.

Result:

  • /call-prep now produces briefs using your framework and recent call context.
  • /forecast now weights pipeline by your stage probabilities.

Finance

Connect: your ERP or data warehouse.

Share: your chart of accounts, materiality thresholds, and close calendar.

Reference: last period's close package and your memo template.

Result:

  • /variance-analysis now decomposes by your drivers and flags what crosses your thresholds.
  • /reconciliation now produces workpapers in your format.

Legal

Connect: your document store.

Share: your standard positions by clause type — what's acceptable, what's negotiated, what's escalated.

Reference: past redlines and your fallback clause library.

Result:

  • /review-contract now flags deviations against your positions with your severity labels.
  • /triage-nda now screens against your defaults for term, jurisdiction, and carveouts.

Marketing

Connect: your CMS and analytics.

Share: your audience segments, channel mix, and style guide.

Reference: brand guidelines and past campaigns that performed.

Result:

  • /campaign-plan now builds briefs for your audiences and channels.
  • /draft-content now writes in your voice for your formats.

Share with your team

The customize session ends with a packaged .plugin file you can pass around.

  • Send the file — teammates select Add › Upload plugin on the plugins page.
  • Host on GitHub — push the plugin folder to a repo that is set up as a marketplace. Teammates add that marketplace, add the plugin from it, and can check for updates after you push.
  • Hand it to your admin — an admin can add the plugin for your organization and, on Enterprise plans, give it to one group, so everyone in that department gets the same pre-configured version. See Manage plugins for your organization.

Things to note

  • Plugins you add in Claude on the web or in Claude Desktop are saved to your account, not to your computer. If Claude tells you that customizing is only available in the desktop app, start the session there.
  • Plugins can come from a few places: Anthropic's pre-built set, ones you add or build, and ones your organization provisions. The first two are yours to edit. You can't edit a plugin your organization manages or one a teammate shared with you.
  • Skills and connectors also exist outside plugins. A standalone skill you add is available in every session, with or without a plugin.

Learn more