From shopify-admin-skills
Generates daily fulfillment triage digest of Shopify open orders segmented by age buckets and flagging holds or exceptions via GraphQL queries. Replaces manual admin review for ops teams.
npx claudepluginhub 40rty-ai/shopify-admin-skills --plugin shopify-admin-skillsThis skill uses the workspace's default tool permissions.
Produces a daily ops triage digest of all unfulfilled and partially-fulfilled orders, segmented by how long they've been waiting. Flags orders with active holds. Replaces the manual process of scrolling through the Shopify admin Orders page to find aging orders and exceptions — this skill fetches every open order, computes its age, buckets it into configurable time segments, and surfaces any or...
Generates bulk reports of Shopify orders at risk of WISMO support tickets: shipped with stale tracking and unfulfilled past SLA window, via GraphQL queries.
Manages Shopify orders, customers, and fulfillments via GraphQL Admin API. Query orders, process fulfillments, handle customer records, create draft orders.
Guides Shopify order management via GraphQL: lifecycle, FulfillmentOrder, returns/refunds, draft orders, editing, transactions, metafields, risk analysis.
Share bugs, ideas, or general feedback.
Produces a daily ops triage digest of all unfulfilled and partially-fulfilled orders, segmented by how long they've been waiting. Flags orders with active holds. Replaces the manual process of scrolling through the Shopify admin Orders page to find aging orders and exceptions — this skill fetches every open order, computes its age, buckets it into configurable time segments, and surfaces any orders currently on a fulfillment hold, giving the ops team a complete exception queue in a single read-only operation.
shopify auth login --store <domain>read_orders| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| store | string | yes | — | Store domain (e.g., mystore.myshopify.com) |
| format | string | no | human | Output format: human or json |
| dry_run | bool | no | false | Preview operations without executing mutations |
| aging_thresholds_days | array | no | [1, 3, 7] | Day boundaries for age buckets (e.g., [1,3,7] creates: 0–1d, 1–3d, 3–7d, 7d+) |
| include_holds | bool | no | true | Include orders with active fulfillment holds in a separate section |
| limit | integer | no | 250 | Maximum orders to fetch per page |
OPERATION: orders — query
Inputs: first: <limit>, query: "fulfillment_status:unfulfilled OR fulfillment_status:partial", sort by CREATED_AT ascending (oldest first), paginate until complete
Expected output: All open orders with createdAt, name, displayFulfillmentStatus; compute age = now − createdAt in days; bucket into aging_thresholds_days segments
OPERATION: fulfillmentOrders — query (via nested order.fulfillmentOrders)
Inputs: For each order from Step 1: fulfillmentOrders(first: 5) to check status and requestStatus; flag any with status: ON_HOLD
Expected output: Hold status per order, holdUntil if set; contribute to the Holds section of the digest
# orders:query — validated against api_version 2025-01
query FulfillmentStatusDigest($first: Int!, $after: String, $query: String) {
orders(first: $first, after: $after, query: $query, sortKey: CREATED_AT) {
edges {
node {
id
name
createdAt
displayFulfillmentStatus
displayFinancialStatus
totalPriceSet {
shopMoney { amount currencyCode }
}
customer {
id
firstName
lastName
}
fulfillmentOrders(first: 5) {
edges {
node {
id
status
requestStatus
fulfillAt
}
}
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}
Note: fulfillmentOrders is a nested field on the Order type — the fulfillmentOrders:query frontmatter entry documents that this operation accesses fulfillment order data.
Claude MUST emit the following output at each stage. This is mandatory.
On start, emit:
╔══════════════════════════════════════════════╗
║ SKILL: fulfillment-status-digest ║
║ 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):
══════════════════════════════════════════════
OUTCOME SUMMARY
Total open orders: <n>
By age bucket (0-1d): <n>
By age bucket (1-3d): <n>
By age bucket (3-7d): <n>
By age bucket (7d+): <n>
Orders on hold: <n>
Errors: 0
Output: none
══════════════════════════════════════════════
For format: json, emit:
{
"skill": "fulfillment-status-digest",
"store": "<domain>",
"started_at": "<ISO8601>",
"completed_at": "<ISO8601>",
"dry_run": false,
"steps": [
{ "step": 1, "operation": "FulfillmentStatusDigest", "type": "query", "params_summary": "limit: <n>, query: fulfillment_status:unfulfilled OR partial", "result_summary": "<n> orders fetched", "skipped": false },
{ "step": 2, "operation": "fulfillmentOrders", "type": "query", "params_summary": "nested per order, first: 5", "result_summary": "<n> orders on hold", "skipped": false }
],
"outcome": {
"total_open_orders": 0,
"buckets": [
{ "label": "0-1d", "count": 0 },
{ "label": "1-3d", "count": 0 },
{ "label": "3-7d", "count": 0 },
{ "label": "7d+", "count": 0 }
],
"orders_on_hold": 0,
"errors": 0,
"output_file": null
}
}
Fulfillment Age Digest — <store> — <date>
| Age Bucket | Order Count | Oldest Order |
|---|---|---|
| 0–1 days | n | #XXXX |
| 1–3 days | n | #XXXX |
| 3–7 days | n | #XXXX |
| 7+ days | n | #XXXX (⚠️ review) |
Orders On Hold (if include_holds: true and holds exist):
| Order | Hold Since | Fulfillment Status |
|---|---|---|
| #XXXX | 3 days | ON_HOLD |
| Error | Cause | Recovery |
|---|---|---|
| No orders returned | No open orders in system | Store is fully fulfilled — no action needed |
fulfillmentOrders returns empty | Order has no fulfillment assignments yet | Order may not have been assigned to a location |
| Rate limit (429) | Large order volume with pagination | Reduce limit to 100 |
format: json to pipe the digest into a Slack notification or dashboard script.order-hold-and-release to act on exceptions identified in this digest without leaving the CLI.limit: 100 and expect pagination — the digest will still aggregate correctly across all pages.