Name: shopify
Rating: 59.2 (1 reviews)
Author: membranedev

shopify

Shopify integration. Manage e-commerce data, records, and workflows. Use when the user wants to interact with Shopify 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/shopify/SKILL.md

Quality

Content

68%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 highly actionable with concrete, executable Membrane commands and a clear connection workflow. Its main weaknesses are an unnecessary introductory explanation of Shopify and the absence of verification steps around destructive actions.

Suggestions

Remove or trim the opening paragraph explaining what Shopify is; Claude already knows this and it costs context tokens.

Add a verification step to the Running-actions and Proxy workflows for destructive operations (e.g. re-fetch the resource after delete/update, or check the response error field before proceeding) so the workflow clears the destructive-ops validation cap.

Tighten padded prose such as "so you can focus on the integration logic rather than auth plumbing" to keep only the actionable detail.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Shopify is a platform that enables anyone to set up an online store...") explains a concept Claude already knows, and prose like "so you can focus on the integration logic rather than auth plumbing" adds padding; most of the body is efficient concrete commands, so it sits at anchor 3 rather than 4.	3 / 5
Actionability	The body provides copy-paste-ready commands for every stage (login, connection ensure, action list/run, request) with flags and JSON examples, plus a table of concrete action keys covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state polling and a re-poll feedback loop, but destructive and batch operations (delete-product, adjust-inventory-level, update-*) run with no verification step before or after; per the rubric cap, missing validation for destructive/batch operations holds this at 3.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references; the inlined Popular-actions table is reasonable for a CLI skill, giving good structure with only a minor organization gap, so anchor 4 fits better than 3 or 5.	4 / 5
	Total	15 / 20 Passed

Description

68%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 well-formed with a clear niche and an explicit Use-when clause, but its capability statement is generic. Concrete verbs and a few Shopify-specific trigger terms would lift it from good to comprehensive.

Suggestions

Replace the generic "Manage e-commerce data, records, and workflows" with concrete actions, e.g. "List and create orders, products, and customers; manage inventory and draft orders".

Add concrete trigger terms users actually say — orders, products, customers, inventory, store — to the Use-when clause to improve trigger-term coverage and specificity.

Dimension	Reasoning	Score
Specificity	The phrase "Manage e-commerce data, records, and workflows" names the Shopify domain but relies on the generic verb "manage" and abstract nouns, with no concrete actions such as list/create/update; this matches anchor 2 (names domain, actions minimal or generic) rather than 3, which requires 1-2 concrete actions.	2 / 5
Completeness	It states both a "what" ("Manage e-commerce data, records, and workflows") and an explicit "when" ("Use when the user wants to interact with Shopify data"), satisfying anchor 4; it is not 5 because neither the what nor the when is comprehensive or concretely triggered.	4 / 5
Trigger Term Quality	The description includes the dominant natural keyword "Shopify" plus "e-commerce data" and "interact with Shopify data", giving good keyword coverage; it stays at 4 rather than 5 because common concrete terms users say (orders, products, customers, store) are absent.	4 / 5
Distinctiveness Conflict Risk	"Shopify integration" names a specific platform with distinct triggers ("Shopify", "interact with Shopify data"), giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/shopify/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.