Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Rube MCP setup and workspace-first task creation
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS with asana
0%
100%
ACTIVE status check
20%
100%
Workspace lookup first
60%
100%
Workspace GID for project lookup
75%
100%
Project GID extracted
100%
100%
GIDs treated as strings
87%
100%
ASANA_CREATE_A_TASK tool used
50%
100%
workspace param on task creation
100%
100%
projects param on task creation
100%
100%
All three tasks created
100%
100%
Without context: $0.5698 · 2m 47s · 28 turns · 30 in / 9,217 out tokens
With context: $0.3511 · 1m 28s · 17 turns · 20 in / 4,660 out tokens
Project and section organization with ID resolution
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS asana
0%
100%
ASANA_GET_MULTIPLE_WORKSPACES for workspace GID
50%
100%
Workspace GID used in project creation
75%
100%
Existing sections checked first
87%
100%
ASANA_CREATE_SECTION_IN_PROJECT for sections
75%
100%
Task search is workspace-scoped
80%
100%
ASANA_ADD_TASK_TO_SECTION for moves
66%
100%
Section GID resolved before use
90%
100%
GIDs treated as strings
75%
100%
Both tasks moved correctly
100%
100%
Without context: $0.2512 · 1m 8s · 12 turns · 19 in / 4,148 out tokens
With context: $0.3599 · 1m 32s · 17 turns · 354 in / 5,275 out tokens
Parallel bulk task operations
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS asana
0%
100%
Workspace GID via ASANA_GET_MULTIPLE_WORKSPACES
0%
100%
Project GID via ASANA_GET_WORKSPACE_PROJECTS
0%
100%
ASANA_SUBMIT_PARALLEL_REQUESTS for bulk updates
0%
100%
actions array structure
40%
100%
All three tasks in batch
100%
100%
No-rollback behavior noted
100%
100%
Cursor-based pagination described
80%
100%
GIDs treated as strings
100%
100%
ASANA_GET_TASKS_FROM_A_PROJECT used
0%
100%
Without context: $0.3151 · 1m 32s · 14 turns · 21 in / 5,196 out tokens
With context: $0.3697 · 1m 30s · 18 turns · 180 in / 4,484 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.