Agent skill · marketing growth · jeremylongshore
navan-incident-runbook
Manage containment, reconciliation, and recovery for a Navan integration incident. Use when handling credential, privacy, booking, expense, identity, or delivery failures. Trigger with "Navan incident", "Navan outage", or "Navan data exposure".
Why this skill is useful
Provides specific API commands and incident response procedures for the Navan platform that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq installed locally. Requires navan account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Navan Integration Incident Command Overview Manage containment, reconciliation, and recovery for a Navan integration incident. This workflow produces an auditable decision or artifact before any live action. Prerequisites Access to the selected tenant's current Navan Help Center and contracted integration documentation. A named business owner and data owner for the travel or expense workflow. A non-production evidence set with secrets and traveler data removed. Current Contract The source of truth spans Navan, the integration, and downstream systems. Recovery is incomplete until credentials, data windows, financial totals, traveler impact, and destination acknowledgements are reconciled. Authentication Use break-glass access only under the documented incident process. Never paste tokens or traveler data into chat, tickets, status updates, or unapproved AI tools. Instructions 1. Declare commander, scope, severity, timeline, and communication boundary. 2. Contain schedules, writes, transfers, credentials, or destinations without erasing evidence. 3. Preserve sanitized logs, checkpoints, schemas, counts, hashes, and approvals. 4. Determine source, destination, traveler, privacy, security, and finance impact. 5. Reconcile the affected window before replay or reopening writes. 6. Recover gradually, monitor, close temporary access, and assign follow-ups. Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. Approval Boundaries Credential rotation, replay, backfill, write enablement, customer communication, legal notification, and evidence sharing require the authorized incident roles. Error Handling Containment comes before reproduction. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-incident-runbook