Agent skill · marketing growth · jeremylongshore
notion-incident-runbook
Analyze and coordinate a Notion integration incident with bounded mitigation, evidence custody, communications, and recovery verification. Use when availability, correctness, privacy, or credential safety is at risk. Trigger with "run Notion incident", "triage Notion outage", or "contain Notion sync failure".
Why this skill is useful
Adds automated triage scripts and decision trees for Notion API incidents that are not publicly documented.
What it needs
Requires curl, jq installed locally. Requires notion account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Notion Integration Incident Command Overview Analyze and coordinate a Notion integration incident with bounded mitigation, evidence custody, communications, and recovery verification.. This workflow produces an auditable decision or artifact before any live action. Prerequisites Current first-party Notion documentation and the selected integration's tested API-version contract. A named workspace owner, content or data owner, and operation owner. Synthetic or approved non-production fixtures with secrets and workspace content removed. Current Contract Separate Notion service health, authentication, access, version shape, application defects, queues, downstream systems, and data correctness. Availability recovery does not prove data reconciliation. Recheck the dated evidence map before relying on mutable fields, endpoints, versions, limits, or delivery behavior. Authentication If compromise is suspected, freeze token use and follow the approved secret-rotation lane; never expose credentials in the incident channel. Instructions 1. Name the incident commander, severity, affected tenants, operations, data classes, and start time. 2. Freeze unsafe writes and retries while preserving queue, cursor, request-ID, and deployment evidence. 3. Classify the fault domain and compare official status with application telemetry. 4. Choose the smallest reversible mitigation with an owner and rollback trigger. 5. Restore service in stages, then reconcile pages, cursors, webhook signals, duplicates, and missed work. 6. Close only after security, data correctness, communications, and follow-up ownership are evidenced. Tool Discipline Use Read, Glob, and Grep to inspect documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, workspace content, user data, file transfer, deployment, capability or sharing changes, writes, spend, or deletion. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/notion-incident-runbook--f59ab3