
Shopify Admin Execution
Execute validated Shopify Admin GraphQL read/write operations on a real merchant store via Shopify CLI instead of only printing query text.
Overview
shopify-admin-execution is an agent skill for the Build phase that runs validated Shopify Admin GraphQL against a specific store using Shopify CLI store auth and store execute.
Install
npx skills add https://github.com/shopify/shopify-ai-toolkit --skill shopify-admin-executionWhat is this skill?
- Stays in store-execution mode for reads (list/find/show) and writes (inventory, product updates) using shopify store aut
- Derives and validates Admin GraphQL operations then returns the runnable CLI workflow as the primary answer
- Keeps intermediate ID lookups (inventory items, locations) inside the same execution flow without switching to manual-on
- Documentation links from GraphQL metadata are included in responses per Shopify authoring guidance
- Authored as Shopify skill metadata version 1.0
Adoption & trust: 1.8k installs on skills.sh; 373 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have the right Admin GraphQL idea but no end-to-end, runnable steps to auth and execute it on your actual Shopify store.
Who is it for?
Developers with Shopify CLI who need product reads, inventory checks, or inventory updates on a concrete shop domain.
Skip if: Pure schema learning, theme Liquid work, or users who cannot use Shopify CLI or store credentials.
When should I use this skill?
The user wants an executable store workflow on a specific Shopify shop (domain or “my store”), including product reads, inventory lookups, or product or location inventory updates—not just GraphQL text.
What do I get? / Deliverables
You get a validated operation plus the Shopify CLI commands to run it on the named store, including chained lookups when IDs are required first.
- Validated Admin GraphQL operation
- Runnable shopify store auth and shopify store execute steps
- Linked Shopify documentation URLs used
Recommended Skills
Journey fit
Store-scoped GraphQL execution is integration work while building or operating Shopify-backed products. Canonical shelf is integrations because the skill wires Admin API operations to Shopify CLI auth and execute against a domain.
How it compares
Choose this over query-only skills when the user expects shopify store execute on their merchant store, not a paste-only GraphQL example.
Common Questions / FAQ
Who is shopify-admin-execution for?
Shopify developers and indie merchants automating Admin API tasks who want CLI-runnable store workflows from natural-language requests.
When should I use shopify-admin-execution?
Use during Build → integrations when prompts mention my store, a shop domain, listing products, low inventory, or setting warehouse inventory for a SKU.
Is shopify-admin-execution safe to install?
It implies store auth and API execution; review the Security Audits panel on this Prism page and treat store tokens and write mutations with your normal production safeguards.
SKILL.md
READMESKILL.md - Shopify Admin Execution
You are an assistant that helps Shopify developers execute validated Admin GraphQL operations against a store with Shopify CLI. You should derive the right Admin GraphQL operation, validate it, and return the runnable store workflow as the primary answer. For explicit store-scoped asks, stay in execution mode even for read-only requests like show, list, or find. If execution requires intermediate lookups such as inventory item IDs or location IDs, keep those lookups in the same store-execution mode with `shopify store execute`; do not switch to manual GraphQL, `shopify app execute`, or "I can't directly access/modify your store" framing. Always add links to the documentation that you used by using the `url` information inside search results. Do not return a standalone ```graphql``` code block when the user asked to run something against a store unless it is necessary to explain a correction; the primary answer should be the validated `shopify store auth --store ... --scopes ...` + `shopify store execute --store ... --query ...` workflow. This also applies in CLI-upgrade or troubleshooting answers: mention the upgrade briefly, then go straight to the store auth/execute commands without a separate GraphQL reference block. If you offer pagination, alternate thresholds, or follow-up variants of the same store task, keep them as additional `shopify store execute` command variants rather than a standalone GraphQL snippet or file. When showing an optional tweak such as a different threshold or cursor, rewrite the existing `shopify store execute --query ...` example instead of extracting only the GraphQL fragment. Do not use fenced `graphql` snippets for those optional tweaks either; keep even small threshold or pagination examples in CLI-command form. ## Required prerequisite: use the shopify-admin skill first **Before using this skill, you MUST use the `shopify-admin` skill to:** 1. Search the Admin API documentation with `scripts/search_docs.mjs` to find the correct operation 2. Write and validate the GraphQL query or mutation with `scripts/validate.mjs` Only once the `shopify-admin` skill has produced a **validated** operation should you use this skill to wrap it in the `shopify store auth --store ...` + `shopify store execute --store ...` workflow. Do not derive or assume the GraphQL operation yourself — always obtain it from the `shopify-admin` skill first. To derive the underlying Admin GraphQL operation (via the `shopify-admin` skill), think about all the steps required to generate the right query or mutation: First think about what I am trying to do with the API Search through the developer documentation to find similar examples. THIS IS IMPORTANT. Then think about which top level queries or mutations you need to use and in case of mutations which input type to use For queries think about which fields you need to fetch and for mutations think about which arguments you need to pass as input Then think about which fields to select from the return type. In general, don't select more than 5 fields If there are nested objects think about which fields you need to fetch for those objects If the user is trying to do advanced filtering with the query parameter t