Guide 8 min read

Build Custom Claude Plugins – No Code Required

In Claude Cowork you can build custom plugins directly in the UI – no code, no folder structures, no command line. Describe your workflow in plain language and Claude creates the plugin for you.

O

Orcha Team

March 6, 2026

Why build custom plugins?

The pre-built finance plugins cover common workflows. But every company has its own processes: your DCF model is structured differently, your deal evaluation follows specific criteria, your internal reports use a particular format.

A custom plugin codifies exactly that knowledge. Once created, Claude follows your process consistently – new team members receive the same quality from day one as experienced colleagues.

What goes into a plugin?

A plugin consists of four building blocks. You don’t need to worry about the technical implementation – Claude creates everything for you. But it helps to know what each part does:

1

Skills – Your Domain Expertise

Skills are your methodology in written form. For example: “How we build a DCF model” or “Our criteria for deal evaluations.” Claude reads these instructions automatically when they are relevant to the topic. More on Skills →

2

Slash Commands – Quick Actions

Commands are shortcuts for recurring tasks. Type /screen, for example, and Claude launches a full deal screening based on your criteria. Think of it as a macro – but powered by AI.

3

Connectors – Data Integrations

Connectors link Claude to your data sources – for example FactSet, PitchBook or internal systems. This allows Claude to pull live data while working, rather than being limited to your conversation alone. More on Connectors →

4

Sub-Agents – Specialists

Sub-agents are specialised helpers that Claude deploys behind the scenes. During a complex analysis, for instance, one sub-agent can verify financial data while another researches market data – both simultaneously. More on Claude →

Key Takeaway

The most important building block is Skills – your SOPs in written form. Claude follows them step by step. You can find everything else about this in our guide to Skills & Projects.

Creating a plugin – right inside Cowork

There are two ways to build a custom plugin. Both work entirely within the Cowork interface – no code, no command line.

Option 1: Let Claude build it for you

Simply open Cowork and describe in plain language what your plugin should do. Claude automatically recognises that you want to build a plugin and guides you through the process.

How to create a plugin through conversation

1

Open Cowork and start a new task. Describe what your plugin should do – a single sentence is enough to get started, e.g.: “I need a plugin for our monthly management reporting.”

2

Claude asks follow-up questions: Which data sources do you use? What steps does the process involve? What output format do you need? How do you handle edge cases?

3

Based on your answers, Claude automatically creates the Skills, Commands and Connectors for your plugin.

4

Test it immediately: run a slash command. If something doesn’t fit, tell Claude – and it adjusts on the spot.

Option 2: Customise an existing plugin

Instead of starting from scratch, you can take an existing plugin as a template and adapt it to your workflow.

How to customise an existing plugin

1

Open an installed plugin (e.g. Financial Analysis) and click “Customize” in the top-right corner.

2

Cowork opens a new task with a customisation guide. Click “Let’s go”.

3

Tell Claude what you want to change: different criteria, different data sources, a different output format. Claude adjusts the Skills, Commands and Connectors accordingly.

Example: Deal Screening Plugin

Suppose your M&A advisory firm evaluates potential acquisition targets using a fixed set of criteria. Here is what your description to Claude might look like:

Your description to Claude

“Build a plugin for our M&A deal screening. When I type /screen, Claude should: ask for industry, revenue range and region. Then search for matching companies and score them using our framework: revenue growth >10% (+2 points), EBITDA margin >20% (+2), leverage <3x EBITDA (+1), management tenure >5 years (+1). Output as a table with the top 20 sorted by score.”

Claude automatically creates a Skill with your scoring framework, a /screen command and, optionally, connectors to PitchBook or FactSet. You can test it right away and have it adjusted as needed.

Another example: Monthly reporting

“Build a plugin for our monthly management reporting. When I type /report, Claude should: summarise the current financial data (revenue, EBITDA, cash flow), flag variances against the budget, write a commentary on the three largest variances and output the result as a PowerPoint template.”

Where does the data come from? You can provide the financial data (revenue, EBITDA, cash flow) in several ways: upload an Excel or CSV file, paste it directly into the chat, or have it pulled automatically from your ERP or BI system via a connector.

Test and improve

The best way to improve a plugin: use it with real data. If a step is missing, the criteria are off or the output format doesn’t match – tell Claude directly and it adjusts the plugin on the spot.

You can also upload a finished sample document (e.g. a previous report) so that Claude adopts the format and structure.

Sharing plugins with your team

Finished plugins are stored locally on your machine. There are three options for sharing with the team:

  • Share the file: Export the plugin as a file and send it to colleagues. They import it into Cowork via “Customize” → “Browse plugins.”
  • Team / Enterprise plan: Admins can distribute plugins centrally through the organisation’s private plugin marketplace. Plugins then appear automatically in the catalogue for all team members.
  • Automatic provisioning: On Enterprise plans, specific plugins can be pre-installed for all users.

Tips for building great plugins

  • Start small: One workflow, one plugin. Only expand once the first process works reliably.
  • Be specific: The more precisely you describe your methodology, the more consistently Claude performs. Vague instructions lead to unpredictable results.
  • Upload examples: A finished report or an Excel template helps Claude adopt your desired format straight away.
  • Iterate: No plugin is perfect on the first try. Test, give feedback, adjust – all within the conversation with Claude.
  • Ask Claude for feedback: Ask Claude directly: “What would you change or improve about this plugin?” Claude understands the structure and often suggests useful additions you may have overlooked.
  • Share what works: When a plugin performs well, pass it on to the team. Plugins benefit from collective experience.

Conclusion

Custom plugins let you embed your company’s knowledge into Claude – without any technical resources. Simply describe your workflow and Claude turns it into a reusable plugin with slash commands and data connections. To get started: identify your most repetitive process and begin there.

Want more guides like this?

Subscribe to our newsletter for new resources delivered to your inbox.