shopify-automation

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

2.05x

Quality

—

Does it follow best practices?

Impact

74%

2.05x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A well-structured, highly actionable routing skill that assumes Claude's competence and avoids conceptual padding. Its main weaknesses are redundant recap content and missing verification feedback loops around batch/mutating operations.

Suggestions

Add a verification step after bulk create and inventory mutations (e.g., re-query the affected product/location to confirm the change applied) to establish a validate→fix→retry loop.

Collapse the 'Quick Reference' table or fold 'Known Pitfalls' into the per-section 'Pitfalls' lists to remove the redundancy and tighten conciseness.

Consider moving the per-domain tool sequences and parameter tables into a reference file linked from a concise overview, so the SKILL.md body stays a lean entry point.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of padded conceptual explanation, but the 'Quick Reference' table largely restates the per-section tool sequences and 'Known Pitfalls' repeats per-domain pitfalls, so it could be tightened.	2 / 3
Actionability	Provides exact tool slugs, named key parameters, and a quick-reference table, giving concrete, directly usable routing guidance; the absence of executable code is appropriate for this instruction-only skill.	3 / 3
Workflow Clarity	Setup is sequenced with an explicit ACTIVE-status checkpoint, but batch/mutating operations like 'SHOPIFY_BULK_CREATE_PRODUCTS' and inventory changes lack validate→fix→retry feedback loops, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but at ~166 lines it is a single monolithic file with all detail inline and no split-out references, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with good natural trigger terms and a clear niche, weakened only by the absence of an explicit 'Use when...' trigger clause. Adding one sentence on when to invoke it would lift completeness.

Suggestions

Add an explicit trigger clause such as 'Use when automating Shopify store operations — managing products, orders, customers, inventory, or collections.' to satisfy the 'when' half of completeness.

Lead with the user-facing verb actions (e.g., 'Create, list, and update Shopify products and orders') before naming the underlying MCP, so the description reads as capabilities rather than a tool list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — 'products, orders, customers, inventory, collections' — each a distinct, specific Shopify domain rather than vague language.	3 / 3
Completeness	Clearly states what it does, but lacks an explicit 'Use when...' trigger clause — 'Always search tools first for current schemas' is process guidance, not a usage trigger, capping completeness at 2.	2 / 3
Trigger Term Quality	Uses natural user-facing terms ('Shopify', 'products', 'orders', 'customers', 'inventory', 'collections') that a user would actually say, giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	The narrow Shopify-via-Rube-MCP niche with domain-specific triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: davepoon/buildwithclaude
Commit: 366e45b

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