Shopify app development - Remix, Admin API, checkout extensions
38
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/shopify-apps/SKILL.mdQuality
Discovery
32%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 is essentially a comma-separated list of topic keywords rather than a proper skill description. It lacks any action verbs describing what the skill does, and completely omits a 'Use when...' clause to guide skill selection. While the Shopify-specific terms provide some natural trigger value, the description needs significant improvement to be effective in a multi-skill selection context.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Builds Shopify apps using Remix, integrates with Admin API and GraphQL, creates checkout and theme extensions, configures webhooks and app authentication.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building or modifying Shopify apps, working with Shopify APIs, creating checkout extensions, or setting up a Remix-based Shopify project.'
Expand trigger terms to include common variations like 'Shopify store', 'Polaris', 'Shopify CLI', 'webhooks', 'GraphQL', 'theme extensions', and 'app bridge'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Shopify app development) and lists some technologies/areas (Remix, Admin API, checkout extensions), but these are more like topic labels than concrete actions. No verbs describing what the skill actually does. | 2 / 3 |
Completeness | Provides a weak 'what' (just topic labels, no concrete actions) and completely lacks a 'when' clause. There is no explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Shopify', 'Remix', 'Admin API', and 'checkout extensions' that users might mention, but misses common variations like 'Shopify app', 'Shopify store', 'Polaris', 'webhooks', 'Liquid', or 'Shopify CLI'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Shopify' with specific technologies like 'Remix' and 'Admin API' provides some distinctiveness, but 'app development' is broad enough to potentially overlap with general web development or Remix-specific skills. | 2 / 3 |
Total | 7 / 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 is comprehensive and highly actionable with excellent executable code examples covering the full Shopify app development lifecycle. However, it is far too verbose for a SKILL.md — it reads as a complete tutorial/reference guide rather than a concise skill file, explaining things Claude already knows and inlining content that should be in separate bundle files. The lack of progressive disclosure and validation checkpoints in workflows are significant weaknesses.
Suggestions
Reduce to ~100-150 lines by keeping only the Quick Start, core patterns (auth, GraphQL query/mutation, webhook), and anti-patterns — move scopes table, CLI commands, Prisma schema, deployment config, testing, and full UI examples to separate bundle files like REFERENCE.md, DEPLOYMENT.md, EXTENSIONS.md
Remove explanatory text Claude already knows (e.g., what Partner Dashboard is, how environment variables work, what Prisma does) and trust Claude to fill in standard patterns
Add explicit validation checkpoints in workflows: e.g., 'After scaffolding, run shopify app dev and verify the app loads in your dev store before proceeding' and 'Test webhook delivery in Partner Dashboard before deploying'
Create bundle files for the detailed reference content (scopes, CLI commands, extension targets) and link to them with clear one-level-deep references from the main SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~600+ lines. It explains basic concepts Claude already knows (what Prisma is, how environment variables work, what scopes do), includes full boilerplate files that the Shopify CLI generates automatically, and provides reference tables (scopes, CLI commands) that belong in external docs. Much of this is a tutorial rather than a skill. | 1 / 3 |
Actionability | The content is highly actionable with fully executable code examples throughout — complete route files, GraphQL queries with variables, Prisma schemas, deployment configs, and test examples. Everything is copy-paste ready with real imports and proper syntax. | 3 / 3 |
Workflow Clarity | The checklists at the end provide good sequencing for development and submission phases, and the quick start has clear steps. However, there are no validation checkpoints within multi-step workflows (e.g., no 'verify auth works before proceeding to API calls', no 'test extension locally before deploying'). The deployment section lacks a verify step after deploy. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The full Prisma schema, complete settings page component, extension examples, deployment configs, testing examples, and reference tables are all inline. With no supporting files, content like the scopes table, CLI commands, testing patterns, and deployment configs should be split into separate referenced files. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1027 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
7e5f7a2
Table of Contents
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.