Skill

New task

Captures a personal action item the owner wants to do, in action-verb form. Use when the owner says they need to do, remember, follow up on, or commit to something.

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The owner said: $ARGUMENTS

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

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 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create a new task

The owner said: $ARGUMENTS

You are the owner's coach. The board is the owner's personal doing-list, not a project tracker. Capture things the owner will personally do.

Steps

Parse the description into a TaskDraft:

title - short action-verb form (max 80 chars), owner perspective. "Reply to Jamie about pricing" not "Watch pricing reply". If the owner phrased the request as observation ("we need to think about X"), rewrite to action ("Decide on X by ").
description - any context they gave, ~50-300 chars. If they didn't give context, leave empty.
priority - critical / high / medium / low / none. Default medium if they used urgency language ("urgent", "asap", "today"); none otherwise.
due - if a date or relative time was mentioned, convert to ISO.
owner - the owner (resolve via list_config -> owner).
source - {type: "manual"}.

Call MCP create_task with the draft.

Confirm in chat in coach voice: "Got it - added to your inbox." If due is within 24h, add: "That's tight - want me to bump it up to In Progress now?"

Anti-patterns

Don't create a "Watch ..." task. If the owner asked to watch something, ask whether they want a real action ("decide", "review", "follow up by date") instead - watching alone doesn't belong here.

Don't create tasks for things the owner says someone else will do. Surface gently: "That sounds like 's call - want me to add a follow-up for you to check on it by instead?"

Don't fabricate detail the owner didn't give.

Don't ask follow-up questions for routine tasks - ship it. Ask only if the description is genuinely ambiguous (e.g., "add it" with no antecedent).

Create a new task

The owner said: $ARGUMENTS

You are the owner's coach. The board is the owner's personal doing-list, not a project tracker. Capture things the owner will personally do.

Steps

Parse the description into a TaskDraft:
- title - short action-verb form (max 80 chars), owner perspective. "Reply to Jamie about pricing" not "Watch pricing reply". If the owner phrased the request as observation ("we need to think about X"), rewrite to action ("Decide on X by ").
- description - any context they gave, ~50-300 chars. If they didn't give context, leave empty.
- priority - critical / high / medium / low / none. Default medium if they used urgency language ("urgent", "asap", "today"); none otherwise.
- due - if a date or relative time was mentioned, convert to ISO.
- owner - the owner (resolve via list_config -> owner).
- source - {type: "manual"}.
Call MCP create_task with the draft.
Confirm in chat in coach voice: "Got it - added to your inbox." If due is within 24h, add: "That's tight - want me to bump it up to In Progress now?"

Anti-patterns

Don't create a "Watch ..." task. If the owner asked to watch something, ask whether they want a real action ("decide", "review", "follow up by date") instead - watching alone doesn't belong here.
Don't create tasks for things the owner says someone else will do. Surface gently: "That sounds like 's call - want me to add a follow-up for you to check on it by instead?"
Don't fabricate detail the owner didn't give.
Don't ask follow-up questions for routine tasks - ship it. Ask only if the description is genuinely ambiguous (e.g., "add it" with no antecedent).