Claude Cowork in Practice – Real Files, Real Workflows By the end of this lesson, students should be able to: 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: 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. Evaluating Plugin and Skill effectiveness. After using a Plugin or Skill, assess: 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. Enroll to continue this lesson. The preview above shows the lesson objectives and opening lesson content. Enroll to view the full lesson, complete the practice work, and take the lesson quiz.
Lesson 4: Using Skills and Plugins in Context
Lesson Objectives
Lesson Content
