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.
npx claudepluginhub sabbah13/cowork-tasks --plugin cowork-tasksThis skill uses the workspace's default tool permissions.
1. Read the local task store via the MCP `list_tasks` tool with no
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.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
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.