shopify-yourskilllisted

Use when [the specific situations, symptoms, and phrases someone would type or think when they hit this problem]. Pack real trigger words and store-owner symptoms. Describe ONLY when to use it, never summarize the workflow inside. Keep the whole frontmatter under 1024 characters. End by naming what this skill is NOT for, pointing at the sibling skill that covers it.
kgelster/awesome-ecom-skills · ★ 47 · Data & Documents · score 81

Install: claude install-skill kgelster/awesome-ecom-skills

# Shopify Yourskill One or two sentences: what this skill covers and the core principle. Cross- reference sibling skills by name when a task belongs to one of them, rather than repeating their content. ## Guidelines for a good ecom skill Delete this section in your real skill; it's guidance for authoring. - **Name:** `shopify-<area>` (or `ecom-<area>` for platform-neutral skills), lowercase and hyphens only. The directory name MUST equal the frontmatter `name`. - **Description:** starts with "Use when…", lists concrete triggers and keywords, ends with a "not for X, use Y" pointer. No workflow summary: an agent follows the description to decide whether to load the body. - **Original prose only.** Do not paste from shopify.dev, the Matrixify docs, or any other source; write the lesson in your own words and link the canonical doc. Ship the institutional knowledge agency work teaches that the docs don't. - **Body 100–200 lines; heavy detail in `references/*.md`.** No `scripts/` directory: this collection is markdown-only (see recipes doctrine below). - Every SKILL.md ends with a **Provenance and maintenance** section. ## Store access Every skill that touches the Admin API opens with this stanza (paste it, adjust the scopes line to this skill's minimum). Two lanes; pick one. **Lane A: custom-app token (scriptable).** In Shopify admin: Settings → Apps and sales channels → Develop apps → create an app → grant the minimum scopes this skill needs, then install and