asana-automation

Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.

1.88x

Quality

41%

Does it follow best practices?

Impact

100%

1.88x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/asana-automation/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the domain (Asana via Rube MCP/Composio) and lists relevant entity types, but lacks concrete action verbs and an explicit 'Use when...' clause. It reads more like a brief label than a discriminating description that would help Claude reliably select this skill from a large pool. The implementation note about searching tools first is useful internally but doesn't aid skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, update, assign, or manage Asana tasks, projects, or workspaces.'

Replace the vague 'Automate Asana tasks' with specific action verbs: 'Create, update, assign, and search Asana tasks; manage projects, sections, teams, and workspaces.'

Include natural trigger terms users would say, such as 'assign task', 'create project in Asana', 'Asana due date', 'move task to section'.

Dimension	Reasoning	Score
Specificity	It names the domain (Asana) and lists entity types (tasks, projects, sections, teams, workspaces) but doesn't describe concrete actions beyond the vague 'automate'. It lacks specific verbs like 'create', 'update', 'assign', 'move'.	2 / 3
Completeness	It partially addresses 'what' (automate Asana tasks) but there is no explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail, not a trigger. Missing 'when' caps this at 2 per guidelines, but the 'what' is also weak, so scoring at 1.	1 / 3
Trigger Term Quality	Includes 'Asana', 'tasks', 'projects', 'sections', 'teams', 'workspaces' which are relevant keywords users might say. However, it misses common action-oriented terms like 'assign task', 'create project', 'due date', 'Composio' alone is not a natural user term. Coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Asana' and 'Rube MCP (Composio)' provides some distinctiveness, but the generic 'automate tasks' phrasing could overlap with other task management or project management skills. The Asana specificity helps but the description is not sharply delineated.	2 / 3
	Total	7 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid structural overview of Asana automation via Rube MCP with clear tool naming and parameter documentation. Its main weaknesses are the lack of concrete executable examples (actual tool call syntax with real parameters and expected responses), missing validation/verification steps in workflows, and some content redundancy between pitfall sections and the quick reference table duplicating workflow content.

Suggestions

Add at least one fully concrete, executable example showing an actual RUBE_SEARCH_TOOLS call and a subsequent Asana tool call with real parameter values and expected response structure.

Add validation checkpoints to workflows — e.g., after creating a task, verify it exists by calling ASANA_GET_A_TASK and checking the response, especially for the parallel operations workflow where partial failures are possible.

Remove the 'Known Pitfalls' section and consolidate its content into the per-workflow pitfall sections to eliminate redundancy.

Consider splitting the quick reference table into a separate REFERENCE.md file to reduce the main skill's length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but contains some redundancy — the 'Known Pitfalls' section repeats information already stated in per-workflow pitfall sections (e.g., GID format, workspace scoping). The quick reference table duplicates information from the workflow sections. Some trimming would improve token efficiency.	2 / 3
Actionability	The skill provides specific tool names, parameter lists, and sequences, which is helpful. However, the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual executable tool calls with concrete parameter examples. No real input/output examples are shown — e.g., what a RUBE_SEARCH_TOOLS call looks like or what a response contains.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with numbered steps and labeled as prerequisite/optional, which is good. However, there are no validation checkpoints — no steps to verify task creation succeeded, no error handling guidance, and the parallel operations workflow explicitly notes that 'failed individual requests do not roll back successful ones' without providing a verification or recovery strategy.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and a useful quick reference table. However, with no bundle files, all content is inline in a single file that runs quite long (~150 lines of substantive content). The quick reference table and detailed workflow sections could benefit from separation, and the external link to composio.dev is the only reference provided.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: 364c6b2

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.