asana-task-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill asana-task-creatorAsana Task Creator - Auto-activating skill for Enterprise Workflows. Triggers on: asana task creator, asana task creator Part of the Enterprise Workflows skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others, and the redundant trigger terms suggest a template was not properly filled out.
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 'create asana task', 'add to asana', 'new task in asana project', 'asana todo'
Remove the redundant trigger term and add varied natural language phrases users would actually say when needing this functionality
| 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. The 'Triggers on' section just repeats the skill name rather than describing user scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('asana task creator' listed twice) and overly specific to the skill name itself. Missing natural user phrases like 'create asana task', 'add task to asana', 'new asana item', or 'asana todo'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Asana' provides some distinctiveness from generic task management skills, but 'Enterprise Workflows' is vague and could overlap with other enterprise integration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is an empty template that provides zero actionable guidance for creating Asana tasks. It contains only generic placeholder text that could apply to any skill, with no specific API calls, authentication details, request formats, or examples. The content fails to teach Claude anything it doesn't already know.
Suggestions
Add executable code examples showing Asana API calls for task creation, including authentication headers and request body format
Include a clear workflow: authenticate -> create task -> validate response -> handle errors
Provide specific field mappings and required vs optional parameters for Asana task creation
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with concrete implementation details
| 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 content describes what the skill supposedly does but never shows how to actually create an Asana task. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There's no sequence of actions, no API endpoints, no authentication steps, and no validation checkpoints for creating Asana tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, API guides, or examples that would help with actual implementation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.