Agent skill · software engineering · jeremylongshore
navan-multi-env-setup
Separate Navan development, test, staging, and production identities, data, and destinations. Use when configuring multiple environments or tenants. Trigger with "Navan environments", "separate Navan tenants", or "Navan staging setup".
Why this skill is useful
Adds specific environment setup patterns and OAuth management for Navan integrations that the AI wouldn't reliably generate on its own.
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 Tenant and Environment Isolation Overview Separate Navan development, test, staging, and production identities, data, and destinations. 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 Not every Navan customer has equivalent sandbox, API, file, or identity surfaces. Record the real environment model from the account, then simulate absent capabilities locally instead of relabeling production as test. Authentication Give each available environment and tenant distinct credentials, secret paths, host allowlists, destinations, schedules, and revocation owners. Never select production by default. Instructions 1. Inventory real tenants and vendor-provided environments. 2. Map each integration surface, identity, destination, and data class. 3. Create fail-closed configuration with explicit tenant and environment labels. 4. Use synthetic fixtures where a vendor sandbox is unavailable. 5. Define promotion evidence without copying secrets or personal data. 6. Test cross-tenant denial, revocation, rollback, and configuration drift. 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 Creating credentials, enabling a surface, copying data, adding destinations, changing schedules, or promoting to production requires explicit approval. Error Handling A URL suffix is not sufficient environment isolation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-multi-env-setup