Skill

Set up sources

Helps the user check or enable Cowork connectors that Cowork Tasks reads from. Use when the user asks how to connect a source, on first run, or when triage reports a missing connector.

npx claudepluginhub sabbah13/cowork-tasks --plugin cowork-tasks

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Cowork Tasks does **not** run its own OAuth flows. It reads from whatever

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars2

Parent Repo Forks0

Last CommitMay 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Set up sources for Cowork Tasks

Cowork Tasks does not run its own OAuth flows. It reads from whatever sources the user has already authorized in Cowork's Connectors panel. Your job: point them at the right place and confirm what's connected.

Steps

Tell the user where to enable connectors:

Open Customize -> Connectors in the Cowork sidebar. The Cowork Tasks plugin pre-declares 25+ supported connectors so they appear there ready to enable. Toggle on whichever you want Cowork Tasks to read from. Each one uses Cowork's standard OAuth - the same authorization is shared with every other plugin.

List the supported connectors grouped by category. Pull from ${CLAUDE_PLUGIN_ROOT}/CONNECTORS.md if you need a refresh, but the short version is:

Email / calendar / Office: Gmail, Google Calendar, Microsoft 365
Chat: Slack
Issue trackers: Atlassian (Jira), Linear, Asana, monday.com, ClickUp, GitHub
Knowledge: Notion, Guru
Meeting recorders: Fathom, Fireflies, Granola, Gong
Customer support: Intercom
CRM: HubSpot, Close
Incidents / on-call: PagerDuty, Datadog
Files: Box, Egnyte
Signatures: DocuSign
Design: Figma, Canva

If a specific connector failed during a triage run, name it and link the user to the right place:

Slack isn't connected yet. Open Customize -> Connectors -> Slack and click Connect.

After the user connects something, suggest:

Try /cowork-tasks:triage-now to pull anything you've missed since before the connection went live.

Constraints

Never ask the user to paste tokens or run a local OAuth helper.

Never invent connector names. Use the canonical names above.

If the user wants a source we don't pre-declare (e.g., YouTrack, Telegram, Discord), point them at the project's examples/connector-template/ folder and offer to help write a PR. Until that lands, they can run the matching local connector binary in packages/plugin/bin/connectors/ outside Cowork.

Set up sources for Cowork Tasks

Steps

Tell the user where to enable connectors:

Open Customize -> Connectors in the Cowork sidebar. The Cowork Tasks plugin pre-declares 25+ supported connectors so they appear there ready to enable. Toggle on whichever you want Cowork Tasks to read from. Each one uses Cowork's standard OAuth - the same authorization is shared with every other plugin.
List the supported connectors grouped by category. Pull from ${CLAUDE_PLUGIN_ROOT}/CONNECTORS.md if you need a refresh, but the short version is:
- Email / calendar / Office: Gmail, Google Calendar, Microsoft 365
- Chat: Slack
- Issue trackers: Atlassian (Jira), Linear, Asana, monday.com, ClickUp, GitHub
- Knowledge: Notion, Guru
- Meeting recorders: Fathom, Fireflies, Granola, Gong
- Customer support: Intercom
- CRM: HubSpot, Close
- Incidents / on-call: PagerDuty, Datadog
- Files: Box, Egnyte
- Signatures: DocuSign
- Design: Figma, Canva
If a specific connector failed during a triage run, name it and link the user to the right place:

Slack isn't connected yet. Open Customize -> Connectors -> Slack and click Connect.
After the user connects something, suggest:

Try /cowork-tasks:triage-now to pull anything you've missed since before the connection went live.

Constraints

Never ask the user to paste tokens or run a local OAuth helper.
Never invent connector names. Use the canonical names above.
If the user wants a source we don't pre-declare (e.g., YouTrack, Telegram, Discord), point them at the project's examples/connector-template/ folder and offer to help write a PR. Until that lands, they can run the matching local connector binary in packages/plugin/bin/connectors/ outside Cowork.