shopify

Guide for implementing Shopify apps, extensions, themes, and integrations using GraphQL/REST APIs, Shopify CLI, Polaris UI, and various extension types (Checkout, Admin, POS). Use when building Shopify apps, implementing checkout extensions, customizing admin interfaces, creating themes with Liquid, or integrating with Shopify's APIs.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./claude/skills/shopify/SKILL.md

Quality

Content

53%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 content is actionable and reasonably well-structured, but it is bloated with inlined reference material and time-sensitive version pins, and its progressive disclosure is undermined by broken reference-file links. The deploy workflow also lacks an explicit validation checkpoint.

Suggestions

Create the missing reference/ files (cli-commands.md, graphql-admin-api.md, ui-extensions.md) and move the inlined CLI command lists, GraphQL endpoint details, and extension component references into them so SKILL.md stays a lean overview.

Add an explicit validation checkpoint to the Development Workflow before deploy (e.g. 'Run `shopify app dev`, verify the extension renders in the dev store, and confirm webhook deliveries before `shopify app deploy`').

Move the pinned '2025-01' API version into a single dated 'Current API version' note (or a deprecated/old-patterns section) instead of embedding it in endpoint URLs and prose so the skill does not silently go stale.

Dimension	Reasoning	Score
Conciseness	The ~450-line body is mostly efficient reference material, but prose intros ('Real-time event notifications from Shopify', 'Custom data storage for extending Shopify resources') and time-sensitive version pins ('2025-01', 'as of January 2025') sprinkled through endpoints add padding that will go stale and could be tightened.	3 / 5
Actionability	Provides executable copy-paste code for the main cases (GraphQL product query/mutation, React checkout extension, CLI commands, shopify.app.toml), but secondary sections like webhook signature validation and the OAuth flow are described only as bullet hints without code, leaving minor gaps.	4 / 5
Workflow Clarity	The 'Development Workflow' gives a clear init→configure→dev→generate→test→deploy sequence, but the 'test' step is a vague 'Install app on test store' with no explicit pass/fail validation checkpoint before the outward-facing deploy, so the destructive-deploy cap of 3 applies.	3 / 5
Progressive Disclosure	The body signals reference files ('see [reference/cli-commands.md]', 'reference/graphql-admin-api.md', 'reference/ui-extensions.md') but the reference/ directory does not exist, so the links are broken; meanwhile large chunks of CLI/API/extension reference that should live in those files are inlined, leaving a bloated monolith with dangling references.	2 / 5
	Total	12 / 20 Passed

Description

92%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 strong: third-person voice, explicit what-and-when structure, and concrete platform-specific triggers. Its only weakness is trigger-term coverage that omits several synonyms and sub-capabilities the body actually addresses.

Suggestions

Add Storefront API, Hydrogen, Shopify Functions, webhooks, and metafields to the 'Use when' clause so trigger terms match the skill's full scope.

Consider including file/extension cues (e.g. '.liquid theme files', 'shopify.app.toml') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'apps, extensions, themes, and integrations using GraphQL/REST APIs, Shopify CLI, Polaris UI' with named extension types (Checkout, Admin, POS) — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what ('Guide for implementing Shopify apps, extensions, themes, and integrations...') and when ('Use when building Shopify apps, implementing checkout extensions...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The 'Use when' clause covers natural phrases like 'building Shopify apps', 'checkout extensions', 'themes with Liquid', and 'integrating with Shopify's APIs', but omits common synonyms present in the body (Storefront API, Hydrogen, Shopify Functions, webhooks, metafields).	4 / 5
Distinctiveness Conflict Risk	Shopify-specific niche with distinct triggers (Polaris, Liquid, Checkout/Admin/POS extensions) makes conflict with other skills minimal; the scope is tightly bounded to the Shopify platform.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 6 missing	Warning

	Total	15 / 16 Passed

Repository: einverne/dotfiles
Path: claude/skills/shopify/SKILL.md
Commit: 7d18cf4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.