Lesson Content

Quick refresher: Skills, Plugins, Connectors.

Skills are slash-command workflows in Claude Code – reusable instruction sequences that Claude applies when invoked. Connectors bridge Claude to real apps (Gmail, Drive, Slack, etc.). Plugins bundle Skills and Connectors for a specific role or workflow – they combine the two into a package.

In Cowork, you work with Plugins and their Connectors primarily; Skills are more central to Code mode.

When Plugins add genuine value.

Plugins are most useful when the task genuinely requires reaching outside of Claude to a connected system:

• Sending or reading email without switching applications
• Creating or reading calendar events in context
• Searching a connected knowledge base for relevant documents
• Updating a project management tool as part of a workflow

Plugins add overhead: setup, authorization, context about what the connected app contains. They are worth that overhead when the alternative is leaving Claude and doing the external action manually, breaking the workflow.

When a Plugin is not the right tool.

If the task is self-contained – entirely within the conversation, using only uploaded files, or using only Claude's generative abilities – a Plugin is unnecessary overhead. Do not add Plugins to workflows that do not require external app access.

Using a Plugin in a session.

1. Confirm the Plugin is available and authorized in your Cowork environment
2. Reference the Plugin in your task assignment: "Using the [Plugin name] to access [connected resource]…"
3. Claude will use the Plugin to access the connected resource during its task execution
4. Review outputs that came from the Plugin source the same way you review document-based outputs – with spot verification

Evaluating Plugin and Skill effectiveness.

After using a Plugin or Skill, assess:

• Did it save time compared to doing the external action manually?
• Did it introduce errors or retrieve incorrect information from the connected source?
• Was the authorization and setup cost worth the output quality?

If a Plugin consistently introduces errors or retrieves stale data from a connected source, the quality problem may be in the connected app's data – not in the Plugin itself. Investigate the source before blaming the tool.