Agent skill · software engineering · jeremylongshore
navan-sdk-patterns
Design an application-owned Navan adapter pinned to the tenant's actual integration contract. Use when wrapping Booking API, Expense API, SFTP, or direct integration behavior. Trigger with "build a Navan client", "wrap Navan API", or "type Navan responses".
Why this skill is useful
Adds a complete TypeScript API wrapper for Navan's REST endpoints, including token management and error handling, which the AI cannot generate from existing knowledge.
What it needs
Requires dotenv, typescript 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-Bound Adapter Overview Design an application-owned Navan adapter pinned to the tenant's actual integration contract. 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 Do not assume a public SDK, base URL, pagination model, or error envelope. Preserve the vendor payload at the boundary, then map it into versioned application types backed by captured schemas and fixtures. Authentication Accept a secret-provider callback or file-transfer credential reference, never a literal secret. Bind credentials, tenant identity, and host allowlist together so configuration cannot cross environments. Instructions 1. Inventory the enabled operation or file contract and record its revision. 2. Define transport-neutral input, result, page, and error types. 3. Implement authentication, timeout, size limit, and redacted telemetry at one boundary. 4. Preserve raw identifiers as opaque strings and money with explicit currency. 5. Add fixture tests for success, empty data, pagination, denial, throttling, and drift. 6. Expose writes only as separate methods with idempotency and approval requirements. 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 docs and fixtures is local; live calls, secrets, package additions, generated clients, file transfers, and state changes need explicit approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-sdk-patterns--af7bb6