Name: shopwaive
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

shopwaive

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

Quality

65%

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

Quality

Content

67%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 a well-structured, actionable CLI integration guide with a clear connection-state feedback loop, but carries some marketing filler and loose step numbering that prevent top marks.

Suggestions

Trim the introductory marketing prose and filler phrases ('burn less tokens', 'focus on integration logic rather than auth plumbing') to tighten conciseness.

Fix the step numbering: add a '1a' label and a clearly labeled 'Step 2' section so the cross-references resolve, improving workflow clarity.

Add one worked end-to-end example (e.g. a concrete action run with a real input JSON and the expected output field) to push actionability toward fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padded marketing prose ('helps businesses create online stores... easy-to-use online sales solution') and filler ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens'); fits anchor 3 rather than 4 because several sentences could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands covering install, login (incl. headless), connect, poll, search, run, and proxy with a flags table; fits anchor 4's 'mostly executable with minor gaps' (placeholders like <agentType>/CONNECTION_ID and no worked end-to-end example with real params and output) rather than 5.	4 / 5
Workflow Clarity	The connection-readiness flow has an explicit feedback loop (poll state, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll), fitting anchor 4; not 5 because step numbering is loose ('#### 1b' with no 1a, references 'Step 2' with no labeled Step 2).	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested/deep references and content appropriately placed in a single file, fitting anchor 4; not 5 because no separate reference file exists for exhaustive Shopwaive action documentation and the skill exceeds the simple under-50-line case.	4 / 5
	Total	15 / 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 correctly includes an explicit 'Use when' trigger and names a distinct platform, but the capability list is thin (one concrete action) and trigger terms lack the natural variations users would actually say.

Suggestions

Expand the 'what' with concrete capabilities tied to Shopwaive entities, e.g. 'Manage organizations, products, orders, and customers' to lift specificity.

Add natural trigger phrases a user would say, such as 'Use when the user wants to query Shopwaive orders, products, or customer data' to improve trigger term quality.

Replace the generic 'interact with Shopwaive data' with specific object-level triggers to sharpen distinctiveness and completeness.

Dimension	Reasoning	Score
Specificity	Names the domain ('Shopwaive integration') plus one concrete action ('Manage Organizations') and a generic 'interact with Shopwaive data', matching anchor 3's domain + 1-2 concrete actions without comprehensive coverage; not 2 because a concrete action is present, not 4 because coverage is thin and largely generic.	3 / 5
Completeness	Both a 'what' ('Shopwaive integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Shopwaive data.') are present, matching anchor 4; not 5 because the trigger phrase is generic rather than concrete, not 3 because the Use when clause is explicit (no cap applies).	4 / 5
Trigger Term Quality	The only natural keyword is 'Shopwaive' (and 'Shopwaive data'), which is specific but lacks common variations a user would say (orders, products, customers, store); fits anchor 3's 'some relevant keywords but missing common variations' rather than 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	Naming a specific platform ('Shopwaive') gives a clear niche with minor overlap risk against other e-commerce skills, fitting anchor 4; not 5 because the description is thin and the trigger ('interact with Shopwaive data') is not sharply differentiated.	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/shopwaive/SKILL.md
Commit: f484c82

Reviewed: 4 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.