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.

74

1.92x
Quality

63%

Does it follow best practices?

Impact

96%

1.92x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/asana-automation/SKILL.md
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 automation with clear tool sequences and parameter guidance. Its main weaknesses are redundant pitfalls/filler text, missing validation for batch operations, and an opportunity to offload the bulk reference table into a separate file.

Suggestions

Add an explicit validation/verification checkpoint to the Parallel Operations workflow (e.g., check each action's response status and summarize failures before reporting success), since failed sub-requests do not roll back.

Remove the redundant 'Known Pitfalls' section (its GID-format and workspace-scoping points already appear in per-workflow Pitfalls) and delete the filler 'When to Use' line.

Consider moving the Quick Reference table into a references/ file (e.g., REFERENCE.md) and linking to it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material, but the 'Known Pitfalls' section repeats GID-format and workspace-scoping pitfalls already stated per-workflow, and the trailing 'When to Use' line is pure filler, fitting anchor 3 (some unnecessary content that could be tightened).

3 / 5

Actionability

Concrete tool slugs, ordered tool sequences, and specific key parameters (workspace GID, due_on as YYYY-MM-DD) give mostly executable guidance; the minor gap is the absence of example request payloads, keeping it just below anchor 5.

4 / 5

Workflow Clarity

Workflows are clearly sequenced and the setup has an ACTIVE-connection checkpoint, but the batch Parallel Operations workflow has no validation/verification step, so the destructive/batch cap at 3 applies even though the simple-skill exception would otherwise allow higher.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and no bundle files; the Quick Reference table and detailed workflow lists could arguably be split into a reference file, which keeps it at anchor 4 rather than 5.

4 / 5

Total

14

/

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.

The description clearly identifies a distinct Asana-automation niche with natural trigger terms, but it relies on a single vague action verb and omits any explicit 'when to use' guidance. Adding concrete verbs and a Use-when clause would lift completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when the user wants to create, search, or organize Asana tasks, projects, or teams').

Replace the generic verb 'Automate' with several concrete actions (create, search, list, assign, organize) to improve specificity.

Include common synonyms or natural variations users might say (e.g., 'to-do', 'assignees', 'due dates') for fuller trigger coverage.

DimensionReasoningScore

Specificity

Names the Asana domain and lists concrete objects (tasks, projects, sections, teams, workspaces) but the only action verb is the generic 'Automate', matching anchor 3 (domain + 1-2 actions, not comprehensive) rather than 4 which requires several specific actions.

3 / 5

Completeness

It clearly answers 'what' (Automate Asana tasks via Rube MCP) but lacks any 'Use when...' or equivalent explicit trigger guidance, so per the cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Natural Asana terms a user would say (tasks, projects, sections, teams, workspaces) are present, but synonyms and common variations are missing, fitting anchor 4 (good coverage, a few natural terms missing) rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Asana automation via Rube MCP (Composio) is a clear niche with distinct triggers and minimal overlap risk, matching anchor 5; it would not fire for unrelated skills.

5 / 5

Total

15

/

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.

Validation — 15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.