Agent skill · operations · jeremylongshore
flexport-incident-runbook
Analyze, contain, and reconcile a Flexport integration incident without unsafe retries or invented webhook replay APIs. Use when events stop, payload parsing fails, credentials break, or mutation outcomes are uncertain. Trigger with: "Flexport incident", "missing Flexport events", "reconcile Flexport outage".
Why this skill is useful
Provides specific diagnostic scripts and incident response procedures for Flexport API outages that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, grep, jq installed locally. Requires flexport account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Flexport Delivery-Gap Incident Runbook Overview Preserve freight correctness first. Freeze uncertain mutations, separate provider delivery from local processing, and reconstruct affected state with documented resource/event reads. Prerequisites Incident owner, severity, start time, and affected tenant/workflow Last known good release and configuration Bounded reconciliation query and business owners for disputed state Instructions Step 1: Contain Disable automatic bookings and affected writes. Keep authenticated webhook acceptance only if durable enqueue and deduplication remain correct. Step 2: Bound the window Identify first/last bad receipt by surface, operation, release, credential alias, and version without examining broad sensitive payloads. Step 3: Split failure domains Test OAuth, REST read, MCP connection, webhook ingress, queue processing, and downstream state independently. Step 4: Reconcile read-only Use /events or affected resource reads to compare provider state with durable local operation keys. Do not assume Flexport exposes a webhook replay endpoint. Step 5: Repair deterministically Reprocess authenticated durable events or apply approved state corrections exactly once; reconcile uncertain creates/bookings before retry. Step 6: Recover and learn Restore traffic by cohort, verify the full incident window, rotate exposed credentials if needed, and add a sanitized regression fixture. Authentication REST calls authenticate with a cached OAuth 2.0 client-credentials Bearer token using audience https://api.flexport.com, or an explicitly accepted broad API key. Use distinct credentials per workload and never log credentials or tokens. MCP calls use the authenticated connection to https://mcp.flexport.com/mcp and remain subject to each tool's documented account permissions. Tool Discipline Use Read and Grep for discovery and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flexport-incident-runbook