shopify-apps

Shopify app development - Remix, Admin API, checkout extensions

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable, copy-paste-ready Shopify code across the full app lifecycle, but it is a monolithic ~1020-line document that overruns the SKILL.md overview role and lacks explicit validation checkpoints in its build/deploy workflow.

Suggestions

Add a numbered end-to-end workflow (scaffold -> develop -> build -> validate -> deploy) with explicit checkpoints, e.g. run `shopify app build` and confirm no errors before `shopify app deploy`.

Split the monolithic body into one-level-deep reference files (e.g. DEPLOYMENT.md, EXTENSIONS.md, TESTING.md, GDPR.md) and keep SKILL.md a concise overview with clearly signaled links.

Trim standard boilerplate Claude already knows (basic Polaris layout, generic vitest/Playwright scaffolding) to recover token budget for the Shopify-specific patterns only Claude would not recall.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, executable code and config that earns its place, but at ~1020 lines it is far heavier than a SKILL.md overview should be and includes standard patterns Claude already knows (Polaris app layout, Remix settings page, vitest/Playwright boilerplate), fitting the 'mostly efficient but could be tightened' anchor rather than the lean level.	2 / 3
Actionability	It provides fully executable GraphQL queries/mutations, shopify.app.toml configs, CLI commands, Prisma schema, and deployment YAML that are copy-paste ready, matching the 'fully executable code/commands; specific examples' anchor; it is not below because there is no vague or pseudocode-only guidance.	3 / 3
Workflow Clarity	Checklists and some sequencing exist, but the core build-to-deploy flow has no explicit validation checkpoint (e.g. build/verify before `shopify app deploy`), and because deploying app versions and GDPR data deletion are risky operations the missing feedback loop caps this at 2 per the rubric notes.	2 / 3
Progressive Disclosure	The content is well sectioned with clear headings, but it is monolithic: every topic is inline, no references/scripts/assets files exist, and material that should be split out (deployment, extensions, testing) lives in SKILL.md; the under-50-line simple-skill exception does not apply to a ~1020-line document, so it sits at 'some structure but content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 distinct and trigger-rich, naming a clear Shopify niche with natural keywords, but it reads as a technology list rather than a roster of concrete actions and omits an explicit 'Use when...' clause in the description field itself.

Suggestions

Add an explicit 'Use when...' trigger clause to the description (e.g., 'Use when building Shopify apps, checkout UI extensions, or integrating the Admin API') so the when-guidance is self-contained.

Replace the dash-separated technology list with concrete verbs, e.g. 'Scaffold, build, and deploy Shopify Remix apps and checkout UI extensions; query and mutate the Admin API via GraphQL'.

Dimension	Reasoning	Score
Specificity	The description names the domain and tech stack ("Shopify app development - Remix, Admin API, checkout extensions") but lists technologies rather than concrete actions like scaffold, build, deploy, or manage webhooks, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It clearly states what the skill covers but the description field itself contains no "Use when..." clause or equivalent explicit trigger guidance, so per the guideline completeness is capped at 2 rather than reaching the explicit what-and-when level.	2 / 3
Trigger Term Quality	"Shopify app", "Admin API", and "checkout extensions" are exactly the natural terms a user would say when they need this skill, giving good coverage; it is not the level below because it supplies multiple specific, naturally-voiced keywords rather than a single generic phrase.	3 / 3
Distinctiveness Conflict Risk	The Shopify-specific framing (Remix app framework, Admin API, checkout extensions) carves a clear niche with distinct triggers that are unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Commit: 9dacc46

Reviewed: about 5 hours 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.