asana-automation

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

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./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 inclusion of internal implementation guidance ('Always search tools first for current schemas') wastes space that could be used for trigger terms and explicit usage conditions.

Suggestions

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

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

Move the implementation detail ('Always search tools first for current schemas') out of the description and into the skill body, freeing space for natural trigger terms like 'project management', 'assign task', 'due date'.

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, not a usage trigger. 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 naming and workflow sequencing. Its main weaknesses are the lack of concrete executable examples (actual MCP tool call syntax with real parameters and expected responses), missing validation/error-handling checkpoints in workflows, and some content redundancy between the workflow sections and the quick reference table.

Suggestions

Add at least one fully concrete, copy-paste-ready MCP tool call example with actual parameters and expected response structure (e.g., a complete ASANA_CREATE_A_TASK invocation with sample workspace GID, name, and the expected response format).

Add explicit validation steps to workflows — e.g., after creating a task, verify the returned GID; after parallel operations, check the response array for individual failures and provide a retry pattern.

Remove the redundant 'Known Pitfalls' section since GID format and workspace scoping are already covered in individual workflow pitfalls, or consolidate all pitfalls into one section and remove them from individual workflows.

Convert the pseudocode in 'Common Patterns' (ID Resolution) into actual MCP tool call syntax showing the exact parameters and how to extract the GID from the response.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy — the quick reference table largely duplicates information already covered in the core workflows sections. The 'Known Pitfalls' section repeats GID format and workspace scoping points already mentioned in individual workflow pitfalls. The boilerplate 'When to Use' and 'Limitations' sections add little value.	2 / 3
Actionability	The skill provides specific tool names, parameter lists, and sequences, which is helpful. However, the code examples under 'Common Patterns' are pseudocode/plain text rather than actual executable MCP tool calls with concrete parameter examples. No real input/output examples are shown for any tool invocation.	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 that a task was created successfully, no error handling guidance, and the parallel operations section explicitly notes that failed requests don't roll back but provides no guidance on how to detect or recover from partial failures.	2 / 3
Progressive Disclosure	The content is reasonably well-structured with clear section headers and a useful quick reference table. However, with no bundle files, all content is inline in a single long document (~150+ lines). The pagination section, parallel operations, and detailed parameter lists could benefit from being split into referenced files for a cleaner overview.	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: sickn33/antigravity-awesome-skills
Commit: 9e5d4dd

Reviewed: 6 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.