Stats
Actions
Tags
From cowork-tasks
Reports Cowork Tasks health - which Cowork connectors are wired up, board task counts, and any errors. Use when the user asks about Cowork Tasks status or whether it is working.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cowork-tasks:healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Read the local task store via the MCP `list_tasks` tool with no
Read the local task store via the MCP list_tasks tool with no
since cursor. Note the version and the count by column.
Check which Cowork connectors are mounted in this session by listing available MCP tools. For each declared connector, report whether at least one tool is callable.
The plugin declares these connectors in .mcp.json:
gmail, google calendar, ms365slackatlassian, linear, asana, monday, clickup, githubnotion, gurufathom, fireflies, granola, gongintercom, hubspot, closepagerduty, datadogbox, egnyte, docusignfigma, canvaFormat as a short grouped table:
Email/Calendar
gmail connected
google calendar connected
ms365 not connected
Chat
slack connected
Issue trackers
atlassian connected
linear not connected
...
Board: 23 active tasks (Inbox 5 / Todo 12 / In progress 4 / Blocked 1 / Done 1)
MCP version: 47
If popular ones (gmail, slack, atlassian) are missing, suggest
/cowork-tasks:setup.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub sabbah13/cowork-tasks --plugin cowork-tasks