shopify-apps

Shopify app development - Remix, Admin API, checkout extensions

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/shopify-apps/SKILL.md

Quality

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.

The description is essentially a comma-separated list of topic keywords rather than a proper skill description. It lacks any verb-driven explanation of what the skill does, has no 'Use when...' clause, and reads more like a tag list than guidance for skill selection. While the Shopify-specific terms provide some natural trigger value, the description is far too sparse to reliably guide Claude in choosing this skill.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Builds Shopify apps using Remix, integrates with the Admin API, and creates checkout UI extensions.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building or debugging Shopify apps, working with Shopify APIs, creating checkout extensions, or using Remix with Shopify.'

Expand trigger terms to include common variations like 'Polaris', 'Shopify store', 'webhooks', 'app bridge', 'storefront API', or 'theme app extensions' to improve matching coverage.

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 partial 'what' (Shopify app development) but no 'when' clause at all. There is no 'Use when...' or equivalent trigger guidance, and the 'what' itself is more of a topic label than a clear explanation of capabilities.	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', 'storefront', 'webhooks', or 'theme development'.	2 / 3
Distinctiveness Conflict Risk	The Shopify-specific terms provide some distinctiveness, but 'Remix' could overlap with general Remix/React skills, and the description is too terse to clearly delineate its boundaries from a general web development or API skill.	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.

The skill is 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 more like comprehensive reference documentation than a focused skill file. The lack of progressive disclosure (no bundle files, everything inlined) and missing validation checkpoints in workflows are significant weaknesses.

Suggestions

Split content into separate bundle files (e.g., ADMIN_API.md, EXTENSIONS.md, DEPLOYMENT.md, TESTING.md) and reduce SKILL.md to a concise overview with quick start and clear pointers to each reference file.

Remove content Claude already knows — common scopes table, basic Prisma client setup, Polaris AppProvider boilerplate, and explanatory comments like 'This authenticates the request'.

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 'After deploying, run shopify app open to verify the deployment succeeded'.

Trim the quick start to just the essential scaffold + first working route, deferring all other patterns to referenced files.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~600+ lines, covering prerequisites, Partner Dashboard setup, full project structure, complete configuration files, full UI component code, Prisma schemas, deployment configs, testing examples, rate limiting, and checklists. Much of this is reference documentation Claude already knows or can look up, and it massively exceeds what a skill file should contain. Explanations like 'This authenticates the request and redirects to login if needed' and listing common scopes in a table are unnecessary.	1 / 3
Actionability	The skill provides fully executable, copy-paste ready code throughout — complete route files, GraphQL queries with variables, Prisma schemas, extension components in TSX, deployment configs, and CLI commands. Every section contains concrete, runnable examples rather than abstract descriptions.	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 the multi-step workflows (e.g., no 'verify auth works before proceeding to API calls', no 'test extension locally before deploying'). The deployment section lacks verification steps after deploy.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no bundle files to offload content to. The entire Admin API reference, Polaris UI patterns, extension examples, Prisma setup, deployment config, testing, and rate limiting are all inlined in a single file. This should be split into separate reference files (e.g., ADMIN_API.md, EXTENSIONS.md, DEPLOYMENT.md) with the SKILL.md serving as a concise overview with pointers.	1 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: alinaqi/claude-bootstrap
Commit: 65efb33

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.