asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
55
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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 integration) which makes it distinctive, but it lacks concrete action verbs describing what operations are supported and entirely omits a 'Use when...' clause. The listing of entity types (tasks, projects, etc.) is helpful but insufficient without specifying what can be done with them.
Suggestions
Add a 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks to create, update, assign, or query Asana tasks, projects, or workspaces.'
Replace the vague 'Automate Asana tasks' with specific actions like 'Create, update, assign, and search Asana tasks; manage projects and sections; list teams and workspaces.'
Move the implementation detail ('Always search tools first for current schemas') out of the description or rephrase it as internal guidance, since it doesn't help with skill selection.
| 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 for Claude, not a trigger condition. 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)' creates a very clear niche. It's unlikely to conflict with other skills since it targets a specific third-party tool integration. | 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 clear tool names, parameters, and workflow sequences. Its main weaknesses are the lack of concrete executable examples (no actual tool call with sample parameters/responses), missing validation checkpoints in workflows, and some redundancy between the workflow sections and the quick reference table. The content would benefit from being more concise and including at least one end-to-end example with real parameter values.
Suggestions
Add at least one concrete end-to-end example showing actual tool invocations with sample parameter values and expected response structures (e.g., creating a task in a specific project).
Add validation checkpoints to workflows—e.g., 'Verify workspace GID was returned before proceeding' or 'Confirm task creation by checking the returned task GID'.
Remove the redundant 'Known Pitfalls' section since GID format and workspace scoping are already covered in individual workflow pitfalls, or consolidate all pitfalls into one section and remove them from individual workflows.
Consider removing the quick reference table or the detailed workflow tool sequences to reduce redundancy—one or the other is sufficient given the instruction to always search tools first for current schemas.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes some redundancy—the quick reference table largely duplicates information already covered in the workflow sections. The 'Known Pitfalls' section repeats GID format and workspace scoping points already mentioned in individual workflow pitfalls. The boilerplate 'When to Use' and 'Limitations' sections add little value. | 2 / 3 |
Actionability | Tool names and key parameters are clearly listed, which is helpful. However, there are no executable code examples or concrete tool invocation examples with actual parameter values. The 'Common Patterns' section uses pseudocode-style numbered lists rather than showing actual tool calls with sample inputs/outputs. | 2 / 3 |
Workflow Clarity | Workflows are sequenced with numbered steps and labeled as prerequisite/optional, which is good. However, there are no validation checkpoints—no steps to verify that a workspace was found, that a task was created successfully, or error handling guidance. The parallel operations section notes that failed requests don't roll back but doesn't provide a verification/recovery workflow. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and a useful quick reference table. However, it's a fairly long monolithic document (~150+ lines) that could benefit from splitting detailed workflow sections into separate files. The instruction to 'always call RUBE_SEARCH_TOOLS first to get current tool schemas' somewhat undermines the need for the extensive inline reference table. | 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
- boisenoise/skills-collections
- Commit
431bfad
- 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.