shopify-automation
Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill shopify-automation57
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 niche (Shopify automation via specific tooling) but lacks concrete action verbs and explicit trigger guidance. It tells Claude what entities are involved but not what specific operations can be performed or when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Shopify, e-commerce store management, or needs to manage online shop products/orders'
Replace 'Automate Shopify tasks' with specific actions like 'Create, update, and retrieve Shopify products; process orders; manage customer records; sync inventory levels'
Include common user phrasings like 'online store', 'e-commerce', 'shop inventory', 'order fulfillment' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Shopify) and lists entity types (products, orders, customers, inventory, collections) but doesn't describe specific actions beyond generic 'automate tasks'. Missing concrete verbs like 'create', 'update', 'sync', 'retrieve'. | 2 / 3 |
Completeness | Describes what (automate Shopify tasks) but lacks any explicit 'Use when...' clause or trigger guidance. The instruction to 'search tools first' is implementation guidance, not usage triggers. Missing when clause caps this at 1-2, and the weak 'what' pushes it to 1. | 1 / 3 |
Trigger Term Quality | Includes 'Shopify' and entity names users might mention (products, orders, customers, inventory, collections), but missing common variations like 'e-commerce', 'online store', 'shop', or action-oriented terms like 'add product', 'track order'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Shopify via Rube MCP (Composio) - this is a distinct niche that wouldn't conflict with other skills. The platform-specific naming (Shopify, Rube MCP, Composio) creates clear boundaries. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
57%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 comprehensive overview of Shopify automation via Rube MCP with good organization and clear tool references. However, it lacks concrete executable examples and validation/error-handling steps that would make workflows more robust. The content is somewhat verbose with duplicated information between sections.
Suggestions
Add concrete code/JSON examples showing actual tool calls with sample inputs and expected outputs, especially for common operations like creating a product or filtering orders
Include validation checkpoints in workflows - e.g., 'Verify product was created by calling SHOPIFY_GET_PRODUCT with returned ID' or error handling for rate limits
Remove the Quick Reference table or consolidate it with Core Workflows to eliminate redundancy and reduce token usage
Add a concrete GraphQL query example instead of pseudocode steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the Quick Reference table duplicates information from the Core Workflows section, and some explanations like 'When to use' statements are somewhat obvious given the section headers. | 2 / 3 |
Actionability | Provides tool names and parameter lists but lacks executable code examples. The GraphQL section shows pseudocode-style steps rather than actual query examples. Tool sequences are listed but without concrete input/output examples. | 2 / 3 |
Workflow Clarity | Workflows are listed with clear sequences and optional/required markers, but lack validation checkpoints. No feedback loops for error handling - e.g., what to do if connection fails, how to verify product creation succeeded, or how to handle rate limit errors. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, external toolkit docs linked upfront, and a quick reference table for fast lookup. Content is appropriately structured for a single SKILL.md file without needing additional files for this scope. | 3 / 3 |
Total | 9 / 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 | |
- Reviewed
Table of Contents
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.