Name: ecwid
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ecwid

Ecwid integration. Manage Stores. Use when the user wants to interact with Ecwid data.

Quality

57%

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

Quality

Content

57%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 delivers strong executable guidance for connecting to and calling Ecwid via Membrane, with a well-structured connection workflow, but it is padded with background prose and lacks validation safeguards and reference splitting for destructive operations.

Suggestions

Trim background explanation (the Ecwid platform intro and auth-philosophy prose) to assume Claude's competence and tighten token efficiency.

Add an explicit validation checkpoint before destructive actions, e.g. verify the target entity exists and confirm with the user before running delete-* actions.

Move the full popular-actions table into a referenced file (e.g. ACTIONS.md) and keep only the most common examples inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes unnecessary explanation Claude already knows ("Ecwid is an e-commerce platform that allows users to easily create..." and "so you can focus on the integration logic rather than auth plumbing"), matching the mostly-efficient-but-could-be-tightened anchor; not a 4 because several padded prose passages remain.	3 / 5
Actionability	Concrete executable commands appear throughout (install, login, connection ensure/get, action list/run, request) plus a popular-actions table and proxy-flags table, fitting the mostly-executable anchor with minor gaps such as unresolved CONNECTION_ID placeholders; not a 5 because inputSchema/outputSchema usage and parameter passing are not fully exemplified for the common cases.	4 / 5
Workflow Clarity	The connection setup has a clear sequence with explicit state checkpoints and a poll-after-action feedback loop, but running destructive actions (delete-product, delete-order, etc.) includes no validation/verification step, so the destructive-operation cap applies and workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The file is well-sectioned with clear headers and links to official docs, but there are no bundle files and the full action reference is inlined rather than split into a one-level-deep reference, fitting the some-structure-but-could-be-better-organized anchor; not a 4 because reference-worthy content stays inline.	3 / 5
	Total	13 / 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 correctly pairs a what-statement with a Use-when clause and leverages the distinct Ecwid brand, but it is light on concrete capabilities and natural trigger variations.

Suggestions

Replace the generic "Manage Stores" with 2-4 concrete actions, e.g. "Manage Ecwid products, orders, customers, and categories."

Expand the trigger clause with natural phrases users actually say, e.g. "Use when the user wants to query or update Ecwid store data, products, orders, or customers."

Add file-format or entity keywords (products, orders, customers, categories) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Stores" names the Ecwid domain but offers only a single generic action with no concrete capabilities enumerated, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	Both "what" ("Ecwid integration. Manage Stores.") and "when" ("Use when the user wants to interact with Ecwid data") are present, but the trigger is generic rather than concrete, matching the anchor where both exist yet "when" could be more specific; not a 5 because trigger phrases are not concrete.	4 / 5
Trigger Term Quality	"Ecwid" is a relevant natural keyword and "interact with Ecwid data" is a usable phrase, but common variations or synonyms are missing, fitting the anchor where some keywords exist but variations are absent.	3 / 5
Distinctiveness Conflict Risk	"Ecwid integration" establishes a clear platform-specific niche with distinct triggers and minimal conflict risk, though "Manage Stores" could overlap with other e-commerce skills, fitting the mostly-distinct anchor.	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/ecwid/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.