shopify-expert
Use when building Shopify themes, apps, custom storefronts, or e-commerce solutions. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill shopify-expertOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger terms and distinctiveness with strong Shopify-specific vocabulary, making it easy to identify when this skill should be selected. However, it's structured backwards - it focuses on 'when' without clearly stating 'what' the skill actually does. Adding concrete actions (e.g., 'Build and customize Shopify themes, develop apps, integrate APIs') would significantly improve it.
Suggestions
Add concrete action verbs at the beginning describing what the skill does (e.g., 'Builds and customizes Shopify themes, develops apps, integrates Storefront API, configures checkout flows')
Restructure to lead with capabilities before the 'Use when' clause to clearly answer 'what does this do' first
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Shopify) and lists several areas (themes, apps, storefronts, e-commerce solutions, Liquid templating, Storefront API, checkout customization, Shopify Plus), but these are more categories than concrete actions. Missing specific verbs like 'create', 'debug', 'configure', or 'deploy'. | 2 / 3 |
Completeness | Has explicit 'Use when' and 'Invoke for' clauses which is good, but the 'what does this do' portion is weak - it lists contexts/technologies but doesn't clearly state what actions or capabilities the skill provides. The description tells when to use it but not what it actually does. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Shopify themes', 'apps', 'storefronts', 'e-commerce', 'Liquid templating', 'Storefront API', 'checkout customization', 'Shopify Plus'. These are terms developers and merchants naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Shopify-specific terminology (Liquid, Storefront API, Shopify Plus, checkout customization). Very unlikely to conflict with other skills due to the platform-specific focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a high-level overview and routing document to reference files, which is appropriate for progressive disclosure. However, it severely lacks actionability - there are no code examples, no concrete commands, and no executable guidance. The constraints section provides useful guardrails but without accompanying implementation examples, Claude cannot effectively execute Shopify development tasks from this skill alone.
Suggestions
Add at least one executable code example for each major area (Liquid template snippet, Storefront API GraphQL query, basic app scaffold command)
Include specific Shopify CLI commands with actual syntax (e.g., `shopify theme dev`, `shopify app generate extension`)
Add validation checkpoints to the workflow, such as 'Run `shopify theme check` before deployment' and 'Verify webhook signatures in test mode'
Remove or condense the 'Role Definition' section - Claude doesn't need to be told it's a senior developer
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Role Definition' that restates information Claude already knows, and 'Related Skills' that adds little value. The constraints and workflow sections are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete examples, and no copy-paste ready commands. It describes what to do at a high level ('Build Liquid templates', 'Configure theme structure') but never shows how. The reference table points to files but the skill itself lacks any concrete implementation guidance. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints, error recovery steps, or specific commands. For operations like 'Deploy and test' there's no explicit verification step or feedback loop for catching deployment issues. | 2 / 3 |
Progressive Disclosure | The reference table is well-structured with clear one-level-deep references, appropriate 'Load When' context, and good organization. The skill appropriately delegates detailed content to reference files while maintaining a navigable overview. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.