Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.
64
53%
Does it follow best practices?
Impact
74%
2.05xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/shopify-automation/SKILL.mdQuality
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, giving it good distinctiveness. 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. The implementation note about searching tools first, while useful, takes up space that could be used for trigger terms or action specifics.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Shopify store management, e-commerce operations, or mentions Shopify products, orders, or inventory.'
Replace the vague 'Automate Shopify tasks' with specific actions like 'Create and update products, process orders, manage customers, adjust inventory levels, and organize collections in Shopify.'
Add common user-facing trigger terms like 'e-commerce', 'online store', 'shop', 'fulfillment', or 'shipping' to improve keyword coverage.
| 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 entity types), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'always 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 'Shopify', 'products', 'orders', 'customers', 'inventory', 'collections' which are relevant keywords users might say. However, it's missing common variations like 'e-commerce', 'store', 'shop', 'fulfillment', 'shipping', or specific action terms users would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Shopify' and 'Rube MCP (Composio)' creates a very distinct niche. It's unlikely to conflict with other skills unless there are multiple Shopify-related skills, and the specific tooling reference further narrows it. | 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 but suffers from being a reference document rather than an actionable guide. It lists tools and parameters without showing concrete invocation examples, and the workflows lack validation checkpoints for operations that modify data. The content is moderately well-organized but could benefit from splitting into overview + detailed reference files and adding executable examples.
Suggestions
Add concrete, copy-paste-ready tool invocation examples with realistic parameter values (e.g., show an actual RUBE_SEARCH_TOOLS call and a SHOPIFY_BULK_CREATE_PRODUCTS call with a sample product payload).
Add validation/verification steps after write operations (e.g., after bulk product creation, verify with SHOPIFY_GET_PRODUCTS; after inventory changes, confirm with SHOPIFY_GET_INVENTORY_LEVELS).
Remove the quick reference table which largely duplicates the workflow sections, or consolidate the workflows into just the table to reduce redundancy.
Move detailed per-workflow pitfalls and parameters into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the setup flow and most common patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some unnecessary content. The 'When to use' lines are somewhat redundant, and the pitfalls sections contain information Claude likely already knows (e.g., 'Customer data includes order count and total spent'). The quick reference table at the end largely duplicates the workflow sections above it. | 2 / 3 |
Actionability | The skill provides specific tool names and parameter lists, which is helpful, but lacks executable examples showing actual tool invocations with concrete parameter values. The GraphQL section is particularly vague ('Call SHOPIFY_GRAPH_QL_QUERY with custom query' is pseudocode-level). No example payloads or responses are shown. | 2 / 3 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows mark most steps as [Optional] without clear decision logic for when to use each, and there are no validation/verification steps after operations like bulk product creation or inventory changes. Missing feedback loops for destructive/batch operations. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections and a quick reference table, but it's a long monolithic file with no bundle files to offload detail into. The workflow details, pitfalls, and quick reference table could be split into separate files. The external link to Composio docs is helpful but the skill itself tries to contain everything inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 | |
d065ead
Table of Contents
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.