Name: samcart
Rating: 58.4 (1 reviews)
Author: membranedev

samcart

SamCart integration. Manage Products, Orders, Customers, Funnels, Upsells. Use when the user wants to interact with SamCart data.

Quality

68%

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/samcart/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 content delivers concrete, actionable CLI commands and a reasonably clear connection workflow with state-based checkpoints. It is held back by verbosity (intro paragraph, long entity list, duplicated guidance), missing validation for destructive operations, and a fully inlined structure with no progressive disclosure.

Suggestions

Trim the SamCart marketing-style intro paragraph and collapse the ~30-item noun-only entity list into a compact reference, since Claude can discover entities via `membrane action list`.

Add an explicit validation/verification checkpoint before running destructive actions like refunds, cancellations, or payouts (e.g., confirm the target order, run in a non-mutating preview first, then verify the result).

Move the proxy flag reference table and the full entity catalog into a separate reference file linked from SKILL.md to improve progressive disclosure and reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clean command examples, but it pads tokens with the SamCart e-commerce intro paragraph, a ~30-item noun-only entity list, and partially duplicated action-list guidance that could be tightened.	3 / 5
Actionability	Provides concrete, mostly executable commands (install, login, connection ensure, action list/run with --input JSON, request proxy with a flag table); placeholders like CONNECTION_ID and QUERY keep it just short of copy-paste ready.	4 / 5
Workflow Clarity	The connection setup has a clear state-polling sequence with checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but destructive SamCart operations (refunds, cancellations, payouts) lack any explicit validation step, capping the score at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and everything is inlined in a single ~170-line SKILL.md; section headings give some structure, but bulk reference content (the entity list, the proxy flag table) that could live in separate files is inlined with no one-level-deep references.	3 / 5
	Total	13 / 20 Passed

Description

78%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 cleanly states the domain, lists several concrete objects to manage, and includes an explicit "Use when..." trigger, giving it strong distinctiveness. Its main weakness is the generic verb "Manage" and a broad trigger clause that keep specificity and completeness just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names the SamCart domain and enumerates several concrete objects ("Products, Orders, Customers, Funnels, Upsells"), but the single generic verb "Manage" applied to all leaves minor coverage gaps versus a more action-specific breakdown.	4 / 5
Completeness	Answers both "what" ("Manage Products, Orders, Customers, Funnels, Upsells") and "when" ("Use when the user wants to interact with SamCart data") explicitly; the "when" trigger is somewhat broad rather than concretely enumerated.	4 / 5
Trigger Term Quality	Covers natural user terms well ("SamCart", "Products", "Orders", "Customers", "Funnels", "Upsells", "interact with SamCart data"), though it lacks synonyms or variations that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	SamCart is a specific e-commerce platform with a clear niche and distinct triggers ("SamCart data"), making conflict with unrelated skills minimal.	5 / 5
	Total	17 / 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/samcart/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.