Agent skill · software engineering · jeremylongshore
navan-ci-integration
Gate Navan integration changes with deterministic fixtures and an isolated optional live smoke. Use when adding CI checks for adapters or data pipelines. Trigger with "test Navan in CI", "Navan contract tests", or "secure Navan CI".
Why this skill is useful
Adds a complete GitHub Actions CI/CD workflow for Navan API integration with executable scripts for authentication and health checks.
What it needs
Requires jq installed locally. Requires github 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-First CI Contract Overview Gate Navan integration changes with deterministic fixtures and an isolated optional live smoke. 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 Required pull-request checks must not depend on a Navan tenant, credentials, paid services, or private traveler data. A live smoke belongs only in a trusted event with protected secrets and a fixed read-only budget. Authentication Run required jobs without Navan secrets and deny network access. Resolve a non-production credential only inside the separately approved live environment; never expose it to fork code. Instructions 1. Enumerate contract, mapping, privacy, and side-effect regressions. 2. Add sanitized fixtures for each enabled surface and failure class. 3. Require schema, mapping, redaction, reconciliation, and rollback tests. 4. Deny sockets and assert no secret is available in ordinary jobs. 5. Define an optional trusted live smoke with one bounded read and no retry. 6. Publish content-free receipts and preserve artifacts without sensitive payloads. 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 Protected secrets, network, live tenant reads, fixture refreshes, and required-check changes need explicit repository and data-owner approval. Error Handling A skipped required test is not a pass. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-ci-integration--6d4bd0