Agent skill · data analytics · jeremylongshore
navan-common-errors
Triage Navan integration failures without exposing travel or payment data or applying blind retries. Use when a contracted API, SFTP, SCIM, or direct integration fails. Trigger with "Navan error", "Navan sync failed", or "debug Navan integration".
Why this skill is useful
Provides specific diagnostic commands and procedures for resolving Navan API errors 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 Contract Failure Triage Overview Triage Navan integration failures without exposing travel or payment data or applying blind retries. 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 Classify failures by layer: local configuration, identity, tenant enablement, contract/schema, transport, vendor availability, destination, or reconciliation. Status codes alone do not establish safe retry behavior. Authentication Never ask for or reproduce credentials. Confirm only secret presence, source, age, scope label, target host, and last rotation using content-free evidence. Instructions 1. Freeze retries and preserve the first sanitized failure receipt. 2. Identify tenant, environment, surface, operation, and contract revision. 3. Check configuration and identity metadata without printing values. 4. Compare request and response envelopes against fixtures using redacted structure only. 5. Check Navan status and destination health before attributing cause. 6. Select retry, reconcile, credential rotation, contract update, or escalation with an owner. 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 Replays, secret rotation, backfills, file retransmission, traveler-data inspection, and write retries require explicit approval and an impact bound. Error Handling Do not retry a possibly accepted write without idempotency evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-common-errors