asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
64
45%
Does it follow best practices?
Impact
100%
1.88xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/asana-automation/SKILL.mdQuality
Discovery
40%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 clear niche (Asana automation via a specific MCP tool) which makes it distinctive, but it lacks concrete action verbs describing what operations are supported and entirely omits a 'Use when...' clause. The internal implementation note ('Always search tools first for current schemas') wastes space that could be used for trigger terms or explicit usage guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, update, assign, or query Asana tasks, projects, or workspaces.'
Replace the vague 'Automate' with specific actions like 'Create, update, assign, and query Asana tasks; manage projects, sections, teams, and workspaces.'
Move the implementation detail ('Always search tools first for current schemas') into the skill body rather than the description, and use that space for natural trigger terms like 'project management', 'assign task', 'due date'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Asana) and lists entity types (tasks, projects, sections, teams, workspaces), but doesn't describe concrete actions beyond the vague 'automate'. What specific operations—create, update, move, assign, query? | 2 / 3 |
Completeness | Provides a partial 'what' (automate Asana tasks) but has no explicit 'when' clause—no 'Use when...' or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail, not a usage trigger. Per rubric, missing 'Use when...' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes 'Asana', 'tasks', 'projects', 'sections', 'teams', 'workspaces' which are relevant keywords, but misses natural user phrases like 'assign task', 'create project', 'move to section', 'due date', or 'project management'. 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Asana' and 'Rube MCP (Composio)' makes this clearly distinguishable from other skills. It's unlikely to conflict with other project management or task automation skills due to the specific platform reference. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive catalog of Asana operations via Rube MCP with good structural organization and clear tool naming. Its main weaknesses are the lack of executable examples (no actual JSON payloads or tool call formats), missing validation/error-handling steps in workflows, and redundant content between the workflow sections and the quick reference table. The content reads more like API documentation than an actionable skill guide.
Suggestions
Add at least one fully executable tool call example showing exact parameter format/JSON payload (e.g., a complete ASANA_CREATE_A_TASK invocation with all required fields filled in).
Add validation checkpoints to workflows — e.g., after creating a task, verify the returned GID; after adding to a section, confirm the task appears in section listing.
Remove the 'Known Pitfalls' section since its content is already covered in individual workflow pitfalls, or consolidate all pitfalls into one section and remove them from individual workflows.
Consider moving the quick reference table to a separate REFERENCE.md file and linking to it, reducing the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has redundancy — the quick reference table largely duplicates information already covered in the core workflows sections. The 'Known Pitfalls' section repeats GID format and workspace scoping points already mentioned in individual workflow pitfalls. Some trimming would improve token efficiency. | 2 / 3 |
Actionability | Tool names and parameter lists are concrete and specific, but the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual executable examples. There are no real code snippets or copy-paste-ready tool invocations showing exact parameter formats/JSON payloads. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional, which is helpful. However, there are no validation checkpoints — no steps to verify task creation succeeded, no error handling guidance, and the parallel operations section explicitly notes failed requests don't roll back but provides no recovery strategy. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's quite long and monolithic. The quick reference table, detailed workflow sequences, and common patterns could benefit from being split into separate reference files. The single external link to Composio docs is appropriate but more could be offloaded. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Lingjie-chen/MT5
- Commit
3069d33
- 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.