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

snipcart

Snipcart integration. Manage Carts, Products, Customers, Discounts, Orders, ShippingRates. Use when the user wants to interact with Snipcart 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/snipcart/SKILL.md

Quality

Content

61%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 mostly executable and well-structured with a clear connection workflow and feedback loops, but it opens with unnecessary marketing explanation and omits validation/verification steps for action and proxy execution, which caps workflow clarity.

Suggestions

Remove or trim the marketing-style opening paragraph about what Snipcart is and who uses it; assume Claude knows the platform or link the official docs instead.

Add a validation/verification step after running actions and proxy requests (e.g., inspect the `output` field, check for error indicators, confirm write effects before proceeding).

Provide example values for placeholders (e.g., a sample `--intent` query, a sample CONNECTION_ID and actionId) so commands are fully copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	An opening marketing paragraph explains what Snipcart is and who uses it (concepts Claude already knows), and some phrasing like 'those will be used to adjust tooling to be used best with your harness' is padded, going beyond minor over-explanation.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands across install, auth, connection, action discovery, running, and proxying, with minor gaps where placeholders like CONNECTION_ID and <actionId> have no example values and the Popular actions section is thin.	4 / 5
Workflow Clarity	A clear sequence exists with real polling/branching checkpoints for connection state, but running actions and proxy requests (including POST/PUT/PATCH/DELETE) lack verification steps, capping this dimension at 3 per the destructive/batch guidance.	3 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized with clear section headers, but some inline reference-like detail (the proxy flags table, clientAction field schema) and the decorative overview list could be better separated.	4 / 5
	Total	14 / 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 is specific, distinct, and includes both a what and a Use-when clause, naming a concrete platform and its managed resources. Its main weakness is the generic single verb 'Manage' and a generic trigger phrase that keep specificity and completeness just below the top anchors.

Suggestions

Replace the single generic verb 'Manage' with concrete actions per resource (e.g., 'Create, update, list, and search Carts, Products, Customers, Discounts, and Orders').

Make the 'Use when...' trigger more concrete with natural phrases users say, e.g., 'Use when the user wants to manage Snipcart orders, apply discounts, look up customers, or check shipping rates'.

Add common synonyms (e.g., 'shopping cart', 'checkout', 'e-commerce orders') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names six concrete managed resources (Carts, Products, Customers, Discounts, Orders, ShippingRates) but applies a single generic verb ('Manage') rather than listing distinct actions, leaving minor gaps versus comprehensive coverage.	4 / 5
Completeness	Explicitly answers both 'what' (manage listed Snipcart resources) and 'when' (a 'Use when...' clause), but the trigger phrasing 'interact with Snipcart data' is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the platform's primary natural resource terms users would say (orders, customers, discounts, products), but omits synonyms and broader phrases like 'checkout' or 'shopping cart'.	4 / 5
Distinctiveness Conflict Risk	Names a specific e-commerce platform (Snipcart) with its distinct resources, giving a clear niche with minimal conflict risk against other skills.	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/snipcart/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.