Name: asana
Rating: 53.6 (1 reviews)
Author: membranedev

asana

Asana integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Asana data.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/asana/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is actionable and the connection workflow is well-sequenced with explicit state-based checkpoints, but it carries some introductory padding Claude already knows and inlines the full action catalog that would read better as a separate reference. No bundle files exist, so progressive disclosure rests on the single-file structure alone.

Suggestions

Remove the opening "Asana is a project management tool that helps teams organize..." paragraph; Claude already knows what Asana is.

Move the 20-row Popular actions table into a references/actions.md file and link to it from the body, improving progressive disclosure and token efficiency.

Provide one end-to-end worked example (obtain CONNECTION_ID -> action list -> action run -> read output) so the full workflow reads as a single validated sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a compact actions table, but it includes explanatory padding Claude does not need ("Asana is a project management tool that helps teams organize..." and verbose proxy/auth prose), fitting the score-3 anchor of mostly-efficient with some unnecessary explanation rather than the lean bar of 4.	3 / 5
Actionability	It provides concrete, executable commands (install, login, connection ensure/get with --wait, action list/run, request flags) plus a real actions table with keys, which is mostly copy-paste ready with only minor gaps (e.g. the CONNECTION_ID placeholder is never shown being obtained end-to-end), placing it at 4 rather than the fully-covered bar of 5.	4 / 5
Workflow Clarity	The connect flow is well sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, giving clear checkpoints; it stays at 4 rather than 5 because the broader task flow (search action -> run -> read output) is implied rather than presented as a single validated end-to-end sequence.	4 / 5
Progressive Disclosure	There are no bundle files (references/scripts/assets absent) and the body is a single flat SKILL.md holding the full actions table and all reference inline with section headers, fitting the score-3 anchor of some structure with content that could be split out rather than a clearly-tiered overview with one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

60%Weight 40%Scale 1-5

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 clearly identifies Asana and provides an explicit Use-when trigger, but the capability phrasing leans generic ("manage...data, records, and workflows") and lacks the natural task-level vocabulary users actually say. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Asana actions, e.g. "Create, update, and list tasks, projects, sections, and workspaces; manage tickets and attachments."

Add natural trigger terms users say, such as "tasks", "projects", "to-dos", "Asana GIDs", or "Asana workspace".

Tighten the when-clause with concrete triggers: "Use when the user wants to create or track tasks, projects, or tickets in Asana."

Dimension	Reasoning	Score
Specificity	"Manage project management and ticketing data, records, and workflows" names the domain plus a couple of concrete-sounding actions, but the verbs (manage, data, records, workflows) are generic and not comprehensive, matching the score-3 anchor of domain with 1-2 concrete actions rather than the several-specific-actions bar of 4.	3 / 5
Completeness	It answers "what" (manage Asana data/records/workflows) and "when" ("Use when the user wants to interact with Asana data"), placing it above the missing-when ceiling of 3; the when-clause is present but generic, so it does not reach the concrete-trigger-phrases level of 5.	4 / 5
Trigger Term Quality	It surfaces "Asana", "project management", "ticketing", and "data", but misses the natural synonyms users say (tasks, projects, GIDs, to-dos, workspaces) and any file/identifier extensions, fitting the score-3 anchor of relevant keywords with missing common variations rather than the fuller coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The Asana name plus the project-management/ticketing framing carve a clear niche with minimal overlap against other skills, mostly distinct with only minor overlap risk versus a generic project-management skill, fitting the 4 anchor rather than the fully-tailored-trigger 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/asana/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.