ClickUp Automation via Rube MCP workflow skill. Use this skill when the user needs Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
ClickUp Automation via Rube MCP workflow skill. Use this skill when the user needs Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/clickup-automation from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
ClickUp Automation via Rube MCP Automate ClickUp project management workflows including task creation and updates, workspace hierarchy navigation, comments, and team member management through Composio's ClickUp toolkit.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
Call RUBEMANAGECONNECTIONS with toolkit clickup
If connection is not ACTIVE, follow the returned auth link to complete ClickUp OAuth
Confirm connection status shows ACTIVE before running any workflows
CLICKUPGETAUTHORIZEDTEAMSWORKSPACES - Get workspace/team IDs [Prerequisite]
CLICKUPGETSPACES - List spaces in the workspace [Prerequisite]
CLICKUPGETFOLDERS - List folders in a space [Prerequisite]
Imported Workflow Notes
Imported: Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit clickup
If connection is not ACTIVE, follow the returned auth link to complete ClickUp OAuth
Confirm connection status shows ACTIVE before running any workflows
Imported: Core Workflows
1. Create and Manage Tasks
When to use: User wants to create tasks, subtasks, update task properties, or list tasks in a ClickUp list.
Tool sequence:
CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES - Get workspace/team IDs [Prerequisite]
CLICKUP_GET_SPACES - List spaces in the workspace [Prerequisite]
CLICKUP_GET_FOLDERS - List folders in a space [Prerequisite]
CLICKUP_GET_FOLDERLESS_LISTS - Get lists not inside folders [Optional]
CLICKUP_GET_LIST - Validate list and check available statuses [Prerequisite]
CLICKUP_CREATE_TASK - Create a task in the target list [Required]
CLICKUP_CREATE_TASK (with parent) - Create subtask under a parent task [Optional]
parent: Parent task ID string for creating subtasks
tags: Array of tag name strings
time_estimate: Estimated time in milliseconds
Pitfalls:
status is case-sensitive and must match an existing status in the list; use CLICKUP_GET_LIST to check available statuses
due_date and start_date are Unix timestamps in milliseconds, not seconds
Subtask parent must be a task (not another subtask) in the same list
notify_all triggers watcher notifications; set to false for bulk operations
Retries can create duplicates; track created task IDs to avoid re-creation
custom_item_id for milestones (ID 1) is subject to workspace plan quotas
2. Navigate Workspace Hierarchy
When to use: User wants to browse or manage the ClickUp workspace structure (Workspaces > Spaces > Folders > Lists).
Tool sequence:
CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES - List all accessible workspaces [Required]
CLICKUP_GET_SPACES - List spaces within a workspace [Required]
CLICKUP_GET_SPACE - Get details for a specific space [Optional]
CLICKUP_GET_FOLDERS - List folders in a space [Required]
CLICKUP_GET_FOLDER - Get details for a specific folder [Optional]
CLICKUP_CREATE_FOLDER - Create a new folder in a space [Optional]
CLICKUP_GET_FOLDERLESS_LISTS - List lists not inside any folder [Required]
CLICKUP_GET_LIST - Get list details including statuses and custom fields [Optional]
Key parameters:
team_id: Workspace ID from GET_AUTHORIZED_TEAMS_WORKSPACES (required for spaces)
space_id: Space ID (required for folders and folderless lists)
folder_id: Folder ID (required for GET_FOLDER)
list_id: List ID (required for GET_LIST)
archived: Boolean filter for archived/active items
Pitfalls:
ClickUp hierarchy is: Workspace (Team) > Space > Folder > List > Task
Lists can exist directly under Spaces (folderless) or inside Folders
Must use CLICKUP_GET_FOLDERLESS_LISTS to find lists not inside folders; CLICKUP_GET_FOLDERS only returns folders
team_id in ClickUp API refers to the Workspace ID, not a user group
3. Add Comments to Tasks
When to use: User wants to add comments, review existing comments, or manage comment threads on tasks.
Tool sequence:
CLICKUP_GET_TASK - Verify task exists and get task_id [Prerequisite]
CLICKUP_CREATE_TASK_COMMENT - Add a new comment to the task [Required]
CLICKUP_GET_TASK_COMMENTS - List existing comments on the task [Optional]
CLICKUP_UPDATE_COMMENT - Edit comment text, assignee, or resolution status [Optional]
Key parameters for CLICKUP_CREATE_TASK_COMMENT:
task_id: Task ID string (required)
comment_text: Comment content with ClickUp formatting support (required)
assignee: User ID to assign the comment to (required)
notify_all: true/false for watcher notifications (required)
Key parameters for CLICKUP_GET_TASK_COMMENTS:
task_id: Task ID string (required)
start / start_id: Pagination for older comments (max 25 per page)
Pitfalls:
CLICKUP_CREATE_TASK_COMMENT requires all four fields: task_id, comment_text, assignee, and notify_all
assignee on a comment assigns the comment (not the task) to that user
Comments are paginated at 25 per page; use start (Unix ms) and start_id for older pages
CLICKUP_UPDATE_COMMENT requires all four fields: comment_id, comment_text, assignee, resolved
4. Manage Team Members and Assignments
When to use: User wants to view workspace members, check seat utilization, or look up user details.
Tool sequence:
CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES - List workspaces and get team_id [Required]
CLICKUP_GET_WORKSPACE_SEATS - Check seat utilization (members vs guests) [Required]
CLICKUP_GET_TEAMS - List user groups within the workspace [Optional]
CLICKUP_GET_USER - Get details for a specific user (Enterprise only) [Optional]
CLICKUP_GET_CUSTOM_ROLES - List custom permission roles [Optional]
Key parameters:
team_id: Workspace ID (required for all team operations)
user_id: Specific user ID for GET_USER
group_ids: Comma-separated group IDs to filter teams
Pitfalls:
CLICKUP_GET_WORKSPACE_SEATS returns seat counts, not member details; distinguish members from guests
CLICKUP_GET_TEAMS returns user groups, not workspace members; empty groups does not mean no members
CLICKUP_GET_USER is only available on ClickUp Enterprise Plan
Must repeat workspace seat queries for each workspace in multi-workspace setups
5. Filter and Query Tasks
When to use: User wants to find tasks with specific filters (status, assignee, dates, tags, custom fields).
Tool sequence:
CLICKUP_GET_TASKS - Filter tasks in a list with multiple criteria [Required]
CLICKUP_GET_TASK - Get full details for individual tasks [Optional]
Key parameters for CLICKUP_GET_TASKS:
list_id: List ID (integer, required)
statuses: Array of status strings to filter by
assignees: Array of user ID strings
tags: Array of tag name strings
due_date_gt / due_date_lt: Unix timestamp in ms for date range
include_closed: Boolean to include closed tasks
subtasks: Boolean to include subtasks
order_by: "id", "created", "updated", or "due_date"
page: Page number starting at 0 (max 100 tasks per page)
Pitfalls:
Only tasks whose home list matches list_id are returned; tasks in sublists are not included
Date filters use Unix timestamps in milliseconds
Status strings must match exactly; use URL encoding for spaces (e.g., "to%20do")
Page numbering starts at 0; each page returns up to 100 tasks
custom_fields filter accepts an array of JSON strings, not objects
Imported: Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active ClickUp connection via RUBE_MANAGE_CONNECTIONS with toolkit clickup
Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Examples
Example 1: Ask for the upstream workflow directly
Use @clickup-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @clickup-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @clickup-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @clickup-automation using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/clickup-automation, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Quick Reference
Task
Tool Slug
Key Params
List workspaces
CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES
(none)
List spaces
CLICKUP_GET_SPACES
team_id
Get space details
CLICKUP_GET_SPACE
space_id
List folders
CLICKUP_GET_FOLDERS
space_id
Get folder details
CLICKUP_GET_FOLDER
folder_id
Create folder
CLICKUP_CREATE_FOLDER
space_id, name
Folderless lists
CLICKUP_GET_FOLDERLESS_LISTS
space_id
Get list details
CLICKUP_GET_LIST
list_id
Create task
CLICKUP_CREATE_TASK
list_id, name, status, assignees
Update task
CLICKUP_UPDATE_TASK
task_id, status, priority
Get task
CLICKUP_GET_TASK
task_id, include_subtasks
List tasks
CLICKUP_GET_TASKS
list_id, statuses, page
Delete task
CLICKUP_DELETE_TASK
task_id
Add comment
CLICKUP_CREATE_TASK_COMMENT
task_id, comment_text, assignee
List comments
CLICKUP_GET_TASK_COMMENTS
task_id, start, start_id
Update comment
CLICKUP_UPDATE_COMMENT
comment_id, comment_text, resolved
Workspace seats
CLICKUP_GET_WORKSPACE_SEATS
team_id
List user groups
CLICKUP_GET_TEAMS
team_id
Get user details
CLICKUP_GET_USER
team_id, user_id
Custom roles
CLICKUP_GET_CUSTOM_ROLES
team_id
Imported: Common Patterns
ID Resolution
Always resolve names to IDs through the hierarchy:
Workspace name -> team_id: CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES and match by name
Space name -> space_id: CLICKUP_GET_SPACES with team_id
Folder name -> folder_id: CLICKUP_GET_FOLDERS with space_id
List name -> list_id: Navigate folders or use CLICKUP_GET_FOLDERLESS_LISTS
Task name -> task_id: CLICKUP_GET_TASKS with list_id and match by name
Pagination
CLICKUP_GET_TASKS: Page-based with page starting at 0, max 100 tasks per page
CLICKUP_GET_TASK_COMMENTS: Uses start (Unix ms) and start_id for cursor-based paging, max 25 per page
Continue fetching until response returns fewer items than the page size
Imported: Known Pitfalls
ID Formats
Workspace/Team IDs are large integers
Space, folder, and list IDs are integers
Task IDs are alphanumeric strings (e.g., "9hz", "abc123")
