asana-automation

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

1.92x

Quality

48%

Does it follow best practices?

Impact

96%

1.92x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-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 Asana as the target domain and lists relevant entity types, providing reasonable distinctiveness. However, it lacks specific action verbs, natural user trigger terms, and critically missing any 'Use when...' guidance that would help Claude know when to select this skill.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Asana, wants to create/update tasks, manage projects, or organize work in Asana'

Replace generic 'automate' with specific action verbs: 'Create, update, assign, and organize Asana tasks; manage projects and sections; query workspaces and teams'

Add natural user terms like 'to-do list', 'assign task', 'due date', 'project board' that users would actually say when needing Asana help

Dimension	Reasoning	Score
Specificity	Names the domain (Asana) and lists entity types (tasks, projects, sections, teams, workspaces) but doesn't describe concrete actions beyond generic 'automate'. Missing specific verbs like 'create', 'update', 'assign', 'move'.	2 / 3
Completeness	Describes what at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. The instruction to 'search tools first' is operational guidance for Claude, not selection criteria.	1 / 3
Trigger Term Quality	Includes 'Asana', 'tasks', 'projects' which users would naturally say, but missing common variations like 'to-do', 'assign', 'due date', 'project management'. 'Rube MCP (Composio)' is technical jargon users wouldn't use.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Asana specifically, which is a distinct product. Unlikely to conflict with other project management tools (Jira, Trello, etc.) due to explicit Asana naming.	3 / 3
	Total	8 / 12 Passed

Implementation

57%

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 comprehensive reference for Asana automation via Rube MCP with good organization and coverage of operations. However, it lacks concrete executable examples (actual tool calls with parameters and expected responses) and validation/error handling steps in workflows. The content would benefit from being more actionable with real examples rather than listing tool names and parameters.

Suggestions

Add concrete tool call examples with actual parameters and expected response structures, e.g., show a complete ASANA_CREATE_A_TASK call with all required fields and sample response

Include validation steps in workflows, such as verifying task creation succeeded by checking the response for the new task GID

Remove the Quick Reference table or the detailed workflow sections to reduce redundancy - one comprehensive reference is sufficient

Add error handling guidance for common failure scenarios (e.g., invalid GID, permission denied, rate limiting)

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information already covered in the Core Workflows sections. The setup section and prerequisites could be tighter.	2 / 3
Actionability	Tool sequences are listed but lack executable examples. The ID Resolution patterns use pseudocode-style descriptions rather than actual tool call examples with parameters. No concrete input/output examples are provided.	2 / 3
Workflow Clarity	Workflows have clear sequences with prerequisites marked, but lack validation checkpoints. The Setup section has a good verification flow, but Core Workflows don't include error handling or validation steps after operations.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections: Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference. The structure allows easy navigation without requiring external file references for this scope.	3 / 3
	Total	9 / 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: boisenoise/skills-collections
Commit: 5c5ae21

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