CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-automation

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

64

2.05x
Quality

53%

Does it follow best practices?

Impact

74%

2.05x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

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 reasonable catalog of Shopify operations via Rube MCP with clear tool names and workflow groupings. However, it lacks executable examples (no actual tool invocations with sample parameters), includes some redundant content (quick reference table duplicates workflow sections), and misses validation checkpoints for destructive/batch operations. The content would benefit from being more concise while adding concrete, copy-paste-ready examples.

Suggestions

Add concrete, executable examples showing actual tool invocations with realistic parameters (e.g., a complete SHOPIFY_BULK_CREATE_PRODUCTS call with sample product data)

Add validation/verification steps after batch or mutating operations (e.g., after bulk product creation, verify with SHOPIFY_GET_PRODUCTS_COUNT or spot-check a created product)

Remove the quick reference table or the detailed workflow sections—having both is redundant; keep the table and make workflows more example-driven

Remove generic knowledge sections like API versioning and rate limits, or condense them to single-line warnings within relevant workflows

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some unnecessary content. The 'Known Pitfalls' section about API versioning and rate limits is generic knowledge Claude likely already knows. The quick reference table largely duplicates information already presented in the workflow sections. Some parameter listings are padding rather than adding value.

2 / 3

Actionability

The skill provides tool names and parameter lists, which is somewhat concrete, but lacks executable examples. There are no actual code snippets showing how to call these tools with real parameters, no example payloads for bulk product creation, and the GraphQL section is essentially pseudocode. The instruction to 'always call RUBE_SEARCH_TOOLS first' is good but the skill doesn't show what that call looks like.

2 / 3

Workflow Clarity

Steps are listed with clear sequences and the setup flow includes 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 performing operations like bulk product creation or inventory changes—operations that could benefit from confirmation steps.

2 / 3

Progressive Disclosure

The content is reasonably structured with clear section headers and a quick reference table, but it's a long monolithic file with no bundle files to offload detailed content. The workflow details, parameter lists, and the full reference table could be split into separate files. The external link to Composio docs is helpful but the skill itself could benefit from better content distribution.

2 / 3

Total

8

/

12

Passed

Description

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 automation via a specific MCP tool) and lists relevant entity types, giving it reasonable distinctiveness. However, it lacks specific concrete actions beyond listing entity nouns, misses a 'Use when...' clause, and could benefit from more natural trigger terms that users would actually say when requesting Shopify-related help.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about managing their Shopify store, creating/updating products, processing orders, or managing inventory.'

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

Include additional natural trigger terms like 'e-commerce', 'online store', 'fulfillment', 'shipping', 'discounts', or 'Shopify admin'.

DimensionReasoningScore

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 rather than a trigger condition. Per rubric guidelines, 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 misses common variations like 'e-commerce', 'store', 'shop', 'fulfillment', 'shipping', 'discounts', or specific action-oriented terms users would naturally use.

2 / 3

Distinctiveness Conflict Risk

The description is clearly scoped to Shopify via Rube MCP (Composio), which is a very specific niche. It's unlikely to conflict with other skills unless there are multiple Shopify-related skills, and the mention of the specific MCP tool further distinguishes it.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.