setup
/setup
Helps the user check or enable the 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.
- Author
- sabbah13 ↗
- Repository
- cowork-tasks ↗
- Licence
- MIT
- Last repository change
- 05.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Helps the user check or enable the 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.
Original author description
Helps the user check or enable the 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.
How it works
- Steps
- Constraints
SKILL.md preview
---
name: setup
description: Helps the user check or enable the 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.
---
# Set up sources for Cowork Tasks
Cowork Tasks does **not** run its own OAuth flows. It reads from whatever
connectors the user has already added and connected in Claude. Your job:
point them at the right place and confirm what's connected.
## Steps
1. Tell the user where to enable connectors:
> Open **Customize > Plugins**, select **Cowork Tasks**, and open its
> **Connectors** tab. It lists the 26 connectors the plugin can read
> from. For each one you want, add it if it shows **Not added**, then
> connect it if it shows **Not connected**. Installing the plugin does
> not connect anything by itself. Connectors you add also appear under
> **Customize > Connectors**, and the same sign-in is shared with every
> other plugin on your account.
2. 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
3. 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**, find
> **Slack**, and select Connect.
4. 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.
- **Never** suggest writing a custom connector package, polling daemon,
or local OAuth helper. Cowork Tasks only reads from MCP connectors
that Claude already hosts - that's the architecture, not a temporary
state.
- If the user wants a source there is no connector for yet (e.g.
YouTrack, Telegram, Discord), tell them honestly: source coverage is
upstream. They should request the connector from Anthropic. We add a
one-line entry to `.mcp.json` once it's available.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sabbah13/cowork-tasks | 90 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 027cf69a8c6b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100health
Reports Cowork Tasks health - which connectors are wired up, board task counts, and any errors. Use when the user asks about Cowork Tasks status or whether it is working. - 100setup-cowork
Guided Cowork setup — install a matching plugin, try a skill, connect tools. Use when: set up cowork, setup cowork, get started with cowork, cowork onboarding, configure cowork, personalize cowork. - 100browse-connectors
Recommends MCP connectors to add to Claude Cowork based on the user's business and empty tool buckets. Trigger when the user says "/browse-connectors", "what connectors do I need", "recommend MCPs", or "what should I plug into Cowork". - 100level-up
Finds the single highest-leverage next move for the user's Cowork AI OS setup. Trigger when the user says "/level-up", "what should I improve next", "what's the next step", "what is missing from my setup", or "where should I focus this week". - 100routines-setup-assistant
Interview-style setup for Claude Cowork Scheduled Tasks. Turns your recurring tasks into ready-to-paste automation prompts. Use when automating weekly reports, digests, or reviews. Triggers: 'set up routines', 'automate my recurring tasks', 'настрой рутины', 'помоги создать scheduled tasks'. - 100triage-now
Scans the owner's connected sources (email, calendar, chat, issue trackers, meetings, CRM, incidents, files, design tools) and converts ONLY the owner's own action items into Cowork Tasks - skipping watch/FYI items, work owned by others, and dashboards. Use when the owner wants…