clickup-tool

Add a comment to a ClickUp task. Can compose comment text from instructions like "summarize the last commit" or "write a status update".

Log time on a ClickUp task. Can analyze git history to determine duration and description automatically.

Get comments and discussion on a ClickUp task

Delete a time tracking entry from ClickUp.

Check ClickUp authentication and show current user info

List all workspace members (id, username, email)

Change the status of a ClickUp task. Understands free-form input like "в работу", "close it", "on hold".

Browse ClickUp workspace hierarchy (spaces, folders, lists/sprints)

List available tags in a ClickUp space

Get full details of a specific ClickUp task including description, checklists, and time tracking

List ClickUp tasks assigned to me (filter by status, tag, assignee)

Use a **Haiku** clickup-executor subagent to fetch and format time entries. Do NOT run clickup-tool commands inline.

Execute ClickUp data queries and return structured summaries. Dispatched by /clickup-tool:tasks, /clickup-tool:task, /clickup-tool:comments, /clickup-tool:set-status, and /clickup-tool:time-entries commands. Runs in isolated context — only the final summary returns to the main conversation. <example> Context: User wants to see their tasks user: "/clickup-tool:tasks" assistant: "I'll dispatch the clickup-executor agent to fetch and format the task list." <commentary> Heavy data query — dispatch to clickup-executor to keep raw JSON out of main context. </commentary> </example> <example> Context: User wants task details user: "/clickup-tool:task 86abc123" assistant: "I'll dispatch the clickup-executor agent to fetch full task details." <commentary> Single task detail with description, checklists, time entries — dispatch to clickup-executor. </commentary> </example> <example> Context: User asks for task comments user: "/clickup-tool:comments 86abc123" assistant: "I'll dispatch the clickup-executor agent to fetch the discussion thread." <commentary> Comments with replies and attachments — dispatch to clickup-executor. </commentary> </example>

Deep ClickUp task analysis agent — use for complex multi-step queries that chain multiple API calls (sprint tasks + comments, cross-list comparisons, team workload analysis). Runs in isolated context to avoid polluting the main conversation with intermediate JSON data.

This skill should be used when the user asks to "check my tasks", "show ClickUp tasks", "get task details", "view task comments", "show project structure", "list sprints", "what am I working on", "show my ClickUp board", "task status", "add a comment", "post a note", "log time", "track time", "delete time entry", "time entries", "timesheet", "how much did I work", "change status", "set status", "move to in progress", "close task", "create task", "new task", "add task", "make a task", "create a ticket", "file a bug", "create issue", or mentions ClickUp, tasks, sprints, or project management queries. Provides read and write access to ClickUp workspace data through the clickup-tool CLI with normalized, compressed JSON output.

1 hook across 1 event