shopify-admin-agentic-…
Edit the theme's robots.txt.liquid to explicitly allow AI crawlers (GPTBot, ClaudeBot,…
Read-only: for native bundle products and metafield-defined bundles, verifies every component variant has sufficient stock to fulfill the bundle's effective availability.
$ npx -y skills add 40rty-ai/shopify-admin-skills --skill shopify-admin-bundle-availability-check --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/shopify-admin-bundle-availability-checkContext preview
The summary Claude sees to decide when to auto-load this skill.
Read-only: for native bundle products and metafield-defined bundles, verifies every component variant has sufficient stock to fulfill the bundle's effective availability.
name: shopify-admin-bundle-availability-check role: fulfillment-ops description: "Read-only: for native bundle products and metafield-defined bundles, verifies every component variant has sufficient stock to fulfill the bundle's effective availability." toolkit: shopify-admin, shopify-admin-execution api_version: "2025-01" graphql_operations: - products:query - productVariants:query - inventoryItems:query status: stable compatibility: Claude Code, Cursor, Codex, Gemini CLI
Walks every product flagged as a bundle (either via Shopify's native `requiresComponents` mechanic or a `bundle.components` metafield convention), then verifies each component variant has sufficient inventory to back the bundle's quantity ratio. Surfaces bundles that are listed as in-stock on the storefront but cannot actually be fulfilled because one component has run out. Read-only — no mutations.
| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | metafield_namespace | string | no | bundle | Metafield namespace where bundle component definitions live | | metafield_key | string | no | components | Metafield key that holds the JSON list of `{variantId, quantity}` | | safety_stock | integer | no | 0 | Treat component as out-of-stock if on-hand minus this buffer is below required | | only_listed | bool | no | true | Only check bundle products with status `ACTIVE` | | format | string | no | human | Output format: `human` or `json` |
> ℹ️ Read-only skill — no mutations are executed. Safe to run at any time. The skill reads inventory and metafields only; it never adjusts component quantities or bundle availability.
1. **OPERATION:** `products` — query **Inputs:** `first: 250`, `query: "metafield:<namespace>.<key>:* OR product_type:bundle"`, select `requiresSellingPlan`, `status`, `metafield(namespace, key)`, `variants`, pagination cursor **Expected output:** Bundle products and their parent variants; paginate until `hasNextPage: false`
2. For each bundle, parse component list. Native bundles use `productVariant.requiresComponents` and `productVariant.productVariantComponents`. Metafield bundles parse JSON value into `[{variantId, quantity}]`.
3. **OPERATION:** `productVariants` — query **Inputs:** Batched IDs of all unique component variants, select `inventoryQuantity`, `inventoryItem { id }`, `product { title }` **Expected output:** On-hand quantity per component
4. **OPERATION:** `inventoryItems` — query **Inputs:** Batched component inventory item IDs, select `tracked`, `inventoryLevels(first: 25) { quantities }` **Expected output:** Per-location quantity for each component
5. For each bundle, compute `max_buildable_units = floor(min over components of (component_on_hand - safety_stock) / required_qty)`. Flag bundles where `max_buildable_units == 0` (broken bundle) or `< min_listed_inventory_threshold`.
# products:query — validated against api_version 2025-01
query BundleProducts($query: String!, $after: String, $namespace: String!, $key: String!) {
products(first: 250, after: $after, query: $query) {
edges {
node {
id
title
status
productType
metafield(namespace: $namespace, key: $key) {
id
value
type
}
variants(first: 100) {
edges {
node {
id
title
sku
inventoryQuantity
requiresComponents
productVariantComponents(first: 50) {
edges {
node {
quantity
productVariant {
id
sku
inventoryQuantity
product {
id
title
}
}
}
}
}
}
}
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}# productVariants:query — validated against api_version 2025-01
query ComponentVariantStock($ids: [ID!]!) {
nodes(ids: $ids) {
... on ProductVariant {
id
sku
inventoryQuantity
product {
id
title
}
inventoryItem {
id
tracked
}
}
}
}# inventoryItems:query — validated against api_version 2025-01
query ComponentInventoryLevels($ids: [ID!]!) {
nodes(ids: $ids) {
... on InventoryItem {
id
tracked
inventoryLevels(first: 25) {
edges {
node {
location {
id
name
}
quantities(names: ["available", "on_hand", "committed"]) {
name
quantity
}
}
}
}
}
}
}**Claude MUST emit the following output at each stage. This is mandatory.**
**On start**, emit:
╔══════════════════════════════════════════════╗ ║ SKILL: Bundle Availability Check ║ ║ Store: <store domain> ║ ║ Started: <YYYY-MM-DD HH:MM UTC> ║ ╚══════════════════════════════════════════════╝
**After each step**, emit:
[N/TOTAL] <QUERY|MUTATION> <OperationName>
→ Params: <brief summary of key inputs>
→ Result: <count or outcome>**On completion**, emit:
For `format: human` (default):
══════════════════════════════════════════════ BUNDLE AVAILABILITY CHECK Bundles inspected: <n> Fully buildable: <n> Cons
Community-maintained AI agent skills for operating Shopify stores — workflows, optimization, reports and more
Edit the theme's robots.txt.liquid to explicitly allow AI crawlers (GPTBot, ClaudeBot,…
Rewrite thin product descriptions into structured, fact-rich copy (materials, fit, use-cases,…
Generate and set descriptive alt text on product images so AI agents (which can't 'see'…
Generate and publish an /llms.txt guide (brand summary, flagship products, key policies,…
Define and populate agentic-commerce metafields (material, attributes, key features, specs,…
Inject an Organization JSON-LD block (name, logo, sameAs social links, contactPoint) into the…