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
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 extremely weak, consisting essentially of a skill name repeated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms users would say, and no explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from any other Asana-related skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates tasks in Asana with titles, descriptions, assignees, due dates, and project assignments.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an Asana task, add a to-do in Asana, make a ticket, or assign work in Asana.'
Remove the duplicated trigger term ('asana task creator' listed twice) and replace with varied natural language phrases users would actually say, such as 'new Asana task', 'add task to Asana', 'Asana ticket'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Asana Task Creator') but does not describe any concrete actions like creating tasks, assigning them, setting due dates, or adding to projects. It is essentially a name repeated with no capability details. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no explicit 'Use when...' clause or meaningful trigger guidance beyond the repeated skill name). | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'asana task creator' repeated twice. There are no natural user keywords like 'create a task in Asana', 'add Asana ticket', 'assign task', 'project management', or 'to-do' that users would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Asana' provides some domain specificity that distinguishes it from generic task or project management skills, but the lack of detail about what specifically it does with Asana could cause overlap with other Asana-related 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 hollow template with no actual content. It contains only generic placeholder text that describes what a skill would do without providing any actionable information about creating Asana tasks. There are no API examples, no authentication guidance, no task creation payloads, and no workflow steps whatsoever.
Suggestions
Add concrete, executable code examples showing Asana API calls for task creation (e.g., using the Asana REST API with curl or Python requests, including authentication headers and JSON payloads).
Define a clear multi-step workflow: authenticate → specify project/workspace → create task with required fields → validate response → handle errors, with explicit validation checkpoints.
Remove all generic filler sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like API endpoint references, required fields, and example request/response pairs.
Add references to Asana API documentation and link to separate files for advanced patterns like batch task creation, custom fields, or subtask hierarchies.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual guidance, commands, or code. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No API calls, no code examples, no specific Asana endpoints, no configuration snippets. The content only describes what it would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for creating Asana tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed materials, no links to API documentation, and no structured navigation to deeper content. | 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
4dee593
- 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.