Agent skill · software engineering · jeremylongshore
navan-hello-world
Prove one contracted Navan integration can authenticate and return a bounded read-only response without inventing a universal API. Use when completing access intake. Trigger with "test Navan access", "first Navan read", or "Navan connectivity proof".
Why this skill is useful
Adds executable scripts for authenticating and retrieving data from the Navan API, which are not publicly documented.
What it needs
Requires dotenv, node, python 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 Read-Only Connectivity Proof Overview Prove one contracted Navan integration can authenticate and return a bounded read-only response without inventing a universal API. 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 The public site confirms downstream Booking API access and an Expense API for custom ERP integrations, but it does not publish a universal route or response schema. The selected tenant's current contract is the only execution authority. Authentication Resolve the approved non-production credential at runtime and bind it only to the documented host. Redact headers, query values, traveler identities, booking details, and expense data from evidence. Instructions 1. Select the smallest documented read operation for the enabled surface. 2. Copy its method, host, path, parameters, and response schema into a dated local contract fixture. 3. Set a short timeout, response-size bound, and zero automatic retries. 4. Run only after network and data-access approval is explicit. 5. Validate status, content type, required fields, pagination envelope, and redaction. 6. Store a content-free receipt and revoke temporary credentials when required. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-hello-world