Name: api-to-every-ecommerce-cart-and-marketplace
Rating: 56.8 (1 reviews)
Author: membranedev

api-to-every-ecommerce-cart-and-marketplace

API to every Ecommerce Cart and Marketplace integration. Manage data, records, and automate workflows. Use when the user wants to interact with API to every Ecommerce Cart and Marketplace 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/api-to-every-ecommerce-cart-and-marketplace/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 strongly actionable, well-sequenced CLI guide with real feedback loops for connection setup. It loses points mainly to redundancy and light conceptual padding.

Suggestions

Cut the boilerplate intro sentence explaining what a unified ecommerce API is and collapse the empty Overview bullet list.

Differentiate the 'Popular actions' section from 'Searching for actions' by showing example intents/results instead of restating the same list command.

Add a brief validation/confirmation step before running mutating actions (e.g., inspect inputSchema and confirm before action run).

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but the intro explains concepts Claude can infer, the Overview section is near-empty, and the 'Popular actions' section repeats the discovery command from the prior section.	3 / 5
Actionability	Provides concrete, executable membrane commands with flags and JSON examples across install, auth, connection, action list/run, and proxy, with only minor gaps (no sample action run output).	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with explicit connection-state checkpoints and polling feedback loops; the action-run half lacks an explicit verification step.	4 / 5
Progressive Disclosure	Single well-sectioned SKILL.md with no nested or broken references and a single external docs link; content is appropriately organized though some API reference detail is inlined.	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 is third person, includes an explicit 'Use when' trigger, and targets a distinct niche. Its weakness is generic action language and limited trigger-term variation.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete capabilities (e.g., list orders, sync products, fetch customers) to lift specificity.

Add natural trigger synonyms users would say (e.g., 'online store', 'shop platform', 'marketplace orders') and avoid repeating the verbose product name twice.

Tighten the 'Use when' clause to name concrete scenarios (e.g., pulling orders or syncing inventory across ecommerce platforms).

Dimension	Reasoning	Score
Specificity	Names the domain (ecommerce cart/marketplace) and offers 'Manage data, records, and automate workflows', but the actions are generic rather than the concrete, comprehensive set the top anchor requires.	3 / 5
Completeness	States both a 'what' (integration / manage data and workflows) and an explicit 'when' clause ('Use when the user wants to interact with...'), though the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes relevant terms like 'Ecommerce Cart and Marketplace' and 'data', but lacks common variations, synonyms, or concrete platform/file triggers users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The 'API to every Ecommerce Cart and Marketplace' framing carves out a fairly distinct niche with low overlap risk, though the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap potential.	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/api-to-every-ecommerce-cart-and-marketplace/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.