CtrlK
BlogDocsLog inGet started
Tessl Logo

shopify-development

Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid.

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/shopify-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, well-structured Shopify development skill that covers the major development surfaces (apps, extensions, themes) with concrete code examples and clear routing logic. Its main weaknesses are some verbosity in best practices/troubleshooting sections that state things Claude already knows, and the lack of explicit validation checkpoints in multi-step workflows like app deployment or extension development. The progressive disclosure is well-designed with clear pointers to reference files.

Suggestions

Add explicit validation/verification steps to workflows — e.g., after 'shopify app deploy', include a step to verify the deployment succeeded and check for errors before proceeding.

Trim the Best Practices and Security sections to remove guidance Claude already knows (e.g., 'store credentials in env vars', 'use exponential backoff') and keep only Shopify-specific advice.

Add the missing React imports (useState, useEffect) to the checkout extension example to make it truly copy-paste ready.

Remove the vacuous 'When to Use' section at the end — it adds no information beyond what the routing section already provides.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary content. The 'Use this skill when' section and 'Best Practices' sections contain guidance Claude already knows (e.g., 'store API credentials in environment variables', 'use exponential backoff'). The GraphQL query examples are somewhat lengthy but useful as reference patterns. The 'When to Use' section at the end is vacuous filler.

3 / 5

Actionability

Provides concrete, executable CLI commands, GraphQL queries with proper syntax, a complete checkout extension TSX example, Liquid template code, and TOML configuration snippets. Minor gaps include the checkout extension example missing React imports (useState, useEffect) and the scripts section lacking usage examples beyond one-liners.

4 / 5

Workflow Clarity

The routing section provides a clear decision tree for what to build, and CLI commands are sequenced logically. However, there are no explicit validation checkpoints in the workflows — for example, after 'shopify app deploy' there's no verification step, and the extension development flow lacks a validate-then-fix loop. The troubleshooting section partially compensates but is reactive rather than proactive.

3 / 5

Progressive Disclosure

Good structure with clear routing to reference files (app-development.md, extensions.md, themes.md) with descriptions of what each contains. References are one level deep and well-signaled. However, since no bundle files were provided, we cannot verify the referenced files exist. The main file includes substantial inline content (GraphQL examples, extension code) that could arguably be in reference files, but the balance is reasonable for a skill overview.

4 / 5

Total

14

/

20

Passed

Description

70%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 concise and technically specific, clearly identifying the Shopify development domain with relevant technologies. Its main weakness is the lack of an explicit 'Use when...' clause that would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural user phrases would elevate it significantly.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Shopify development, building Shopify apps, creating themes, or working with Liquid templates.'

Include additional natural trigger terms like 'storefront', 'e-commerce', 'Hydrogen', 'checkout extensions', or 'Shopify store' to capture more user query variations.

DimensionReasoningScore

Specificity

Lists several specific actions ('Build Shopify apps, extensions, themes') and names concrete technologies (GraphQL Admin API, Shopify CLI, Polaris UI, Liquid). However, it could be more comprehensive about what specific operations are performed (e.g., deploying, testing, configuring webhooks).

4 / 5

Completeness

Clearly answers 'what' (build Shopify apps, extensions, themes using specific technologies) but has no explicit 'when' clause. The absence of a 'Use when...' clause caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'Shopify', 'apps', 'extensions', 'themes', 'GraphQL', 'Polaris', 'Liquid', and 'Shopify CLI' that users would naturally mention. Missing some common variations like 'storefront', 'e-commerce', 'Hydrogen', or 'checkout' that users might also say.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with a clear niche around Shopify development specifically. The combination of Shopify-specific terms (Polaris UI, Liquid, Shopify CLI, GraphQL Admin API) makes it very unlikely to conflict with other skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.