asana-automation

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

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/asana-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

The skill body delivers concrete, well-sequenced MCP tool guidance with useful pitfalls and parameter listings, but it is padded with generic boilerplate, a duplicative reference table, and lacks validation steps for its batch operation. Splitting reference material into a bundled file and adding verification guidance for parallel requests would raise quality notably.

Suggestions

Move the 20-row Quick Reference table to a references/ file (e.g., tools.md) and point to it from the body, trimming SKILL.md to the workflows and patterns.

Add validation/rollback guidance for ASANA_SUBMIT_PARALLEL_REQUESTS, e.g., verify each action's response status and report partial failures before retrying only the failed actions.

Replace the boilerplate "When to Use" and generic "Limitations" sections with concrete, Asana-specific guidance or remove them.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (tool sequences, key parameters, pitfalls), but the boilerplate "When to Use" section ("This skill is applicable to execute the workflow or actions described in the overview"), the generic Limitations section, and a Quick Reference table that largely duplicates the workflow tool lists add padding that could be trimmed, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Guidance is mostly executable: exact tool slugs (e.g., ASANA_CREATE_A_TASK), ordered sequences with [Prerequisite]/[Optional] markers, named key parameters, and pitfalls like "Task GIDs are returned as strings, not integers". It falls short of 5 because no example tool-call payloads or concrete argument values are shown for the common cases.	4 / 5
Workflow Clarity	Sequences are present and the setup section has an explicit validation checkpoint ("Confirm connection status shows ACTIVE before running any workflows"), but the batch workflow (ASANA_SUBMIT_PARALLEL_REQUESTS) has no validation/verification or rollback guidance despite acknowledging "Failed individual requests do not roll back successful ones" — the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Sections are well-organized, but no bundle files exist and a 20-row API-reference table is inlined in SKILL.md — content that belongs in a separate reference file — fitting the 'some structure but content that should be separate is inline' anchor; it is above a 2 because the structure and navigation within the file itself are clear.	3 / 5
	Total	13 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 distinct, well-scoped niche and names the domain objects it covers, but it lacks any explicit 'when to use' trigger clause and relies on a single generic action verb. Adding a 'Use when...' clause with natural user phrasings and a few concrete operations would substantially improve it.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to create, search, or organize Asana tasks, projects, sections, or teams."

Replace the generic "Automate" with 2-3 concrete operations (e.g., "create and search tasks, organize projects and sections, list team members").

Include natural synonyms users might say (to-dos, assignees, due dates) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (Asana via Rube MCP/Composio) and its objects ("tasks, projects, sections, teams, workspaces"), but the only action verb is the generic "Automate"; it does not enumerate concrete operations like create, search, assign, or move, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.	3 / 5
Completeness	The 'what' is clear (automating Asana tasks, projects, sections, teams, workspaces through Rube MCP), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3; it is not a 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"Asana", "tasks", and "projects" are terms users would naturally say, but the description misses common variations and synonyms (e.g., to-dos, assignees, due dates, tickets, boards), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	"Asana" plus the named integration path (Rube MCP, Composio) is a clear niche with distinct triggers and minimal conflict risk against other skills, matching the top anchor.	5 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/asana-automation/SKILL.md
Commit: 7b534bc

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