CtrlK
BlogDocsLog inGet started
Tessl Logo

asana-automation

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is asana-automation in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is a well-structured, actionable reference for Asana MCP operations, but it is held back by redundant sections, generic boilerplate, and the absence of validation checkpoints in its batch/create workflows.

Suggestions

Add explicit validation/verification steps to the Parallel Operations and task-creation workflows (e.g., verify created task GIDs, confirm batch results) to lift workflow clarity above the batch-operation cap.

Remove duplication by either dropping the 'Known Pitfalls' section or the 'Quick Reference' table, keeping the reference in one place.

Replace the generic 'When to Use' and 'Limitations' boilerplate with concise, skill-specific guidance or remove it.

DimensionReasoningScore

Conciseness

Mostly efficient reference material, but the 'Known Pitfalls' section repeats per-workflow pitfalls, the Quick Reference table duplicates the tool sequences, and the 'When to Use'/'Limitations' sections are generic boilerplate that could be tightened.

3 / 5

Actionability

Concrete numbered tool sequences with [Prerequisite]/[Optional] tags, explicit key parameters, and a Quick Reference mapping task to tool slug and params give mostly executable guidance, with minor gaps (no full example call payloads).

4 / 5

Workflow Clarity

Sequences are clearly numbered, but the batch 'Parallel Operations' workflow and create operations lack validation/verification checkpoints, so per the destructive/batch cap workflow clarity is held at 3.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no broken or deeply nested references; held at 4 rather than 5 because the large inline Quick Reference table duplicates earlier content and no detail is split into separate reference files.

4 / 5

Total

14

/

20

Passed

Description

70%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 clearly communicates a distinct Asana-automation niche with good keyword coverage, but it lacks an explicit 'when to use' trigger clause, which caps completeness and limits overall quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when the user wants to create or organize Asana tasks, projects, or sections').

Replace the generic verb 'Automate' with a few concrete action verbs (create, search, list, move) to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the Asana domain and enumerates five concrete capability areas ('tasks, projects, sections, teams, workspaces'), though the governing verb ('Automate') is generic rather than a list of distinct actions, leaving it just below the comprehensive-action anchor of 5.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' trigger clause — 'Always search tools first for current schemas' is a behavioral instruction, not a usage trigger, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural Asana-domain keywords ('Asana tasks', 'projects', 'sections', 'teams', 'workspaces') align with what users would say, with good but not exhaustive coverage; not a 5 because no synonym variations or explicit trigger phrases are included.

4 / 5

Distinctiveness Conflict Risk

The Asana-specific niche via Rube MCP (Composio) is clearly delimited with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
boisenoise/skills-collections
Reviewed

Table of Contents

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.