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.

57

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable, with concrete tool sequences, parameters, and pitfalls for each Asana workflow. It loses points for duplicated pitfalls and boilerplate sections, a missing feedback loop for batch operations, and the absence of any progressive-disclosure file structure.

Suggestions

Add a validate-and-retry feedback loop to the Parallel Operations workflow (check per-action results, surface failures, retry failed actions) since failures do not roll back.

Remove the duplicate 'Known Pitfalls' section and the generic 'When to Use'/'Limitations' boilerplate, keeping pitfalls inline with their workflows only.

Extract the Quick Reference table into a references file (e.g. references/tool-reference.md) and point to it from the overview to establish one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

Most content is concrete and useful, but pitfalls are duplicated per-workflow and again under 'Known Pitfalls', and the generic 'When to Use'/'Limitations' sections are boilerplate padding that could be trimmed.

2 / 3

Actionability

Provides exact tool slugs, ordered sequences with prerequisite/optional markers, key parameters, and a copy-ready Quick Reference table mapping each task to its tool and params — the executable form for this MCP domain.

3 / 3

Workflow Clarity

Workflows are clearly sequenced with validation in Setup, but the batch/destructive Parallel Operations section warns that failures don't roll back yet provides no validate-retry feedback loop, capping this at 2.

2 / 3

Progressive Disclosure

Sections are well organized, but all content lives inline in a single ~170-line file with no bundle files or one-level-deep references, and the large Quick Reference could appropriately be split out.

2 / 3

Total

9

/

12

Passed

Description

67%

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 is specific and clearly distinguishable, naming concrete Asana domains and the integration mechanism. Its main weakness is the absence of an explicit 'when to use' trigger clause and limited natural-term variation.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., when the user asks to create, search, or organize Asana tasks/projects).

Broaden trigger-term coverage with natural user phrasings such as 'assign tasks', 'task list', 'due dates', or 'move tasks to sections'.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities and resource domains ('tasks, projects, sections, teams, workspaces') plus an explicit operational instruction ('Always search tools first for current schemas'), matching the multiple-specific-actions anchor.

3 / 3

Completeness

The 'what' is clear (automate Asana via Rube MCP across listed domains), but there is no explicit 'Use when...' trigger clause — only a procedural note — which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

It includes natural terms like 'Asana tasks', 'projects', and 'workspaces', but lacks common user phrasings such as 'task list', 'assign tasks', or 'due dates', so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply scoped to 'Asana via Rube MCP (Composio)' with distinct, unlikely-to-collide triggers, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.