daBongo LMS AI Training Courses

← Back to Course

Claude Cowork in Practice – Real Files, Real Workflows

Lesson 4: Using Skills and Plugins in Context

Lesson Objectives

By the end of this lesson, students should be able to:

  • Identify which tasks benefit from a Plugin versus a Skill versus neither
  • Activate and use a Plugin in a Cowork session
  • Invoke a Skill at the appropriate point in a task
  • Evaluate whether a Plugin or Skill is genuinely improving workflow output

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.

Practical Example

A marketing coordinator uses the Google Drive Connector in Cowork to pull the latest campaign brief from a shared Drive folder and cross-reference it against the previous campaign's results document.

Without the Connector, she would manually download both files, upload them to Cowork, and manage version discrepancy risk.

With the Connector, Claude accesses the current Drive versions directly, pulling the latest data.

She verifies the campaign brief version number to confirm Claude pulled the current version, not a cached older one.

The Connector reduces setup time but requires one version-check – worth it for a frequently updated document.

Lesser-Known Tip

When evaluating whether to add a Plugin to a recurring workflow, time both versions once: the workflow with the Plugin fully configured, and the workflow without (manual file management). The Plugin will win on an ongoing basis if the recurring time savings exceed the setup and authorization cost – typically by the third or fourth use. One-time tasks rarely justify Plugin setup.

Safety Notes

Plugins that connect to real apps – email, calendar, project management – can take direct actions: sending emails, creating events, updating records. Before authorizing any Plugin with write access to a real app, understand exactly what actions it can take and under what conditions. For write-access Plugins, review Claude's proposed actions before they execute rather than authorizing fully autonomous operation.

Practice Task

Identify one Cowork task you do regularly that currently requires you to leave Claude and take action in another application. Determine whether a Plugin exists for that application. If yes, evaluate whether setting it up is worth the time savings for your use case. If a Plugin is not available or not worth the setup, document why – this evaluation is itself a useful skill.

Completion Check

You should be able to identify when a Plugin adds value versus when it adds overhead, describe how to use a Plugin in a task assignment, and evaluate whether a Plugin is improving or complicating a workflow.

Log in and enroll to access lesson quizzes.

← Back to Course

Scroll to Top