CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-onboarding-merchant

Set up and connect a Shopify store from your AI assistant. Use when the user wants to: set up my Shopify store, connect my store, install Shopify plugin, get started with Shopify, manage my store, add products to my store, merchant onboarding, start selling online, Shopify setup help, create my first store, how do I set up an online store, import products, migrate from Square, migrate from WooCommerce, migrate from Etsy, migrate from Amazon, migrate from eBay, migrate from Wix, import from Google Merchant Center, migrate from Clover, migrate from Lightspeed, move products to Shopify, import catalog, replatform to Shopify. This is for store owners — not developers.

73

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A highly actionable, well-sequenced merchant onboarding skill: exact commands, complete GraphQL mutations, explicit wait-for-user checkpoints, and validate-preview-confirm loops around every batch mutation. Its main weaknesses are mild redundancy (duplicated install command and shell-safety note, long dialogue templates) and a monolithic single-file layout where platform-specific tables and constraints would fit naturally in on-demand reference files.

Suggestions

Deduplicate the repeated guidance: state the 'write variables JSON to a temp file, never inline merchant data' rule once, and reference the single npm upgrade command instead of repeating it in the failure path.

Move the per-platform material (supported-platforms notes, export paths, validation-guide links, and validation constraints) into a references/ file (e.g., platforms.md) fetched only after the merchant names a platform, keeping SKILL.md as a lean overview plus routing table.

Tighten the scripted response templates (menu wording, example prompts) to shorten the ~540-line body without losing the tone-control intent.

DimensionReasoningScore

Conciseness

The body is dense and operational — nearly every line is an instruction, exact command, table, or scripted response, with no explanation of concepts Claude already knows. Minor trimming is possible: the 'write variables JSON to a file' rule is stated twice ('Write the variables JSON to a temporary file...' followed by '**Important:** Never inline merchant data...'), the npm install command appears twice, and some scripted dialogue templates are longer than needed. Fits anchor 4 (efficient, minor over-explanation) rather than 5.

4 / 5

Actionability

Fully executable throughout: exact install commands ('npm install -g @shopify/cli@latest', 'brew tap shopify/shopify && brew install shopify-cli'), the exact auth command with normalized store handle, complete GraphQL query strings for productSet and inventorySetOnHandQuantities including the @idempotent directive, concrete JSON structures for single- and multi-variant products, per-platform export click-paths, and explicit shell-safety handling for merchant data. Copy-paste ready for the common cases.

5 / 5

Workflow Clarity

Clear sequenced workflow (Steps 1-4, auth, import) with explicit validation checkpoints at every risky point: wait-for-user gates, a dedicated CSV validation stage distinguishing blocking errors from warnings, a preview-and-confirm step before any mutation, and feedback loops for recovery (auth failure -> upgrade CLI -> retry; 'If there were errors, offer to retry the failed products'). The batch import operation is validated both before (CSV validation) and after (error reporting, retry offer), so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

Good structure: heavy per-platform detail (column mappings, validation steps) is deferred to on-demand fetched guides, with compact routing tables in SKILL.md serving as the index, and sections are clearly headed and easy to navigate. However, no bundle files exist (references/, scripts/, assets/ are absent), and several sizable inlined blocks — the scopes table, validation constraints table, supported-platform/export-path/validation-guide triple tables, and known-limitations table — plus ~540 lines total could partly live in reference files fetched only when the merchant names a platform. Fits anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

95%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.

A strong description: it states the skill's purpose in third person, provides an explicit and extensive 'Use when' trigger list covering setup, management, and per-platform migration phrasings, and explicitly scopes out developers. The only weakness is that the opening capability sentence covers just setup/connect, with the fuller capability set (manage, add products, import, migrate) carried by trigger phrases instead of stated actions.

Suggestions

State the fuller capability set in the opening sentence (e.g., 'Set up and connect a Shopify store, manage products, inventory, orders and discounts, and import catalogs from other platforms') so the 'what' is comprehensive rather than carried entirely by the trigger list.

Trim near-duplicate trigger phrasings (e.g., 'migrate from Square' vs 'move products to Shopify' style variants) if a shorter list retains the same coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Set up and connect a Shopify store', 'install Shopify plugin', 'manage my store', 'add products', 'import products', 'migrate from' ten named platforms — though the opening what-statement names only setup and connect, leaving the rest implied via trigger phrases rather than stated capabilities. This fits anchor 4 (several specific actions, minor gaps) rather than 5, where the full capability set would be stated explicitly.

4 / 5

Completeness

Explicitly answers both what ('Set up and connect a Shopify store from your AI assistant') and when ('Use when the user wants to: ...') with a long list of concrete trigger phrases, and adds audience scoping ('This is for store owners — not developers'). Written in third-person/declarative voice with no first- or second-person framing.

5 / 5

Trigger Term Quality

Comprehensive natural phrasing users would actually say: 'set up my Shopify store', 'get started with Shopify', 'start selling online', 'how do I set up an online store', 'merchant onboarding', plus platform-specific migration triggers (Square, WooCommerce, Etsy, Amazon, eBay, Wix, Clover, Lightspeed, Google Merchant Center) and synonyms like 'replatform to Shopify'. Matches the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche with Shopify-specific trigger terms and an explicit boundary ('This is for store owners — not developers') that separates it from developer-oriented Shopify skills. Minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (541 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

openai/plugins

Path

plugins/shopify/skills/shopify-onboarding-merchant/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.