asana-task-creator
Asana Task Creator - Auto-activating skill for Enterprise Workflows. Triggers on: asana task creator, asana task creator Part of the Enterprise Workflows skill category.
32
Quality
3%
Does it follow best practices?
Impact
77%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/asana-task-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely underdeveloped, essentially just restating the skill name with boilerplate category information. It lacks any explanation of capabilities, concrete actions, or guidance on when Claude should select this skill. The duplicated trigger term suggests a copy-paste error.
Suggestions
Add specific actions the skill performs, e.g., 'Creates tasks in Asana with titles, descriptions, due dates, assignees, and project assignments'
Include a 'Use when...' clause with natural trigger phrases like 'Use when the user wants to create an Asana task, add items to Asana, or mentions creating tickets/to-dos in Asana'
Add varied trigger terms users would naturally say: 'asana', 'create task', 'new ticket', 'add to-do', 'asana project'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Asana Task Creator' without describing any concrete actions. It doesn't explain what creating a task involves (e.g., setting due dates, assignees, projects, subtasks). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'asana task creator, asana task creator' (duplicated). Missing natural user phrases like 'create asana task', 'add task to asana', 'new asana ticket', or 'asana to-do'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Asana' provides some specificity that distinguishes it from generic task creators, but 'Enterprise Workflows' is vague and could overlap with other enterprise integration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual instructional content. It describes what the skill would do in abstract terms but provides zero actionable guidance for creating Asana tasks—no API endpoints, no code examples, no authentication steps, no task creation parameters. Claude would learn nothing from this skill that it doesn't already know.
Suggestions
Add concrete code examples showing Asana API calls for task creation, including authentication, required fields, and response handling
Include a clear workflow with steps: authenticate -> create task -> validate response -> handle errors
Remove all generic boilerplate ('provides step-by-step guidance', 'follows industry best practices') and replace with actual Asana-specific instructions
Add specific examples of task payloads with required and optional fields (name, assignee, due_date, projects, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Asana task creation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, API calls, commands, or specific instructions are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There is no sequence, no validation checkpoints, and no actual process for creating Asana tasks. The content only describes triggers and capabilities without any operational detail. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed documentation, no links to examples, and no organization that would help Claude navigate to actual implementation details. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.