Agent skill · operations · jeremylongshore
salesforce-incident-runbook
Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention. Use when handling service or data incidents. Trigger with "respond to Salesforce incident".
Why this skill is useful
Adds specific incident response procedures and executable scripts for Salesforce outages that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq, salesforce-cli installed locally. Requires salesforce account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Salesforce Integration Incident Response Overview Restore business invariants safely by separating Salesforce platform state, customer org state, application behavior, data correctness, and event delivery. Prerequisites Incident commander, severity model, affected environments and workloads, communications, and evidence channel Current deployment, org identity, app and principal, API, limits, jobs, events, data, and reconciliation contracts Pre-approved containment, failover, deferral, rollback, credential revocation, and vendor escalation procedures Tool Discipline Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts. Current Contract Salesforce Status reports platform incidents, while org-specific authorization, limits, metadata, automation, jobs, events, and data can fail independently. A green platform status does not prove an integration or business invariant is healthy. Authentication Use read-only incident access first and separate break-glass access under the customer process. Never paste tokens, sessions, private keys, raw records, or unrestricted logs into tickets or chat. Instructions 1. Declare severity, commander, time window, affected orgs and workloads, business invariant, data risk, and communication cadence. 2. Freeze deployments and unsafe retries; preserve request, job, event, deployment, and reconciliation identifiers. 3. Check Salesforce Status, org identity, authorization, API support, limits, metadata, automation, async jobs, event flow, and application telemetry. 4. Classify platform, org, identity, permission, schema, capacity, code, dependency, data, or consumer failure and bound impact. 5. Select the least-destructive approved containment such as pausing intake, deferring work, isolating a consumer, rollback, or credential revocation. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/salesforce-incident-runbook