[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-4c2e42ca-9caa-4d56-a72b-7fc0463f8a86":3,"$fwuyWdLnx6EACCFRxHi3CH7s4ecvKd74UcLwSkt8eCmg":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"4c2e42ca-9caa-4d56-a72b-7fc0463f8a86","clickup-automation","自动化ClickUp项目管理，包括任务、空间、文件夹、列表、评论和团队操作，通过Rube MCP（Composio）。始终首先搜索当前架构的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: clickup-automation\ndescription: \"Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# ClickUp Automation via Rube MCP\n\nAutomate ClickUp project management workflows including task creation and updates, workspace hierarchy navigation, comments, and team member management through Composio's ClickUp toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active ClickUp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup`\n3. If connection is not ACTIVE, follow the returned auth link to complete ClickUp OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Tasks\n\n**When to use**: User wants to create tasks, subtasks, update task properties, or list tasks in a ClickUp list.\n\n**Tool sequence**:\n1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - Get workspace\u002Fteam IDs [Prerequisite]\n2. `CLICKUP_GET_SPACES` - List spaces in the workspace [Prerequisite]\n3. `CLICKUP_GET_FOLDERS` - List folders in a space [Prerequisite]\n4. `CLICKUP_GET_FOLDERLESS_LISTS` - Get lists not inside folders [Optional]\n5. `CLICKUP_GET_LIST` - Validate list and check available statuses [Prerequisite]\n6. `CLICKUP_CREATE_TASK` - Create a task in the target list [Required]\n7. `CLICKUP_CREATE_TASK` (with `parent`) - Create subtask under a parent task [Optional]\n8. `CLICKUP_UPDATE_TASK` - Modify task status, assignees, dates, priority [Optional]\n9. `CLICKUP_GET_TASK` - Retrieve full task details [Optional]\n10. `CLICKUP_GET_TASKS` - List all tasks in a list with filters [Optional]\n11. `CLICKUP_DELETE_TASK` - Permanently remove a task [Optional]\n\n**Key parameters for CLICKUP_CREATE_TASK**:\n- `list_id`: Target list ID (integer, required)\n- `name`: Task name (string, required)\n- `description`: Detailed task description\n- `status`: Must exactly match (case-sensitive) a status name configured in the target list\n- `priority`: 1 (Urgent), 2 (High), 3 (Normal), 4 (Low)\n- `assignees`: Array of user IDs (integers)\n- `due_date`: Unix timestamp in milliseconds\n- `parent`: Parent task ID string for creating subtasks\n- `tags`: Array of tag name strings\n- `time_estimate`: Estimated time in milliseconds\n\n**Pitfalls**:\n- `status` is case-sensitive and must match an existing status in the list; use `CLICKUP_GET_LIST` to check available statuses\n- `due_date` and `start_date` are Unix timestamps in **milliseconds**, not seconds\n- Subtask `parent` must be a task (not another subtask) in the same list\n- `notify_all` triggers watcher notifications; set to false for bulk operations\n- Retries can create duplicates; track created task IDs to avoid re-creation\n- `custom_item_id` for milestones (ID 1) is subject to workspace plan quotas\n\n### 2. Navigate Workspace Hierarchy\n\n**When to use**: User wants to browse or manage the ClickUp workspace structure (Workspaces > Spaces > Folders > Lists).\n\n**Tool sequence**:\n1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List all accessible workspaces [Required]\n2. `CLICKUP_GET_SPACES` - List spaces within a workspace [Required]\n3. `CLICKUP_GET_SPACE` - Get details for a specific space [Optional]\n4. `CLICKUP_GET_FOLDERS` - List folders in a space [Required]\n5. `CLICKUP_GET_FOLDER` - Get details for a specific folder [Optional]\n6. `CLICKUP_CREATE_FOLDER` - Create a new folder in a space [Optional]\n7. `CLICKUP_GET_FOLDERLESS_LISTS` - List lists not inside any folder [Required]\n8. `CLICKUP_GET_LIST` - Get list details including statuses and custom fields [Optional]\n\n**Key parameters**:\n- `team_id`: Workspace ID from GET_AUTHORIZED_TEAMS_WORKSPACES (required for spaces)\n- `space_id`: Space ID (required for folders and folderless lists)\n- `folder_id`: Folder ID (required for GET_FOLDER)\n- `list_id`: List ID (required for GET_LIST)\n- `archived`: Boolean filter for archived\u002Factive items\n\n**Pitfalls**:\n- ClickUp hierarchy is: Workspace (Team) > Space > Folder > List > Task\n- Lists can exist directly under Spaces (folderless) or inside Folders\n- Must use `CLICKUP_GET_FOLDERLESS_LISTS` to find lists not inside folders; `CLICKUP_GET_FOLDERS` only returns folders\n- `team_id` in ClickUp API refers to the Workspace ID, not a user group\n\n### 3. Add Comments to Tasks\n\n**When to use**: User wants to add comments, review existing comments, or manage comment threads on tasks.\n\n**Tool sequence**:\n1. `CLICKUP_GET_TASK` - Verify task exists and get task_id [Prerequisite]\n2. `CLICKUP_CREATE_TASK_COMMENT` - Add a new comment to the task [Required]\n3. `CLICKUP_GET_TASK_COMMENTS` - List existing comments on the task [Optional]\n4. `CLICKUP_UPDATE_COMMENT` - Edit comment text, assignee, or resolution status [Optional]\n\n**Key parameters for CLICKUP_CREATE_TASK_COMMENT**:\n- `task_id`: Task ID string (required)\n- `comment_text`: Comment content with ClickUp formatting support (required)\n- `assignee`: User ID to assign the comment to (required)\n- `notify_all`: true\u002Ffalse for watcher notifications (required)\n\n**Key parameters for CLICKUP_GET_TASK_COMMENTS**:\n- `task_id`: Task ID string (required)\n- `start` \u002F `start_id`: Pagination for older comments (max 25 per page)\n\n**Pitfalls**:\n- `CLICKUP_CREATE_TASK_COMMENT` requires all four fields: `task_id`, `comment_text`, `assignee`, and `notify_all`\n- `assignee` on a comment assigns the comment (not the task) to that user\n- Comments are paginated at 25 per page; use `start` (Unix ms) and `start_id` for older pages\n- `CLICKUP_UPDATE_COMMENT` requires all four fields: `comment_id`, `comment_text`, `assignee`, `resolved`\n\n### 4. Manage Team Members and Assignments\n\n**When to use**: User wants to view workspace members, check seat utilization, or look up user details.\n\n**Tool sequence**:\n1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List workspaces and get team_id [Required]\n2. `CLICKUP_GET_WORKSPACE_SEATS` - Check seat utilization (members vs guests) [Required]\n3. `CLICKUP_GET_TEAMS` - List user groups within the workspace [Optional]\n4. `CLICKUP_GET_USER` - Get details for a specific user (Enterprise only) [Optional]\n5. `CLICKUP_GET_CUSTOM_ROLES` - List custom permission roles [Optional]\n\n**Key parameters**:\n- `team_id`: Workspace ID (required for all team operations)\n- `user_id`: Specific user ID for GET_USER\n- `group_ids`: Comma-separated group IDs to filter teams\n\n**Pitfalls**:\n- `CLICKUP_GET_WORKSPACE_SEATS` returns seat counts, not member details; distinguish members from guests\n- `CLICKUP_GET_TEAMS` returns user groups, not workspace members; empty groups does not mean no members\n- `CLICKUP_GET_USER` is only available on ClickUp Enterprise Plan\n- Must repeat workspace seat queries for each workspace in multi-workspace setups\n\n### 5. Filter and Query Tasks\n\n**When to use**: User wants to find tasks with specific filters (status, assignee, dates, tags, custom fields).\n\n**Tool sequence**:\n1. `CLICKUP_GET_TASKS` - Filter tasks in a list with multiple criteria [Required]\n2. `CLICKUP_GET_TASK` - Get full details for individual tasks [Optional]\n\n**Key parameters for CLICKUP_GET_TASKS**:\n- `list_id`: List ID (integer, required)\n- `statuses`: Array of status strings to filter by\n- `assignees`: Array of user ID strings\n- `tags`: Array of tag name strings\n- `due_date_gt` \u002F `due_date_lt`: Unix timestamp in ms for date range\n- `include_closed`: Boolean to include closed tasks\n- `subtasks`: Boolean to include subtasks\n- `order_by`: \"id\", \"created\", \"updated\", or \"due_date\"\n- `page`: Page number starting at 0 (max 100 tasks per page)\n\n**Pitfalls**:\n- Only tasks whose home list matches `list_id` are returned; tasks in sublists are not included\n- Date filters use Unix timestamps in milliseconds\n- Status strings must match exactly; use URL encoding for spaces (e.g., \"to%20do\")\n- Page numbering starts at 0; each page returns up to 100 tasks\n- `custom_fields` filter accepts an array of JSON strings, not objects\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve names to IDs through the hierarchy:\n- **Workspace name -> team_id**: `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` and match by name\n- **Space name -> space_id**: `CLICKUP_GET_SPACES` with `team_id`\n- **Folder name -> folder_id**: `CLICKUP_GET_FOLDERS` with `space_id`\n- **List name -> list_id**: Navigate folders or use `CLICKUP_GET_FOLDERLESS_LISTS`\n- **Task name -> task_id**: `CLICKUP_GET_TASKS` with `list_id` and match by name\n\n### Pagination\n- `CLICKUP_GET_TASKS`: Page-based with `page` starting at 0, max 100 tasks per page\n- `CLICKUP_GET_TASK_COMMENTS`: Uses `start` (Unix ms) and `start_id` for cursor-based paging, max 25 per page\n- Continue fetching until response returns fewer items than the page size\n\n## Known Pitfalls\n\n### ID Formats\n- Workspace\u002FTeam IDs are large integers\n- Space, folder, and list IDs are integers\n- Task IDs are alphanumeric strings (e.g., \"9hz\", \"abc123\")\n- User IDs are integers\n- Comment IDs are integers\n\n### Rate Limits\n- ClickUp enforces rate limits; bulk task creation can trigger 429 responses\n- Honor `Retry-After` header when present\n- Set `notify_all=false` for bulk operations to reduce notification load\n\n### Parameter Quirks\n- `team_id` in the API means Workspace ID, not a user group\n- `status` on tasks is case-sensitive and list-specific\n- Dates are Unix timestamps in **milliseconds** (multiply seconds by 1000)\n- `priority` is an integer 1-4 (1=Urgent, 4=Low), not a string\n- `CLICKUP_CREATE_TASK_COMMENT` marks `assignee` and `notify_all` as required\n- To clear a task description, pass a single space `\" \"` to `CLICKUP_UPDATE_TASK`\n\n### Hierarchy Rules\n- Subtask parent must not itself be a subtask\n- Subtask parent must be in the same list\n- Lists can be folderless (directly in a Space) or inside a Folder\n- Subitem boards are not supported by CLICKUP_CREATE_TASK\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` | (none) |\n| List spaces | `CLICKUP_GET_SPACES` | `team_id` |\n| Get space details | `CLICKUP_GET_SPACE` | `space_id` |\n| List folders | `CLICKUP_GET_FOLDERS` | `space_id` |\n| Get folder details | `CLICKUP_GET_FOLDER` | `folder_id` |\n| Create folder | `CLICKUP_CREATE_FOLDER` | `space_id`, `name` |\n| Folderless lists | `CLICKUP_GET_FOLDERLESS_LISTS` | `space_id` |\n| Get list details | `CLICKUP_GET_LIST` | `list_id` |\n| Create task | `CLICKUP_CREATE_TASK` | `list_id`, `name`, `status`, `assignees` |\n| Update task | `CLICKUP_UPDATE_TASK` | `task_id`, `status`, `priority` |\n| Get task | `CLICKUP_GET_TASK` | `task_id`, `include_subtasks` |\n| List tasks | `CLICKUP_GET_TASKS` | `list_id`, `statuses`, `page` |\n| Delete task | `CLICKUP_DELETE_TASK` | `task_id` |\n| Add comment | `CLICKUP_CREATE_TASK_COMMENT` | `task_id`, `comment_text`, `assignee` |\n| List comments | `CLICKUP_GET_TASK_COMMENTS` | `task_id`, `start`, `start_id` |\n| Update comment | `CLICKUP_UPDATE_COMMENT` | `comment_id`, `comment_text`, `resolved` |\n| Workspace seats | `CLICKUP_GET_WORKSPACE_SEATS` | `team_id` |\n| List user groups | `CLICKUP_GET_TEAMS` | `team_id` |\n| Get user details | `CLICKUP_GET_USER` | `team_id`, `user_id` |\n| Custom roles | `CLICKUP_GET_CUSTOM_ROLES` | `team_id` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,142,1733,"2026-05-16 13:11:12",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"058cad2c-d3f6-4c92-b6f5-ed5c2c7ccbf5","1.0.0","clickup-automation.zip",4186,"uploads\u002Fskills\u002F4c2e42ca-9caa-4d56-a72b-7fc0463f8a86\u002Fclickup-automation.zip","76e3a7cd9ab45a400dbc6a10370dd1b01b33d87a5c59207bcc5ff2fad1d4631d","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":12105}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]