Asana Automation V2

Asana Automation via Rube MCP

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/asana-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.

Asana Automation via Rube MCP Automate Asana operations through Composio's Asana toolkit via Rube MCP.

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 Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. 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

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.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit asana
3. If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth
4. Confirm connection status shows ACTIVE before running any workflows
5. ASANAGETMULTIPLE_WORKSPACES - Get workspace ID [Prerequisite]
6. ASANASEARCHTASKSINWORKSPACE - Search tasks [Optional]
7. ASANAGETTASKSFROMA_PROJECT - List project tasks [Optional]

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.

1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
2. Call RUBE_MANAGE_CONNECTIONS with toolkit asana
3. If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth
4. Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Manage Tasks

When to use: User wants to create, search, list, or organize tasks

Tool sequence:

1. ASANA_GET_MULTIPLE_WORKSPACES - Get workspace ID [Prerequisite]
2. ASANA_SEARCH_TASKS_IN_WORKSPACE - Search tasks [Optional]
3. ASANA_GET_TASKS_FROM_A_PROJECT - List project tasks [Optional]
4. ASANA_CREATE_A_TASK - Create a new task [Optional]
5. ASANA_GET_A_TASK - Get task details [Optional]
6. ASANA_CREATE_SUBTASK - Create a subtask [Optional]
7. ASANA_GET_TASK_SUBTASKS - List subtasks [Optional]

Key parameters:

• workspace: Workspace GID (required for search/creation)
• projects: Array of project GIDs to add task to
• name: Task name
• notes: Task description
• assignee: Assignee (user GID or email)
• due_on: Due date (YYYY-MM-DD)

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:

1. ASANA_GET_WORKSPACE_PROJECTS - List workspace projects [Optional]
2. ASANA_GET_A_PROJECT - Get project details [Optional]
3. ASANA_CREATE_A_PROJECT - Create a new project [Optional]
4. ASANA_GET_SECTIONS_IN_PROJECT - List sections [Optional]
5. ASANA_CREATE_SECTION_IN_PROJECT - Create a new section [Optional]
6. ASANA_ADD_TASK_TO_SECTION - Move task to section [Optional]
7. ASANA_GET_TASKS_FROM_A_SECTION - List tasks in section [Optional]

Key parameters:

• project_gid: Project GID
• name: Project or section name
• workspace: Workspace GID for creation
• task: Task GID for section assignment
• section: Section GID

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:

1. ASANA_GET_TEAMS_IN_WORKSPACE - List workspace teams [Optional]
2. ASANA_GET_USERS_FOR_TEAM - List team members [Optional]
3. ASANA_GET_USERS_FOR_WORKSPACE - List all workspace users [Optional]
4. ASANA_GET_CURRENT_USER - Get authenticated user [Optional]
5. ASANA_GET_MULTIPLE_USERS - Get multiple user details [Optional]

Key parameters:

• workspace_gid: Workspace GID
• team_gid: Team 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:

1. ASANA_SUBMIT_PARALLEL_REQUESTS - Execute multiple API calls in parallel [Required]

Key parameters:

• actions: Array of action objects with method, path, and data

Pitfalls:

• Each action must be a valid Asana API call
• Failed individual requests do not roll back successful ones

Imported: Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Asana connection via RUBE_MANAGE_CONNECTIONS with toolkit asana
• Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @asana-automation-v2 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 @asana-automation-v2 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 @asana-automation-v2 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 @asana-automation-v2 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/skills/asana-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.

Imported Reference Notes

Imported: Quick Reference

Imported: 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 offset parameter
• Check for next_page in response
• Pass offset from next_page.offset for next request

Imported: 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

Imported: 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.