CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shopify-development

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

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shopify-development/SKILL.md

The canonical home for this skill is shopify-development in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-structured, highly actionable skill with real CLI commands, configs, and code covering the main Shopify surfaces, backed by genuine one-level-deep reference files. The main weaknesses are an implicit rather than explicit development workflow (no validation checkpoints), inline GraphQL blocks that duplicate the references, and one non-runnable code example.

Suggestions

Add an explicit stepwise app workflow with validation checkpoints, e.g.: 1. 'shopify app init' 2. configure scopes in shopify.app.toml 3. 'shopify app dev' → verify the tunnel loads 4. test webhook HMAC validation locally 5. only then 'shopify app deploy'.

Move the full GraphQL query blocks into 'references/app-development.md' and keep one compact example inline, trimming the duplicated material and the filler 'When to Use' sentence.

Fix the checkout extension example to import 'useState' and 'useEffect' from 'react' so it is copy-paste executable.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and code with almost no concept explanations Claude already knows, but it can be tightened: ~90 lines of full GraphQL queries duplicate material in 'references/app-development.md', the API version '2026-01' is pinned twice in the body (time-sensitive detail not in a deprecated/old-patterns section), and the trailing 'When to Use' sentence ('This skill is applicable to execute the workflow or actions described in the overview.') is pure filler. This fits anchor 3 (mostly efficient, some tightening possible) better than 4, whose 'minor instances' understates the inlined query blocks.

3 / 5

Actionability

Guidance is highly executable: install/init/deploy CLI commands, TOML access-scope and webhook configs, complete GraphQL queries with a variables example, a working Liquid snippet, and IF/→ troubleshooting steps. It falls just short of anchor 5 because the checkout extension example uses 'useState' and 'useEffect' without importing them, so that block is not copy-paste runnable — a concrete minor gap matching anchor 4.

4 / 5

Workflow Clarity

The ROUTING section is a clear IF/→ decision tree and the CLI section implies a sequence (init → dev → deploy), but no explicit ordered workflow with validation checkpoints exists (e.g., verify the dev tunnel, confirm scopes granted, test webhook delivery before deploy). This matches anchor 3 (sequence present/implicit, checkpoints missing); it is not 4 because 'most checkpoints present' is not met, and not 2 because the routing and troubleshooting sections give coherent, well-defined structure.

3 / 5

Progressive Disclosure

Good structure: a routing table pointing to the three real one-level-deep reference files (verified present: app-development.md, extensions.md, themes.md), a 'Reference Files' section describing each file's contents, and documented scripts. It is not 5 because some reference-level material (full GraphQL queries) is inlined in SKILL.md instead of being pointed to, and the 'scripts/tests' directory is never mentioned — minor organization gaps matching anchor 4.

4 / 5

Total

14

/

20

Passed

Description

65%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 highly distinctive and keyword-rich within its niche, but it is a stack listing rather than a capability statement: a single generic verb ('Build') and no 'Use when...' trigger clause. Adding explicit actions (deploy, query, scaffold, customize checkout) and a trigger clause would lift it substantially.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks about Shopify app development, theme customization, checkout extensions, or Shopify API integrations.'

Replace the single verb 'Build' with several concrete actions, e.g. 'Scaffold, develop, and deploy Shopify apps and extensions; build and customize Liquid themes; query the GraphQL Admin API.'

Include natural user phrasings such as 'storefront', 'checkout customization', and 'webhooks' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Build Shopify apps, extensions, themes') plus a concrete tool stack ('GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid'), but the only action verb is 'Build' — it never states what is actually done (authenticate, deploy, query, template). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is not 4 because no several distinct actions are listed, and not 2 because the named artifacts and tools go beyond minimal/generic.

3 / 5

Completeness

The 'what' is clear (build Shopify apps/extensions/themes with the named tools), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the judging guidelines explicitly cap completeness at 3 in that case. It is not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms a user would say are present: 'Shopify', 'apps', 'extensions', 'themes', 'Liquid', 'Polaris'. It is not 5 because common user phrasings like 'storefront', 'checkout', 'webhooks', or 'Shopify store' are absent; it is above 3 because coverage of the core vocabulary is good, not just partial.

4 / 5

Distinctiveness Conflict Risk

'Build Shopify apps, extensions, themes using GraphQL Admin API, Shopify CLI, Polaris UI, and Liquid' occupies a clear niche with distinct triggers; only Shopify-development requests would match it, so conflict risk is minimal — a clean match for anchor 5.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shopify-development/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.