Agent skill · marketing growth · jeremylongshore
maintainx-incident-runbook
Manage incident response for MaintainX integration failures.
Why this skill is useful
Provides detailed incident response procedures and executable scripts for handling MaintainX integration failures that the AI wouldn't generate on its own.
What it needs
Requires jq installed locally. Requires maintainx account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
MaintainX Incident Runbook Overview Step-by-step procedures for responding to MaintainX integration incidents, from detection through resolution and post-mortem. Prerequisites Access to monitoring dashboards MaintainX admin API credentials On-call contact list Severity Classification Severity Definition Response Time ---------- ----------- --------------- SEV-1 Complete integration failure, no work orders processing 15 min SEV-2 Partial failure, some endpoints degraded 1 hour SEV-3 Performance degradation, slow responses 4 hours SEV-4 Non-critical feature broken, workaround available Next business day Instructions Step 1: Immediate Triage (First 5 Minutes) Step 2: Determine Root Cause Symptom Likely Cause Check --------- ------------- ------- All endpoints return 401 API key expired echo ${#MAINTAINXAPIKEY} and test with curl All endpoints return 5xx MaintainX platform outage Check status.getmaintainx.com 429 on all requests Rate limit exceeded Review request volume in last hour Specific endpoint 404 API path changed Check MaintainX changelog Timeouts Network issue curl -w "Total: %timetotal seconds" ... Your service crashes Application error Check container logs, OOM, disk space Step 3: Apply Mitigation API Key Expired (SEV-1): Rate Limited (SEV-2): MaintainX Platform Outage (SEV-1): Step 4: Verify Resolution Step 5: Post-Incident Documentation Output Incident triaged and severity classified Root cause identified using diagnostic steps Mitigation applied (key rotation, rate reduction, or request buffering) Recovery verified with health checks and data flow validation Post-incident report documented Error Handling Scenario Immediate Action ---------- ----------------- Total API failure Buffer requests, check status page, escalate Intermittent 500s Enable retry logic, reduce request rate Data sync gap Note gap window, schedule backfill after recovery Webhook delivery failure Fall back to polling, queue missed events Resources MaintainX Status Page MaintainX API Refer …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/maintainx-incident-runbook