asana-automation

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

1.88x

Quality

66%

Does it follow best practices?

Impact

100%

1.88x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

68%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.

A lean, well-structured single-file skill that gives Claude concrete tool sequences and parameters without padding. Its main weaknesses are the absence of any validation loop for the batch Parallel Operations workflow (capping workflow clarity) and the lack of a single example tool-call payload to ground parameter usage.

Suggestions

Add an explicit validation step and error-recovery loop to the Parallel Operations workflow, e.g. check each result in the ASANA_SUBMIT_PARALLEL_REQUESTS response and report/handle failures before considering the batch complete.

Include one concrete example tool call (e.g. a sample ASANA_CREATE_A_TASK invocation with parameter values) to ground the abstract parameter lists.

Deduplicate the pitfalls content repeated between per-workflow 'Pitfalls' sections and the 'Known Pitfalls' section to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is dense, well-organized reference material with no explanation of concepts Claude already knows; only minor trimming is needed (pitfalls repeated between per-workflow 'Pitfalls' and 'Known Pitfalls', and the Quick Reference table restates the tool sequences).	4 / 5
Actionability	Concrete tool slugs, ordered sequences with [Prerequisite]/[Required] markers, and named parameters with formats (e.g. 'due_on: Due date (YYYY-MM-DD)') make the guidance mostly executable, though no example tool-call payload is shown for any operation.	4 / 5
Workflow Clarity	Sequences are clearly ordered and setup includes validation checkpoints ('Confirm connection status shows ACTIVE'), but the Parallel Operations workflow is a batch operation with no validation or verification loop, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	With no bundle files, the single SKILL.md is well-structured into workflows, common patterns, pitfalls, and a quick reference, though the 20-row table is borderline inline API reference that could live in a separate file.	4 / 5
	Total	15 / 20 Passed

Description

65%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.

A concise, distinctive description with good natural keywords, but it is action-light (one generic verb) and entirely lacks a 'when to use' trigger clause, which both limits completeness and blurs when the skill should activate. Adding an explicit 'Use when...' clause and naming the distinct operations (create, search, assign, organize) would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Asana, Asana tasks, projects, or to-do management.'

Replace the single generic verb 'Automate' with the distinct operations supported, e.g. 'Create, search, and organize Asana tasks, projects, sections, teams, and workspaces.'

Include one or two common user synonyms such as 'to-dos' or 'project management' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and five concrete object types ("tasks, projects, sections, teams, workspaces") but relies on a single generic verb ("Automate"), matching anchor 3's 'concrete actions but not comprehensive' rather than anchor 4's multiple distinct actions.	3 / 5
Completeness	It clearly answers 'what' (automating Asana tasks, projects, sections, teams, workspaces via Rube MCP) but contains no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Asana", "tasks", "projects", and "teams" are natural terms users would say, giving good keyword coverage, though common variations like "to-dos", "assign", "due dates", and "project management" are missing.	4 / 5
Distinctiveness Conflict Risk	"Asana" plus entity-specific terms ("sections", "workspaces", "teams") establish a clear niche with distinct triggers and minimal risk of triggering the wrong skill.	5 / 5
	Total	15 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/asana-automation/SKILL.md
Commit: c9856ea

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.