asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 specific tooling) but lacks concrete action verbs and explicit trigger guidance. It tells Claude what entities it can work with but not what operations it performs or when to select this skill over others.
Suggestions
Add explicit trigger guidance: 'Use when the user mentions Asana, project management tasks, or wants to automate work tracking.'
Replace generic 'automate' with specific actions: 'Create, update, assign, and organize Asana tasks; manage projects and sections; query workspaces and teams.'
Add natural user terms like 'to-do list', 'assign task', 'due date', 'project board' that users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Asana) and lists entity types (tasks, projects, sections, teams, workspaces) but doesn't describe concrete actions beyond generic 'automate'. Missing specific verbs like 'create', 'update', 'assign', 'move'. | 2 / 3 |
Completeness | Describes what (automate Asana tasks) but has no explicit 'Use when...' clause or trigger guidance. The instruction to 'search tools first' is operational guidance for Claude, not selection criteria. | 1 / 3 |
Trigger Term Quality | Includes 'Asana', 'tasks', 'projects' which users would naturally say, but missing common variations like 'to-do', 'assign', 'due date', 'project management'. The technical term 'Rube MCP (Composio)' is jargon users wouldn't use. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Asana specifically via Rube MCP/Composio integration. Unlikely to conflict with other skills due to the specific platform and integration method mentioned. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
57%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 reference for Asana automation via Rube MCP with good organization and clear workflow structures. However, it lacks executable examples (actual MCP call syntax with real parameters) and validation checkpoints for confirming operations succeeded. The content is somewhat verbose with the quick reference table duplicating workflow information.
Suggestions
Add concrete MCP call examples with actual syntax, e.g., showing a complete RUBE_SEARCH_TOOLS call and its response structure
Include validation steps in workflows, such as 'Verify task creation by checking the returned task GID' or 'Confirm section assignment by calling ASANA_GET_TASK'
Remove the quick reference table or the detailed workflow sections to eliminate redundancy - one comprehensive format is sufficient
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the quick reference table duplicates information from the workflow sections, and some explanations (like GID format) could be more terse. The setup section is appropriately brief. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The 'ID Resolution' patterns use pseudocode rather than actual MCP call syntax. Key parameters are listed but without concrete example values or complete call structures. | 2 / 3 |
Workflow Clarity | Workflows are sequenced with numbered steps and prerequisites marked, but lack validation checkpoints. No explicit verification steps after operations (e.g., confirming task creation succeeded). The [Optional] markers on most steps reduce clarity about actual required sequences. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference). External toolkit docs are linked appropriately. Content is appropriately structured for a single SKILL.md file without needing additional files. | 3 / 3 |
Total | 9 / 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 | |
- 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.