Name: api2cart
Rating: 53.6 (1 reviews)
Author: membranedev

api2cart

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

Quality

60%

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

Quality

Content

66%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 content is actionable with executable commands and a clear install-to-run workflow including polling and state checks. It is slightly padded with background explanation and a duplicated command, but well structured.

Suggestions

Trim the opening overview paragraph explaining what API2Cart is and who uses it; assume Claude knows this and lead with what the skill does.

Remove the duplicated 'membrane action list' command in 'Popular actions' since it is already shown in 'Searching for actions'.

Add a brief validation/check step after 'Running actions', e.g. how to inspect the 'output' field or handle errors, to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining what API2Cart is and who uses it ('used by developers and businesses who need to integrate...') is background Claude does not need, and the repeated 'membrane action list' command in 'Popular actions' duplicates the earlier 'Searching for actions' section.	3 / 5
Actionability	Provides concrete, executable shell commands for install, auth, connection, action search/run, and proxy requests with flags table, covering the common cases; minor gaps are placeholders like CONNECTION_ID and actionId that the user must fill in.	4 / 5
Workflow Clarity	Clear sequence from install -> auth -> connection ensure -> poll until READY -> search actions -> run, with explicit state-based branching and polling checkpoints; lacks an explicit validation/verify step after running actions but the operations are non-destructive reads by default.	4 / 5
Progressive Disclosure	Well-organized with clear section headers (Overview, Working with API2Cart, Popular actions, Best practices) and no bundle files or nested references; the body is a self-contained single-level overview appropriate for this skill, with only minor inlining of the proxy flag table that is reasonable here.	4 / 5
	Total	15 / 20 Passed

Description

53%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 and includes an explicit 'Use when' trigger, but its action language is generic rather than naming concrete API2Cart capabilities. It is clearly distinguishable due to the platform-specific trigger.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions such as 'list products, fetch orders, sync customers, and manage categories across Shopify, Magento, and WooCommerce'.

Add natural trigger terms users would actually say, e.g. 'Use when the user wants to query or sync e-commerce store data via API2Cart'.

Mention the supported shopping platforms in the description to improve trigger coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (API2Cart) but the actions are generic ('Manage data, records, and automate workflows') with no concrete API2Cart-specific operations like 'list products' or 'fetch orders' stated.	2 / 5
Completeness	Provides a clear 'what' (manage data, records, automate workflows) and an explicit 'Use when...' clause for the 'when', though the 'what' is somewhat generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the natural keyword 'API2Cart' and the phrase 'interact with API2Cart data', but lacks common synonyms or variations users might say such as shopping-platform names (Shopify, Magento) or 'e-commerce API'.	3 / 5
Distinctiveness Conflict Risk	The API2Cart-specific trigger makes it mostly distinct from other skills, though 'Manage data, records, and automate workflows' is broad enough to create minor overlap with generic data-management skills.	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/api2cart/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.