CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-automation

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/shopify-automation/SKILL.md

The canonical home for this skill is shopify-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 delivers genuinely useful, non-obvious operational content (exact Composio tool slugs, parameters, pagination patterns, rate limits) organized into clear per-domain workflows, but it is held back by a redundant quick-reference table, a filler closing section, missing validation steps for batch operations, and a monolithic single-file structure with no progressive disclosure. Tightening duplication and moving the tool catalog to a reference file would raise it substantially.

Suggestions

Add validation/verification steps after batch or mutating operations, e.g., after SHOPIFY_BULK_CREATE_PRODUCTS confirm via SHOPIFY_GET_PRODUCTS_COUNT or SHOPIFY_GET_PRODUCT before reporting success.

Remove the duplicated Quick Reference table (or the per-workflow tool listings) and drop the empty 'When to Use' filler section; a single source of truth for the tool catalog is enough.

Move the tool catalog / quick-reference table into a references/ file (e.g., references/tool-catalog.md) and keep SKILL.md as a lean overview pointing to it, giving the skill one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

Most content is non-obvious operational detail (Composio tool slugs, parameters, pitfalls, rate limits) that earns its place, but the 17-row Quick Reference table fully duplicates the Core Workflows tool sequences, and the closing 'When to Use' section is pure filler ('This skill is applicable to execute the workflow or actions described in the overview.'). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than anchor 4's minor trims.

3 / 5

Actionability

Concrete, specific instruction-style guidance throughout: exact tool slugs, ordered tool sequences, and parameter lists (e.g., "Call RUBE_MANAGE_CONNECTIONS with toolkit shopify", "status: 'active', 'draft', or 'archived'", "Use limit and page_info cursor for paginated results"). Minor gaps keep it from anchor 5: no example call payloads or responses, and the [Optional]/[Required] markers on tool-sequence steps are confusing rather than instructive.

4 / 5

Workflow Clarity

The Setup section has a genuine validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'), and each workflow has an ordered tool sequence. However, batch and destructive operations (SHOPIFY_BULK_CREATE_PRODUCTS, SHOPIFY_CREATE_SMART_COLLECTIONS, SHOPIFY_ADD_PRODUCT_TO_COLLECTION) have no post-operation verification steps, and per the judging guidelines missing validation in batch operations caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and no external references are signaled; the full tool catalog plus the 17-row quick-reference table are inlined in a ~165-line file where that reference material clearly belongs in a separate file. Section organization is good (so not anchor 2), but with everything inline and no references at all it fits 'content that should be separate is inline' rather than anchor 4.

3 / 5

Total

13

/

20

Passed

Description

65%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 clearly identifies its niche (Shopify automation via Rube MCP/Composio) and lists the covered object domains with good natural trigger terms, but it lacks an explicit 'Use when...' trigger clause and relies on one generic action verb rather than concrete per-domain actions. These gaps hold it to a mid-tier rating despite strong distinctiveness.

Suggestions

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

Replace the generic 'Automate Shopify tasks' with concrete verbs per domain, e.g., 'list and create products, search orders, query inventory levels, manage collections'.

Include a few natural synonyms users might say, such as 'store', 'fulfillment', or 'e-commerce', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ("Automate Shopify tasks via Rube MCP (Composio)") and enumerates five capability areas ("products, orders, customers, inventory, collections"), but the single generic verb "Automate... tasks" conveys no concrete per-area actions, unlike the anchor-4 pattern of distinct specific verbs. It sits above anchor 2 (actions are not minimal) but below anchor 4 (no specific actions like 'create products' or 'list orders' are stated).

3 / 5

Completeness

The 'what' is clear (automating products, orders, customers, inventory, collections via Rube MCP), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing explicit 'when' caps completeness at 3, matching the anchor 'clear what but when missing'.

3 / 5

Trigger Term Quality

"Shopify", "products", "orders", "customers", "inventory", "collections" are all terms users naturally say when needing this skill. A few natural terms are missing (e.g., "store", "fulfillment", "e-commerce"), so it does not reach the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The combination of "Shopify" and "Rube MCP (Composio)" defines a clear niche with distinct triggers; no other skill category would plausibly be triggered by these terms. This matches the anchor-5 example of minimal conflict risk.

5 / 5

Total

15

/

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/shopify-automation/SKILL.md

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.