Name: avada-commerce
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

avada-commerce

AVADA Commerce integration. Manage data, records, and automate workflows. Use when the user wants to interact with AVADA Commerce data.

Quality

61%

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/avada-commerce/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 body is highly actionable with concrete CLI commands and a sensible flow, but it is padded with introductory fluff and has a broken step-numbering scheme plus no validation before destructive operations. Tightening prose and fixing the workflow anchors would materially improve it.

Suggestions

Remove the marketing-style overview paragraph and the 'so you can focus on the integration logic' aside; assume Claude knows what an e-commerce platform is.

Fix the workflow numbering: define Step 1 and Step 2 explicitly (or drop the 'Step 2' / '1b' references) so the 'skip to Step 2' instruction resolves.

Add an explicit validation checkpoint before running mutating actions or proxy POST/PUT/DELETE calls (e.g., confirm the connection state is READY and re-read the inputSchema before executing), which would also lift workflow_clarity above the destructive-operations cap.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph explaining what AVADA Commerce is ('an e-commerce platform designed for businesses...') and lines like 'so you can focus on the integration logic rather than auth plumbing' add explanation Claude does not need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action run) plus a flags table, covering common cases copy-paste ready with only minor gaps such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	A rough sequence exists (install, auth, connect, poll for state, search, run) with state-based feedback, but 'skip to Step 2' references a Step 2 that is never defined and '1b' has no '1a', and there are no validation checkpoints before destructive action/proxy calls (POST/PUT/DELETE on commerce data), which caps this at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (install, auth, connecting, actions, proxy, best practices) with no bundle files to reference; structure is good though the state-machine and proxy-flag detail could arguably live in separate files, keeping it just below 5.	4 / 5
	Total	14 / 20 Passed

Description

62%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 is clear and distinct, explicitly pairing a 'what' with a 'when' trigger, but its action list and trigger vocabulary are generic. Sharpening the concrete capabilities and adding natural synonyms would lift it.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete capabilities, e.g. 'Create and update orders, manage customers and products, and trigger marketing automations'.

Expand the trigger clause with natural phrases users say, e.g. 'Use when the user wants to manage AVADA Commerce orders, customers, products, or automate marketing workflows'.

Drop filler like 'integration' as the lead and lead with the most distinctive action to sharpen first-impression specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('AVADA Commerce integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	It explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with AVADA Commerce data'), but the 'when' is somewhat generic rather than packed with concrete triggers, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The trigger phrase 'Use when the user wants to interact with AVADA Commerce data' supplies the core product name but lacks synonyms, variants, or related natural terms, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to a named platform ('AVADA Commerce') gives it a clear niche with low conflict risk, though the generic action verbs keep it just short of the fully distinct anchor.	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/avada-commerce/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.