Name: cloudcart
Rating: 60 (1 reviews)
Author: membranedev

cloudcart

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

Quality

70%

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

Quality

Content

82%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 strong, executable guide to the Membrane CLI integration with concrete commands and a well-validated connection workflow. Its main weaknesses are minor padding in the intro and the absence of verification steps for data-mutating actions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean CLI commands and tables, with only minor over-explanation (the CloudCart intro paragraph and "so you can focus on the integration logic rather than auth plumbing"), fitting the anchor for efficient content with minor trims possible.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input JSON, request with full flag tables), covering the common cases concretely.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with an explicit validation feedback loop (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but data-mutating actions (create/update/proxy DELETE) lack verification checkpoints, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, but the 20-row Popular actions table is reference material that could live in a separate file, so structure is good with minor organization gaps.	4 / 5
	Total	17 / 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 includes an explicit "Use when..." trigger and names a distinct platform, but its capability list is generic ("data, records, workflows") rather than concrete e-commerce actions. It is functional but would benefit from specific verbs and natural user terms.

Suggestions

Replace generic nouns with concrete actions, e.g. "List, create, and update products, orders, and customers".

Add natural trigger terms users say, such as "products", "orders", "customers", "store", or "catalog".

Tighten the when-clause to reference specific e-commerce intents, e.g. "Use when the user wants to manage products, orders, or customers in their CloudCart store".

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the domain but the actions are generic nouns rather than concrete operations (e.g. listing products or creating orders), matching the anchor that names the domain with minimal/generic actions.	2 / 5
Completeness	It states a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger, satisfying both; the "when" is present but could be more specific, fitting the anchor where both exist but the when could be more explicit.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with CloudCart data" offers the keyword CloudCart but omits natural terms users would actually say (orders, products, customers, store), so it has some relevant keywords but misses common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform CloudCart gives it a clear niche with low conflict risk, but the generic "data, records, workflows" wording leaves minor overlap with other integration skills rather than the fully distinct triggers of a 5.	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/cloudcart/SKILL.md
Commit: f484c82

Reviewed: ~12 hours 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.