Agent skill · software engineering · jeremylongshore
navan-prod-checklist
Audit whether a Navan integration is ready for production using evidence and rollback criteria. Use when preparing to enable a live API, transfer, identity, or finance workflow. Trigger with "ship Navan integration", "Navan go-live", or "Navan production checklist".
Why this skill is useful
Adds executable scripts for validating production readiness and compliance for Navan API integrations that are not publicly documented.
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 Production Readiness Gate Overview Audit whether a Navan integration is ready for production using evidence and rollback criteria. 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 Production readiness binds one documented tenant contract to one identity, destination, data purpose, operating window, and rollback plan. A successful sandbox or fixture test is necessary but not sufficient. Authentication Confirm production credential provenance, least privilege, rotation, revocation, host binding, break-glass ownership, and separation from non-production. Instructions 1. Freeze the approved contract revision and change scope. 2. Review security, privacy, retention, accounting, and traveler-impact controls. 3. Prove offline tests, non-production smoke, reconciliation, monitoring, and alert routing. 4. Define canary scope, success thresholds, stop conditions, and rollback owner. 5. Verify runbooks for credential, schema, vendor, destination, and data incidents. 6. Collect named approvals and record the exact release receipt. 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 Require service, Navan admin, security, data, and finance owners as applicable; no checklist completion can self-authorize production writes or traveler impact. Error Handling A missing owner or rollback signal is a no-go. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-prod-checklist