Workflow·Finance & Commerce·v2.7.0

Shopify Incident Runbook

Execute Shopify incident response with triage using Shopify status page,.

You say
Buy it · $35 Read it before you buy $35 Written by jeremylongshore · unverified publisher
Context cost
1.9k tokensestimated from the bundle, loaded when it triggers
Bundle
3 files · 7.7 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
v2.7.0
Servers it uses
Noneruns standalone

What it does

Execute Shopify incident response with triage using Shopify status page,

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

e-commerceshopify

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.5 kB · 139 lines
--- name: shopify-incident-runbook description: 'Execute Shopify incident response with triage using Shopify status page, API health checks, and rate limit diagnosis. Use when a Shopify integration is down, returning errors, or behaving unexpectedly in production. Trigger with phrases like "shopify incident", "shopify outage", "shopify down", "shopify on-call", "shopify emergency", "shopify not responding". ' allowed-tools: Read, Grep, Bash(curl:*) version: 2.7.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: - saas - ecommerce - shopify compatibility: Designed for Claude Code ---
25# Shopify Incident Runbook
26
27## Overview
28
29Rapid incident response for Shopify API outages, authentication failures, and rate limit emergencies. Distinguish between Shopify-side issues and your app's integration issues.
30
31## Prerequisites
32
33- Access to Shopify admin and status page
34- Application logs and metrics
35- Communication channels (Slack, PagerDuty)
36
37## Instructions
38
39### Step 1: Quick Triage (First 5 Minutes)
40
41Run the triage script to check Shopify status, API connectivity, REST rate limits, and GraphQL throttle state in one pass.
42
43See [Triage Script](references/triage-script.md) for the complete diagnostic script.
44
45### Step 2: Decision Tree
46
47```
48Is Shopifystatus.com showing an incident?
49├── YES → Shopify-side outage
50│ ├── Enable graceful degradation / cached responses
51│ ├── Notify stakeholders: "Shopify is experiencing issues"
52│ └── Monitor status page for resolution
53
54└── NO → Likely your integration
55 ├── HTTP 401? → Token expired or revoked
56 │ └── Check: Was app reinstalled? Rotate token.
57 ├── HTTP 403? → Scope missing
58 │ └── Check: Were scopes changed? Re-run OAuth.
59 ├── HTTP 429 / THROTTLED? → Rate limit exceeded
60 │ └── Check: Runaway loop? Reduce query frequency.
61 ├── HTTP 5xx? → Intermittent Shopify issue
62 │ └── Retry with backoff, monitor for pattern.
63 └── Network timeout? → Infrastructure issue
64 └── Check: DNS, firewall, TLS certificates.
65```
66
67### Step 3: Immediate Actions by Error Type
68
69Diagnostic commands and remediation for 401 (token expired), 429 (rate limited), and 5xx (Shopify internal errors). Always capture X-Request-Id headers for Shopify support.
70
71See [Error Type Actions](references/error-type-actions.md) for complete commands per error type.
72
73### Step 4: Communication Templates
74
75**Internal (Slack):**
76
77```
78INCIDENT: Shopify Integration Issue
79Severity: P[1/2/3]
80Status: INVESTIGATING
81Impact: [What users/merchants are affected]
82Root cause: [Shopify outage / Our auth issue / Rate limiting]
83Action: [What we're doing now]
84Next update: [Time]
85Responder: @[name]
86```
87
88**External (Merchant-facing):**
89
90```
91We're currently experiencing issues with some Shopify-connected features.
92[Order sync / Product updates / etc.] may be delayed.
93We're actively working on resolution and will update shortly.
94All data is safe — no orders or products have been lost.
95```
96
97## Output
98
99- Triage completed within 5 minutes
100- Root cause identified (Shopify vs. integration)
101- Immediate mitigation applied
102- Stakeholders notified
103
104## Error Handling
105
106| Scenario | Response Time | Escalation |
107|----------|--------------|------------|
108| Shopify API fully down | Monitor status page | Nothing to fix on our side |
109| Auth token revoked | < 15 min | Trigger re-auth, notify merchant |
110| Rate limit exhaustion | < 30 min | Reduce query frequency, optimize costs |
111| Webhook delivery failures | < 1 hour | Check endpoint health, review HMAC |
112| Data sync stalled | < 4 hours | Run manual sync after resolution |
113
114## Examples
115
116### One-Liner Health Check
117
118```bash
119curl -sf -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
120 "https://$SHOPIFY_STORE/admin/api/${SHOPIFY_API_VERSION:-2025-04}/shop.json" \
121 | jq '{name: .shop.name, plan: .shop.plan_name}' \
122 && echo "SHOPIFY: HEALTHY" || echo "SHOPIFY: UNREACHABLE"
123```
124
125### Post-Incident Checklist
126
127- [ ] Timeline documented with UTC timestamps
128- [ ] Root cause identified
129- [ ] X-Request-Id values collected (for Shopify support)
130- [ ] Customer impact assessed
131- [ ] Prevention action items created
132- [ ] Monitoring/alerting gaps identified
133
134## Resources
135
136- [Shopify Status Page](https://www.shopifystatus.com)
137- [Shopify Partner Support](https://help.shopify.com/en/partners)
138- [Shopify Community Forums](https://community.shopify.dev)
139
In the file
SKILL.md612 words
Files3
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈160
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,765
on trigger
The instruction body and 2 supporting files, read only when the skill fires.
0.96%
of a 200k window
Ten skills this size would take about 10% of the window before you open a file.
050k100k150k200k context window

1.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

3 files, 7.7 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md4.5 kB
  • references/error-type-actions.md1.3 kB
  • references/triage-script.md1.9 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 3 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$35 once
Shopify Incident Runbook · MIT · jeremylongshore
one-time
Price$35 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 2.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version2.7.0
Publishedno release date on file
Price$35
Referencejeremylongshore/shopify-incident-runbook

Versions

v2.7.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v2.7.0
  • No earlier releases have been published to the marketplace.
Pinning

Put jeremylongshore/shopify-incident-runbook@2.7.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

JE
jeremylongshore

Publishes on mcprush.

0 servers listed6 skills listednot claimed
Profile
Publisher
Servers0