Skip to main content

Claude Plugins Are Now on the Web (and Why They Beat Skills for Teams)

Claude's breakdown of when to use a Skill versus a Plugin

Claude plugins now work in the web app, and for teams they matter more than skills. A plugin packages skills, MCP connectors, commands and agents into one unit you install once, so a team can share, version and update a whole workflow instead of each person maintaining their own skills. Use a skill for a personal, repeatable task; use a plugin when a team needs the same workflow and the connectors it depends on.

Plugins bring skills and connectors together

If you've been using Claude for a while, you've probably used skills. At its simplest level, Claude can produce prompts (SKILL.md) that allow it to use the same set of instructions for repeated workflows. The best part: Claude can decide when to use them, not just the user. At higher levels of complexity, skills can manage multiple processes and workflows. These complex skills (just .zip files with some requirements and a modified .skill extension) package together folders and layers of resources, with 'progressive disclosure' allowing Claude to discover and utilize a number of different workflows at once. Skills like this are great, but they have a couple of key problems:

  1. Skills have to be edited manually by the user or recreated entirely from scratch by Claude. That makes maintenance and enhancements a total pain.

  2. The skills exist independently of related MCP connectors, so users have to reference connectors directly in the skill instead of natively including an allowed or suggested list.

  3. Skills have no version control or binding to GitHub, which means there's no easy way for a large team or organization with many different contributors to maintain them.

Plugins solve those problems

Plugins are packages made to be maintained remotely and installed by users. They bundle everything a workflow needs — instructions, MCP connections, agents, hooks, background monitors, settings — into a single deployable package. You add it once. It works everywhere it's supposed to.

The difference matters more than it sounds. Skills are great for personal workflows and repeatable tasks you've built yourself. Plugins are built to be shared, versioned, and maintained. That's a meaningful shift for teams and for anyone who wants to use AI tooling that keeps up with how their business actually operates.

Anthropic and their partners have produced a number of plugins for Claude, with some of the most popular being those for Legal and for Small Business, both of which I've found useful in my work. You can also build your own plugins, and they can be maintained the same way. Keep a plugin in a GitHub repository, add that repository as a marketplace, and updates flow from the source. On Team and Enterprise plans, an organization owner can sync the company's plugins from a private GitHub repository and make them available, installed by default, or required for members. That makes plugins the way to securely and easily maintain an organization's workflows and processes.

If you want to try it today, Claude has its own workflow on the web to help you build one. Go to Customize > Plugins > Add > Create with Claude. Custom plugins offer a way for teams across industries — marketing, finance, consulting, legal, and more — to combine the value of skills and connectors into more easily-managed packages.

If you want to talk through what a plugin could do for your team, let's chat!


Mosaic Solutions helps small and mid-sized businesses implement AI that actually works. mosaicsolutions.tech

Frequently Asked Questions

What is a Claude plugin?

A Claude plugin is a package that bundles skills, MCP connectors, commands and agents so you can add them to Claude as one unit. You install it from Customize, then Plugins, in claude.ai or the desktop app, and it is saved to your account, so the same plugin is available in chat, Cowork and Claude Code without installing it again.

What's the difference between a Claude skill and a plugin?

A skill is a set of instructions Claude follows when a task matches, such as your process for a weekly report. A plugin can contain several skills plus the connectors, commands and agents they rely on, packaged so a team can share, version and update them together. Use a skill for a personal, repeatable task and a plugin for a workflow a whole team needs.

How do I create a Claude plugin on the web?

In claude.ai, go to Customize, then Plugins, then Add. Choose Create with Claude to build the plugin in a conversation, or Create a plugin to write its files directly in an editor. On Team and Enterprise plans you can then share the plugin with specific people or publish it to your whole organization.

Can a team keep a custom Claude plugin updated from GitHub?

Yes. A GitHub repository that contains plugins can be added as a marketplace, and updates flow from that source. On Team and Enterprise plans, an organization owner can sync the company's plugins from a private or internal GitHub repository in organization settings, then make each plugin available, installed by default or required for members.

Drew Bloom, founder of Mosaic Solutions

Drew Bloom

Founder, Mosaic Solutions — Business Systems, Software & Automation

Drew is the founder of Mosaic Solutions. He spent several years as an automation consultant and Innovation Lead for Affinity, where he worked with law firms and enterprise clients on AI strategy, change management, and custom software. He works with small and mid-sized businesses in Iowa and beyond to fix the systems that slow them down — with better processes, software, and AI that actually works.

More about Mosaic LinkedIn Work with Drew

Fix the System That Slows You Down.

Custom software, integrations and modernization, built inside the stack you already run and scoped before work begins.