In this lesson, you'll define a plugin and what it bundles together, recognize the two shapes plugins take, and install or customize a plugin against a real piece of your work.
Plugins come in two flavors โ both useful, both common.
Shape 1: An end-to-end process bundled together. When the work has many sequential steps, you can package the skills for each step into a plugin so the whole process runs as one. For example, a monthly-close plugin might include separate skills for pulling the actuals, building the variance table, and drafting the board memo โ each one a step in the larger workflow. Anyone on the team installs the plugin and gets the entire process the way you do it.
Shape 2: A team's most-used skills bundled together. This is great for a set of recurring jobs the team does. You can bundle the most important ones into a single plugin. For example, a finance plugin might include separate skills for variance analysis, financial modeling, investment-memo drafting, and quarterly reports. They aren't dependent on each other โ they're just the skills the team reaches for most. Bundling them means new teammates install one thing and have the team's whole toolkit.
The shape that matters in either case: a plugin is a package built around workflows. "Renewal prep for our customer success team" is a plugin. "Equity research for our fund" is a plugin. "The monthly board cycle for the CFO's office" is a plugin.
Anthropic publishes plugins for the most common roles in knowledge work, each one built and maintained as a starting point you can use as-is or shape to your team. Find them in Customize โ Plugins in Cowork. Browse for the plugin that matches your work, click , and approve the connectors the plugin uses. The plugin's skills become available immediately.
Sign in to join the discussion
A plugin from the marketplace is a strong default, not a final answer. The skills and connectors inside use a generic version of the workflow; your team has its own templates, definitions, and steps. You can shape any installed plugin to match.
After you've installed the plugin, go back to Customize โ Plugins โ [Plugin name] and click Customize. This opens a new Cowork task where you and Claude work together to tailor the plugin. You can add a starter prompt by directing it to specific assets, sharing context, or uploading the examples you want it to use as a base. Claude will then update the plugin to be true to your team's context.
For example, you could say something like:
Here are our last three red-lined NDAs. Update the /nda-triage skill in this plugin so the format and tone match these.
Claude adapts the plugin in place. The more you shape it to your team's actual work, the more leverage it produces.
If your team has a workflow that doesn't fit any existing plugin, you can build one by working with Cowork. It will bundle the skills the workflow needs, include any connectors it depends on, and package it for easy installation into your instance of Cowork.
Most teams start small. One skill for the most repetitive task. Then another. By the time it has three or four skills and the connectors that matter, it's a plugin worth sharing โ and you'll learn how to share it with your team in Lesson 13.
Your admin may have already published plugins for your organization โ check the Directory (Customize โ Plugins) before you build anything yourself.
Let's find the plugins that fit your work. In a new Cowork conversation, type:
/setup-cowork
The skill starts a short interview. Claude asks about the type of work you do, then suggests a plugin that would work best for your needs. You can easily add the plugin right from chat and test it out in the conversation. Once installed, customize it for your team.
You've now made Cowork yours for one piece of your work. The next module is about extending Cowork beyond the desktop โ into your browser, and into the M365 apps where a lot of the work lands.