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.

71

2.05x
Quality

65%

Does it follow best practices?

Impact

74%

2.05x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/shopify-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The body is well-structured and mostly efficient, with concrete tool references and a clear setup sequence. Its main weaknesses are missing validation checkpoints for batch/destructive operations and non-executable GraphQL examples.

Suggestions

Add explicit validation/verification steps after bulk or destructive operations (e.g. verify created product count, query order status after bulk create).

Replace the prose-in-a-code-fence GraphQL section with an actual executable GraphQL query example and a parsed-response note.

Move the Quick Reference table into a separate reference file (e.g. references/quick-reference.md) and link to it, reducing duplication with the workflow sections.

DimensionReasoningScore

Conciseness

Lean tool sequences and parameter lists with no over-explanation of concepts, but the Quick Reference table duplicates much of the per-workflow tool sequences, adding redundancy.

4 / 5

Actionability

Concrete tool names and key parameters are actionable for an MCP skill, but the GraphQL section is prose steps in a code fence rather than executable query examples, and no sample request payloads are provided.

3 / 5

Workflow Clarity

Setup has a clear numbered sequence with an ACTIVE-status checkpoint, but batch/destructive operations like SHOPIFY_BULK_CREATE_PRODUCTS and BULK_QUERY_OPERATION lack validation/verification steps, which caps this at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references; the long Quick Reference table could plausibly live in a separate reference file, leaving a minor organization gap.

4 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 is specific and well-scoped to a clear niche, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when...' sentence would lift it into the top tier.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Shopify products, orders, customers, inventory, or collections.'

Use concrete action verbs per domain (e.g. 'list, search, create, and update products, orders, and customers') instead of the single verb 'Automate'.

Include a few more natural synonyms (e.g. 'store', 'checkout', 'fulfillment') to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists five concrete Shopify domains (products, orders, customers, inventory, collections), but relies on a single generic verb ('Automate') rather than enumerating specific actions per area, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is explicit ('Automate Shopify tasks via Rube MCP (Composio): products, orders, customers, inventory, collections'), but there is no 'Use when...' trigger clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Shopify', 'products', 'orders', 'customers', 'inventory', 'collections'), but omits common synonyms such as 'store', 'checkout', or 'fulfillment'.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Shopify automation via the Rube MCP/Composio toolkit, a distinct niche with dedicated triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.