asana-automation

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

1.88x

Quality

45%

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

40%

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 a clear niche (Asana automation via a specific MCP integration) which makes it distinctive, but it lacks concrete action verbs describing what operations are supported and entirely omits a 'Use when...' clause. The listing of entity types (tasks, projects, etc.) is helpful but insufficient without specifying what can be done with them.

Suggestions

Add a 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks to create, update, assign, or query Asana tasks, projects, or workspaces.'

Replace the vague 'Automate Asana tasks' with specific actions like 'Create, update, assign, and search Asana tasks; manage projects and sections; list teams and workspaces.'

Move the implementation detail ('Always search tools first for current schemas') out of the description or rephrase it as internal guidance, since it doesn't help with skill selection.

Dimension	Reasoning	Score
Specificity	Names the domain (Asana) and lists entity types (tasks, projects, sections, teams, workspaces), but doesn't describe concrete actions beyond the vague 'automate'. What specific operations—create, update, move, assign, query?	2 / 3
Completeness	Provides a partial 'what' (automate Asana tasks) but has no explicit 'when' clause—no 'Use when...' or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail for Claude, not a trigger condition. Per rubric, missing 'Use when...' caps completeness at 2, and the 'what' is also weak, so this scores 1.	1 / 3
Trigger Term Quality	Includes 'Asana', 'tasks', 'projects', 'sections', 'teams', 'workspaces' which are relevant keywords, but misses natural user phrases like 'assign task', 'create project', 'move to section', 'due date', or 'project management'. 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Asana' and 'Rube MCP (Composio)' creates a very clear niche. It's unlikely to conflict with other skills since it targets a specific third-party tool integration.	3 / 3
	Total	8 / 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 names and parameter documentation. Its main weaknesses are redundancy between sections (pitfalls repeated, quick reference duplicating workflow content), lack of concrete executable examples showing actual tool invocations with real parameters and expected responses, and missing validation/error-handling steps in workflows involving bulk or destructive operations.

Suggestions

Add at least one concrete, end-to-end example showing actual tool calls with real parameters and expected response shapes (e.g., creating a task from scratch including the workspace lookup).

Remove duplicated pitfall information — consolidate into either per-workflow pitfalls or the 'Known Pitfalls' section, not both.

Add explicit validation/verification steps after task creation and parallel operations (e.g., 'Verify task was created by calling ASANA_GET_A_TASK with the returned GID').

Consider splitting the quick reference table into a separate REFERENCE.md file to reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but has 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, though it doesn't over-explain concepts Claude already knows.	2 / 3
Actionability	The skill provides specific tool names, parameter lists, and tool 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	The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). The core workflows list tool sequences but mark nearly everything as [Optional], which reduces clarity about what order to actually follow. There are no explicit validation/verification steps after task creation or bulk operations, and the parallel operations section notes that failed requests don't roll back but provides no error-handling guidance.	2 / 3
Progressive Disclosure	The content is well-sectioned with headers and a quick reference table, but it's a monolithic file with no bundle files to offload detail into. The quick reference table and the detailed workflow sections contain overlapping information that could be split. The external link to Composio docs is helpful but the skill itself could benefit from separating the reference table or detailed workflows into supporting files.	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: d065ead

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.