Start with a standalone skill when your team needs a repeatable method for one job. Consider a plugin when several related skills and their connection settings need to be installed and maintained together. Choose around the work people will use, who owns the instructions and how changes will reach the team.

Claude Cowork and Claude Code provide concrete examples of both approaches. The distinctions below use Anthropic's documentation checked on 19 October 2026. Treat plugin packaging as specific to the host application; the word “plugin” alone tells you neither which components are supported nor whether a package will work elsewhere. Claude Code plugins overview.

A skill includes the material its instructions depend on

In Claude Code, SKILL.md is the entry file for a skill. It describes when the skill applies and contains the instructions to follow. The surrounding folder can also hold reference documents, examples, templates and scripts. Those supporting files let the main instructions point to detail needed for particular parts of the work. Claude Code skills documentation.

That makes the complete folder the practical thing to maintain. If the instructions refer to a template that was left behind, the recipient has an incomplete method. Read the references before sharing a skill, preserve its supporting files and distinguish reusable guidance from information someone must supply for each run.

A plugin packages capabilities as a unit

Anthropic documents Cowork plugins as bundles that can include skills and connectors. Claude Code's plugin format can contain multiple skill folders alongside other components, including MCP server configuration. Its plugin manifest can record the package's identity and version. A plugin can therefore carry both the methods for doing work and configuration for the tools those methods use. Claude Help Center, Claude Code manifest reference.

The packaging decision concerns what belongs together. Keep the individual skills focused enough that someone can understand what each one prepares and when to use it. For the separate distinction between tool connections and written procedures, see AI skills and MCP.

Installation and team distribution are separate choices

For standalone custom skills, Anthropic documents uploading a ZIP containing the skill folder. Claude Code also supports skill folders in personal or project locations. These are different installation routes: a folder in Claude Code's personal skills directory is not automatically a Cowork skill. Custom skill packaging, Claude Code skill locations.

In Cowork, the documented plugin route starts in Customize, where users can browse plugins or upload a custom package. Claude Code offers installation through plugin marketplaces, which list packages and where to fetch them. Follow the instructions for the application your team actually uses. Cowork plugin installation, Claude Code plugin installation.

A shared workflow does not automatically require a plugin. Claude also offers organization-wide standalone skill provisioning on Team and Enterprise plans, subject to its prerequisites and organization settings. Choose a bundle because its contents belong together, rather than assuming it is the only way to distribute a skill. Organization skill management.

Illustration: a marketing function grows from one skill

Imagine a marketing team starting with a newsletter-drafting skill. Its folder contains the instructions, a brand guide, an approved-claims reference and a newsletter template. The marketing lead supplies the issue's brief and source material. The skill is intended to prepare a draft with unresolved facts called out; an editor checks it before publication.

The team then designs separate skills for campaign planning and reviewing campaign performance. A marketing plugin could package these with the newsletter skill and configuration for an approved connection to campaign data, subject to the chosen host's support and access setup. The team would have one package to distribute while retaining separate methods for distinct jobs.

Suppose the company changes its product description. The bundle owner would update the shared reference and check a campaign plan, newsletter and performance commentary for outdated language. The marketing lead would still choose the campaign objective and approve publication.

Give the package a maintenance owner

Decide who accepts changes, where the maintained copy lives and how users receive revisions. In Claude Code, automatic plugin updates depend on marketplace settings, and a running session can retain its already-loaded version until reloaded. Installation alone does not establish that everyone is using the revision you expect. Plugin update behavior.

Review a new package or revision before wider use, including supporting scripts and connection settings. Decide who approves changed access and how to return to the previous reviewed version. The security guide explains why checking the main instruction file alone leaves part of that work undone.

For either format, keep representative inputs and agreed review criteria beside the maintenance process. After a change, test the affected outputs, missing-information handling and handoffs. If one complete skill serves the job, keep it focused. When related capabilities need a common release and owner, package them together and check the whole workflow people will use.