shopify-automation

Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.

2.05x

Quality

53%

Does it follow best practices?

Impact

74%

2.05x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/shopify-automation/SKILL.md

Quality

Discovery

57%

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 identifies a clear domain (Shopify via Rube MCP/Composio) and lists relevant entity types, making it reasonably distinctive. However, it lacks specific concrete actions beyond 'automate tasks' and is missing an explicit 'Use when...' clause that would help Claude know when to select this skill. Adding action verbs and trigger guidance would significantly improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Shopify store management, creating/updating products, processing orders, or managing inventory.'

Replace the vague 'Automate Shopify tasks' with specific actions like 'Create and update products, process and fulfill orders, manage customers, adjust inventory levels, organize collections.'

Include additional natural trigger terms users might say, such as 'e-commerce', 'online store', 'shipping', 'refunds', or 'discounts'.

Dimension	Reasoning	Score
Specificity	Names the domain (Shopify) and lists entity types (products, orders, customers, inventory, collections), but doesn't describe specific concrete actions like 'create products', 'update inventory levels', or 'process refunds'. The word 'Automate' is somewhat vague.	2 / 3
Completeness	The 'what' is partially addressed (automate Shopify tasks across several entities), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is an implementation detail, not a trigger condition. Per rubric, missing 'Use when' caps completeness at 2.	2 / 3
Trigger Term Quality	Includes good keywords like 'Shopify', 'products', 'orders', 'customers', 'inventory', 'collections', and 'Rube MCP (Composio)'. However, it misses common user variations like 'store', 'e-commerce', 'shipping', 'refunds', 'discounts', or 'Shopify store management'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Shopify', 'Rube MCP (Composio)', and specific Shopify entity types creates a clear niche that is unlikely to conflict with other skills. This is highly distinctive.	3 / 3
	Total	9 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid catalog of Shopify tools and workflows with clear organization, but lacks executable examples (no actual tool call payloads or expected responses), validation/error-handling steps in workflows, and could be more concise by eliminating duplication between workflow sections and the quick reference table. The content reads more like a reference guide than an actionable skill.

Suggestions

Add at least one concrete, copy-paste-ready tool invocation example with actual parameters and expected response structure (e.g., a RUBE_SEARCH_TOOLS call followed by a SHOPIFY_GET_PRODUCTS call with sample output).

Add validation checkpoints to destructive/batch workflows — e.g., after SHOPIFY_BULK_CREATE_PRODUCTS, verify product count or check for errors in the response before proceeding.

Remove the quick reference table or the detailed workflow sections — having both is redundant. Consider keeping the table as the primary reference and condensing workflows to just the non-obvious sequencing and pitfalls.

Add a concrete GraphQL example with an actual query string rather than pseudocode steps.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy — the quick reference table largely duplicates information already covered in the workflow sections. Some pitfalls are fairly obvious (e.g., 'Large customer lists require pagination'). The content could be tightened by ~30%.	2 / 3
Actionability	Tool names and parameter lists are concrete, but there are no executable code examples or copy-paste-ready tool invocations with actual parameter values. The GraphQL section is essentially pseudocode. Users get tool slugs but not example payloads or responses.	2 / 3
Workflow Clarity	Workflows are listed with clear sequences and labeled steps, but there are no validation checkpoints or error recovery loops. The setup section has a good sequential flow with a connection verification step, but the core workflows lack any 'verify result' or 'if error, then...' guidance, which matters for operations like bulk product creation.	2 / 3
Progressive Disclosure	The content is reasonably structured with clear sections and a quick reference table, but it's quite long (~150 lines of substantive content) with no references to external files for detailed workflows. The toolkit docs link is good, but detailed sections like inventory or collections could be split out.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: 7cc63f3

Reviewed: about 3 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.