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.
87
Quality
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 is an excellent skill description that follows best practices. It uses third person voice, provides specific technologies and capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and is clearly distinguishable from other skills due to its Shopify-specific focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'implementing Shopify apps, extensions, themes, and integrations using GraphQL/REST APIs, Shopify CLI, Polaris UI, and various extension types (Checkout, Admin, POS)'. This provides comprehensive coverage of specific capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Guide for implementing Shopify apps, extensions, themes, and integrations...') AND when ('Use when building Shopify apps, implementing checkout extensions, customizing admin interfaces, creating themes with Liquid, or integrating with Shopify's APIs'). Has explicit 'Use when...' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Shopify apps', 'checkout extensions', 'admin interfaces', 'themes', 'Liquid', 'Shopify's APIs', 'GraphQL', 'REST APIs', 'Polaris'. These are terms developers naturally use when working with Shopify. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Shopify ecosystem. The combination of Shopify-specific terms (Polaris, Liquid, Checkout extensions, Admin extensions, POS) makes it highly unlikely to conflict with other e-commerce or general web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive Shopify development skill with excellent actionability through executable code examples and good progressive disclosure via clear references to detailed documentation. However, it could be more concise by removing explanations of concepts Claude already knows and would benefit from explicit validation checkpoints in the development workflow to catch errors early.
Suggestions
Remove or condense generic explanations (OAuth flow basics, what metafields are) and focus on Shopify-specific implementation details
Add validation checkpoints to the Development Workflow section (e.g., 'Verify app installed: check Partner Dashboard for installation status' after step 5)
Remove the 'When to Use This Skill' section as it duplicates information evident from the content itself
Integrate troubleshooting guidance into relevant workflow steps rather than as a separate section at the end
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude would know (e.g., explaining what OAuth is, what metafields are for). The 'When to Use This Skill' section is redundant given the content. Some sections like 'Best Practices' contain generic advice that doesn't add Shopify-specific value. | 2 / 3 |
Actionability | Provides fully executable code examples including GraphQL queries, CLI commands, and React extension code. Commands are copy-paste ready with specific syntax, and code examples are complete and runnable. | 3 / 3 |
Workflow Clarity | The 'Development Workflow' section provides a clear sequence but lacks validation checkpoints. No verification steps between stages (e.g., confirming app installation succeeded, validating extension configuration before deployment). Troubleshooting is separate rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview sections and explicit references to detailed documentation (reference/cli-commands.md, reference/graphql-admin-api.md, reference/ui-extensions.md). Navigation is clear with one-level-deep references properly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- einverne/dotfiles
- Commit
b1b2fe0
- 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.