Antigravity-awesome-skills asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
git clone https://github.com/sickn33/antigravity-awesome-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/sickn33/antigravity-awesome-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/antigravity-awesome-skills/skills/asana-automation" ~/.claude/skills/sickn33-antigravity-awesome-skills-asana-automation-77f187 && rm -rf "$T"
plugins/antigravity-awesome-skills/skills/asana-automation/SKILL.mdAsana Automation via Rube MCP
Automate Asana operations through Composio's Asana toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Asana connection via
with toolkitRUBE_MANAGE_CONNECTIONSasana - Always call
first to get current tool schemasRUBE_SEARCH_TOOLS
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
respondsRUBE_SEARCH_TOOLS - Call
with toolkitRUBE_MANAGE_CONNECTIONSasana - If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Tasks
When to use: User wants to create, search, list, or organize tasks
Tool sequence:
- Get workspace ID [Prerequisite]ASANA_GET_MULTIPLE_WORKSPACES
- Search tasks [Optional]ASANA_SEARCH_TASKS_IN_WORKSPACE
- List project tasks [Optional]ASANA_GET_TASKS_FROM_A_PROJECT
- Create a new task [Optional]ASANA_CREATE_A_TASK
- Get task details [Optional]ASANA_GET_A_TASK
- Create a subtask [Optional]ASANA_CREATE_SUBTASK
- List subtasks [Optional]ASANA_GET_TASK_SUBTASKS
Key parameters:
: Workspace GID (required for search/creation)workspace
: Array of project GIDs to add task toprojects
: Task namename
: Task descriptionnotes
: Assignee (user GID or email)assignee
: Due date (YYYY-MM-DD)due_on
Pitfalls:
- Workspace GID is required for most operations; get it first
- Task GIDs are returned as strings, not integers
- Search is workspace-scoped, not project-scoped
2. Manage Projects and Sections
When to use: User wants to create projects, manage sections, or organize tasks
Tool sequence:
- List workspace projects [Optional]ASANA_GET_WORKSPACE_PROJECTS
- Get project details [Optional]ASANA_GET_A_PROJECT
- Create a new project [Optional]ASANA_CREATE_A_PROJECT
- List sections [Optional]ASANA_GET_SECTIONS_IN_PROJECT
- Create a new section [Optional]ASANA_CREATE_SECTION_IN_PROJECT
- Move task to section [Optional]ASANA_ADD_TASK_TO_SECTION
- List tasks in section [Optional]ASANA_GET_TASKS_FROM_A_SECTION
Key parameters:
: Project GIDproject_gid
: Project or section namename
: Workspace GID for creationworkspace
: Task GID for section assignmenttask
: Section GIDsection
Pitfalls:
- Projects belong to workspaces; workspace GID is needed for creation
- Sections are ordered within a project
- DUPLICATE_PROJECT creates a copy with optional task inclusion
3. Manage Teams and Users
When to use: User wants to list teams, team members, or workspace users
Tool sequence:
- List workspace teams [Optional]ASANA_GET_TEAMS_IN_WORKSPACE
- List team members [Optional]ASANA_GET_USERS_FOR_TEAM
- List all workspace users [Optional]ASANA_GET_USERS_FOR_WORKSPACE
- Get authenticated user [Optional]ASANA_GET_CURRENT_USER
- Get multiple user details [Optional]ASANA_GET_MULTIPLE_USERS
Key parameters:
: Workspace GIDworkspace_gid
: Team GIDteam_gid
Pitfalls:
- Users are workspace-scoped
- Team membership requires the team GID
4. Parallel Operations
When to use: User needs to perform bulk operations efficiently
Tool sequence:
- Execute multiple API calls in parallel [Required]ASANA_SUBMIT_PARALLEL_REQUESTS
Key parameters:
: Array of action objects with method, path, and dataactions
Pitfalls:
- Each action must be a valid Asana API call
- Failed individual requests do not roll back successful ones
Common Patterns
ID Resolution
Workspace name -> GID:
1. Call ASANA_GET_MULTIPLE_WORKSPACES 2. Find workspace by name 3. Extract gid field
Project name -> GID:
1. Call ASANA_GET_WORKSPACE_PROJECTS with workspace GID 2. Find project by name 3. Extract gid field
Pagination
- Asana uses cursor-based pagination with
parameteroffset - Check for
in responsenext_page - Pass
fromoffset
for next requestnext_page.offset
Known Pitfalls
GID Format:
- All Asana IDs are strings (GIDs), not integers
- GIDs are globally unique identifiers
Workspace Scoping:
- Most operations require a workspace context
- Tasks, projects, and users are workspace-scoped
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| List workspaces | ASANA_GET_MULTIPLE_WORKSPACES | (none) |
| Search tasks | ASANA_SEARCH_TASKS_IN_WORKSPACE | workspace, text |
| Create task | ASANA_CREATE_A_TASK | workspace, name, projects |
| Get task | ASANA_GET_A_TASK | task_gid |
| Create subtask | ASANA_CREATE_SUBTASK | parent, name |
| List subtasks | ASANA_GET_TASK_SUBTASKS | task_gid |
| Project tasks | ASANA_GET_TASKS_FROM_A_PROJECT | project_gid |
| List projects | ASANA_GET_WORKSPACE_PROJECTS | workspace |
| Create project | ASANA_CREATE_A_PROJECT | workspace, name |
| Get project | ASANA_GET_A_PROJECT | project_gid |
| Duplicate project | ASANA_DUPLICATE_PROJECT | project_gid |
| List sections | ASANA_GET_SECTIONS_IN_PROJECT | project_gid |
| Create section | ASANA_CREATE_SECTION_IN_PROJECT | project_gid, name |
| Add to section | ASANA_ADD_TASK_TO_SECTION | section, task |
| Section tasks | ASANA_GET_TASKS_FROM_A_SECTION | section_gid |
| List teams | ASANA_GET_TEAMS_IN_WORKSPACE | workspace_gid |
| Team members | ASANA_GET_USERS_FOR_TEAM | team_gid |
| Workspace users | ASANA_GET_USERS_FOR_WORKSPACE | workspace_gid |
| Current user | ASANA_GET_CURRENT_USER | (none) |
| Parallel requests | ASANA_SUBMIT_PARALLEL_REQUESTS | actions |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.