shopify-apps
Shopify app development - Remix, Admin API, checkout extensions
48
37%
Does it follow best practices?
Impact
Pending
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.
The description is essentially a comma-separated list of topic keywords rather than a proper skill description. It lacks any concrete actions (verbs), has no 'Use when...' guidance, and reads more like a tag list than a description that would help Claude reliably select this skill from a large pool. The Shopify domain provides some natural distinctiveness, but the description needs significant improvement.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Builds Shopify apps using Remix, integrates with the Admin GraphQL API, creates checkout UI extensions, and configures app webhooks.'
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 developing with Shopify CLI.'
Expand trigger terms to include common variations users might say: 'Shopify store', 'Polaris', 'Shopify CLI', 'app bridge', 'storefront API', 'webhooks', 'GraphQL Admin API'.
| 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 with some technologies) but completely lacks a 'when' clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak—just a topic list rather than described capabilities—warranting a score of 1. | 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', 'GraphQL', or '.liquid'. | 2 / 3 |
Distinctiveness Conflict Risk | The Shopify domain is fairly specific and unlikely to conflict with most other skills, but the mention of 'Remix' could overlap with general Remix/React skills, and 'Admin API' is somewhat generic without the Shopify qualifier being strongly tied to it. | 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 severely over-length for a SKILL.md file — it reads more like a complete tutorial/reference guide than a concise skill. The content would benefit enormously from splitting into separate files (e.g., GRAPHQL.md, EXTENSIONS.md, DEPLOYMENT.md) with the SKILL.md serving as a lean overview with navigation.
Suggestions
Split into multiple files: keep SKILL.md as a concise overview (~100 lines) with quick start and navigation links to separate files like ADMIN-API.md, EXTENSIONS.md, DEPLOYMENT.md, and PATTERNS.md
Remove content Claude already knows or that Shopify CLI generates: prerequisites section, project structure listing, Prisma client singleton pattern, basic Polaris AppProvider setup, and the common scopes reference table
Add explicit validation checkpoints to 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'
Remove the CLI commands reference section — this duplicates `shopify app --help` output and adds no unique value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Includes extensive boilerplate that Shopify CLI generates automatically (project structure, Prisma schema, session model, db.server.js, app layout). Explains prerequisites like creating a Partner account and installing Node.js, which Claude doesn't need. The common scopes table and CLI commands reference duplicate official docs without adding insight. | 1 / 3 |
Actionability | Highly actionable with fully executable code examples throughout — GraphQL queries with variables, complete Remix route patterns, extension components, Prisma schemas, deployment configs, and test examples. Code is copy-paste ready and covers the full development lifecycle. | 3 / 3 |
Workflow Clarity | The checklists at the end provide good sequencing for development and submission phases. However, the main development workflow lacks explicit validation checkpoints — there's no 'verify auth works before proceeding' or 'test webhook delivery before deploying' step. The deploy section is minimal without verification steps. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline — the full settings page component, Prisma schema, deployment config, test examples, rate limit handling, and reference tables are all in one file. No content is split into separate reference files despite the skill being well over 500 lines. The external links at the top point to Shopify docs but internal content is not organized into separate 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 (1028 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
d4ddb03
- 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.