Plugins, Skills, and Specialist Agents

Once you’ve installed a plugin or two, you’ll notice Cowork exposes three different kinds of capability: plugins, skills, and specialist agents. They sound similar but they do different jobs, and knowing the difference is the fastest way to use Cowork well.

The three layers, simply

Plugins are the package. They bundle related skills, tool connections, and agents into one install.

Skills are named workflows. You invoke a skill by name (often with a slash command like /draft-content or /seo-audit), give it inputs, and it runs a defined process.

Specialist agents are persistent personas with their own expertise and rules. When you delegate a task to a specialist, they bring their own context, voice, and constraints to the work.

Here’s a useful mental model: a plugin is a hire, a skill is a procedure that hire knows, and a specialist agent is a coworker you can pull into the conversation.

Working with skills

Skills are the easiest layer to start with. You don’t need to think about who’s running them — you just call the skill and provide what it needs.

A typical skill invocation:

/draft-content
Topic: how our new pricing model changes things for small teams
Audience: existing customers on the starter plan
Length: 200 words
Tone: direct, no jargon

The skill picks up your inputs, runs its internal process, and returns the output. Many skills will also ask clarifying questions before producing the final result — answer them like you would for a coworker.

Working with specialist agents

Specialists are the second layer. They live longer than a single skill invocation. They might have their own files, their own memory, and their own preferences for how they work.

For example: a Brand Voice specialist holds your brand guidelines and reviews any content you produce against them. A Sales specialist knows your ICP, your offer, and your typical objections. A Design specialist enforces your design system.

You typically invoke a specialist by name in conversation: “Send this draft to the Brand Voice specialist for a review pass.”

When to use which

Use a skill when you can answer “what’s the process here?” in one sentence.

Use a specialist when the answer to “who would I ask for this?” matters more than “what’s the process?”

Use a plugin when you’ve installed several related skills and specialists separately and want them bundled.

Common patterns

A few real-world patterns that show how the layers stack:

1. Content production loop. Marketing plugin → /draft-content skill produces a draft → Brand Voice specialist reviews → revision skill applies notes → publish.
2. Sales outreach. Sales plugin → /account-research skill on a target company → /draft-outreach skill writes the email → you review and send.
3. Meeting capture. Productivity plugin → Fireflies tool connection pulls the transcript → /summarize-meeting skill extracts action items → posts to Notion automatically.

Notice the pattern: plugins make the tools and skills available, skills do the bounded work, specialists handle the parts that need judgment.

What’s next

You’ve now seen the three layers of Cowork in action. From here, the practical move is to actually run one full pattern end-to-end on your real work — pick one of the three patterns above, identify the equivalent in your role, and run it today. Reading more about Cowork has rapidly diminishing returns compared to using it.