Name: avaza
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

avaza

Avaza integration. Manage Organizations. Use when the user wants to interact with Avaza data.

Quality

66%

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/avaza/SKILL.md

Quality

Content

75%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 body is highly actionable with executable CLI commands and a well-validated connection workflow, but it carries avoidable padding (a product overview paragraph and a descriptions-blank actions table) and offers no progressive disclosure into reference files. Trimming the filler and splitting the action catalog would push it toward top scores.

Suggestions

Remove the marketing-style Avaza overview paragraph and replace the 'No description' actions table with either real one-line descriptions or a pointer to a separate ACTIONS reference file.

Add a validation/verification checkpoint before running destructive create actions (e.g. confirm parameters and inspect the returned output before treating a create as final).

Move the bulk action catalog into a one-level-deep reference file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but the opening Avaza product-marketing paragraph and the 20-row 'Popular actions' table whose entries all read 'No description' are unnecessary padding, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list, action run, request proxy) with clear flag documentation, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection lifecycle is sequenced with explicit state checkpoints and a poll-after-action feedback loop, but the action-running section lacks pre-execution validation for destructive create operations, leaving a minor validation gap that caps it at 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well organized into clearly labeled sections with no nested references, but the inlined 'Popular actions' reference table is content that could live in a separate file and the body exceeds the under-50-lines simple-skill exception, so it sits at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

57%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 successfully pairs a what and a when around a distinct branded product, but the capability list is thin and generic and the trigger guidance lacks concrete synonyms. Tightening the action verbs and adding concrete trigger phrases would lift it toward the top anchors.

Suggestions

Replace the generic "Manage Organizations" with several concrete actions the skill performs (e.g. list/create projects, tasks, timesheets, invoices, expenses) to raise specificity.

Expand the 'Use when' clause with concrete natural trigger phrases (e.g. 'when the user mentions Avaza projects, timesheets, invoices, or expenses') to improve trigger-term quality and completeness.

Add domain-entity synonyms (projects, tasks, time tracking, invoicing) so the description is less reliant on the bare brand name alone.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Avaza integration") and one minimal/generic action ("Manage Organizations"), matching the score-2 anchor of naming the domain but with minimal or generic actions rather than the multiple concrete actions needed for a 3.	2 / 5
Completeness	It states both what ("Avaza integration. Manage Organizations.") and when ("Use when the user wants to interact with Avaza data."), but the when clause is generic rather than listing concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	It surfaces the natural brand keyword "Avaza" plus "Avaza data" and "Organizations", but offers limited synonym/variation coverage, fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named product "Avaza" gives it a clear, mostly-distinct niche with minimal conflict risk, but the generic "Manage Organizations" phrasing leaves minor overlap risk with other CRM/project-management integrations, placing it at 4 instead of 5.	4 / 5
	Total	13 / 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/avaza/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.