[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8ZTX433P8JSVDK0FY2DKC":3,"skill-same:01M7E8ZTX433P8JSVDK0FY2DKC":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7E8ZTX433P8JSVDK0FY2DKC","clickup-automation",null,"Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fautomation\u002Fclickup-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\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## Example\n\n**User request:**\n\n> Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio).\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","# 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## Example\n\n**User request:**\n\n> Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio).\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",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fautomation\u002Fclickup-automation","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill clickup-automation",{"tool":39,"command":40},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill clickup-automation",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill clickup-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fautomation\u002Fclickup-automation\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]