Agent skill · software engineering · jeremylongshore
navan-local-dev-loop
Develop Navan integrations against sanitized contract fixtures with networking denied by default. Use when changing adapters, mappings, or reconciliation logic. Trigger with "develop Navan locally", "mock Navan data", or "add Navan fixtures".
Why this skill is useful
Adds executable scripts for setting up a local development environment with token caching and request logging for Navan API integrations.
What it needs
Requires node 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 Offline Development Loop Overview Develop Navan integrations against sanitized contract fixtures with networking denied by default. 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 Local development should exercise the application-owned contract, not depend on a live tenant. Fixtures must preserve structural edge cases while removing traveler, payment, itinerary, and credential data. Authentication Local tests require no Navan credential. An optional live smoke uses a separate non-production secret and must be explicitly enabled outside the normal test command. Instructions 1. Capture a schema from authorized documentation or a sanitized response. 2. Build minimal success, empty, paginated, corrected, denied, throttled, and malformed fixtures. 3. Validate fixtures against local types and sensitivity rules. 4. Run the adapter with networking blocked and a deterministic clock. 5. Exercise mapping, deduplication, checkpoint, and rollback behavior. 6. Keep live smoke configuration separate, bounded, and disabled by default. 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 Live tenant access, new fixtures derived from real data, dependency changes, and fixture publication require explicit approval. Error Handling Never commit raw tenant responses. A fixture that contains plausible personal data still needs review. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-local-dev-loop