shopify-app-dev

I took a look at your shopify-app-dev skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 60/100, which puts you in D territory. The skill covers real Shopify development needs (solid utility score at 14/20), and your trigger terms are pretty strong—Shopify CLI, OAuth, Hydrogen, Remix are all there. But the architecture and structure need work. This is based on Anthropic's skill best practices.

Strongest areas: Spec Compliance (12/15) and metadata clarity
Weakest area: Progressive Disclosure Architecture (11/30)—this is your biggest opportunity

What's Working Well

• Rich code examples. You've got full implementations for config setup, API calls, and webhook handling—that's genuinely useful when someone's building something.
• Solid trigger coverage. Shopify CLI, Remix, extensions, webhooks, Cloudflare Workers—you've got the keywords people search for.
• Good section hierarchy. The 8 numbered capability sections are easy to scan, and the structure makes sense (setup → workflow → deployment).

The Big One: Monolithic Structure (PDA)

Your entire skill is 744 lines in a single SKILL.md file. Every time Claude loads this skill, the whole thing comes down. This is killing your Progressive Disclosure Architecture score (11/30) and burning token budget unnecessarily.

The fix: Split into a reference architecture:

references/
  ├── shopify-cli-setup.md
  ├── remix-architecture.md
  ├── extensions-guide.md
  ├── webhooks-guide.md
  └── deployment.md

Keep SKILL.md lean—just the basics and pointers to references that load on-demand. This alone would bump you +15 points.

Other Things Worth Fixing

1. No feedback loops. You tell people to run shopify app deploy but never verify it worked or troubleshoot failures. Add: "Verify: shopify app info" and "If you see OAuth redirect error → check shopify.app.toml redirect_urls". +3 points

2. Second-person voice throughout. Phrases like "your-app.com" and "your_api_key" make it read like a tutorial instead of reference material. Use placeholders: <app-domain>, <api-key>. +2 points

3. Missing workflow checklists. Complex setups (especially the app creation flow) need numbered step sequences or checkboxes, not just bullets. +3 points

4. No table of contents. At 744 lines, you need a TOC at the top so people can jump to sections. +2 points

Quick Wins

• Split into references for PDA compliance (+15 pts)
• Add verification steps and troubleshooting (+3 pts)
• Replace "your-" placeholders with <angle-brackets> (+2 pts)
• Add workflow checklists for complex processes (+3 pts)

Hit these and you're looking at D → B territory pretty easily. The content is solid; it just needs to be packaged more efficiently.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that installs skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.