Agent skill · software engineering · jeremylongshore

navan-debug-bundle

Assemble a content-free Navan integration support bundle for operators or vendor escalation. Use when triage needs reproducible evidence. Trigger with "collect Navan diagnostics", "Navan support bundle", or "sanitize Navan logs".

Why this skill is useful

Adds executable scripts for collecting and packaging diagnostic data from the Navan API, which are not available in public documentation.

What it needs

Requires curl, jq, tar 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 Sanitized Support Bundle Overview Assemble a content-free Navan integration support bundle for operators or vendor escalation. 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 A useful bundle proves configuration shape, contract revision, timing, counts, checksums, and failure class without containing credentials, traveler identity, itinerary, payment, receipt, or free-text content. Authentication Record credential source, age band, and scope label only. Never include tokens, client secrets, cookies, file-transfer keys, authorization headers, or raw identity responses. Instructions 1. Define the incident window and minimum evidence questions. 2. Collect version, tenant alias, environment, surface, operation, and contract revision. 3. Add redacted request/response schemas, counts, timings, status class, and correlation identifiers. 4. Hash artifacts and scan them for credentials and sensitive fields. 5. Generate a manifest showing every included and excluded item. 6. Require review before transmitting the bundle outside the approved boundary. 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 Reading local sanitized evidence is allowed; collecting live data or sending any bundle to Navan or another party requires data-owner and incident-owner approval. Error Handling Do not solve redaction by replacing only obvious email addresses. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/navan-debug-bundle

View the source on GitHub

Browse the @skills marketplace