Index of every page on this site: llms.txt
All skills
Run it yourself

Establish a Navan integration access contract without guessing endpoints, grants, or scopes. Use when onboarding a Booking API, Expense API, SFTP, SCIM, SSO, or direct integration. Trigger with "set up Navan access", "authenticate Navan", or "review Navan credentials".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/navan-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈72 tokens for metadata: the name and description. ≈805 when used: this file. ≈279 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈290 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Navan Integration Access Intake

Overview

Establish a Navan integration access contract without guessing endpoints, grants, or scopes. 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

Navan publicly confirms Booking API, Expense API, SFTP, direct integrations, SCIM, SAML, and OpenID Connect surfaces. Exact hosts, credentials, scopes, schemas, and enablement are tenant- and contract-specific; copy them from the current in-account source.

Authentication

Record the credential type, issuer, audience or destination, scopes or permissions, expiry, rotation owner, and storage location from the tenant contract. Never infer OAuth client credentials or reuse interactive session cookies.

Instructions

  1. Choose one integration surface and its business owner.
  2. Capture the current tenant documentation URL, revision date, and access prerequisites.
  3. Request least-privilege non-production credentials through the approved secret channel.
  4. Create a redacted connection profile with no credential values.
  5. Plan one read-only or metadata-only validation allowed by the contract.
  6. Record rotation, revocation, escalation, and production-promotion gates.

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

Require the Navan admin and data owner before credential issuance, scope expansion, production access, SSO/SCIM changes, or any traveler-data read.

Error Handling

  • A public product page is not an endpoint contract.
  • A login redirect is not proof that an API route exists.
  • Missing scope or tenant enablement must fail closed and go to the Navan administrator.

Output

Return an access matrix, evidence links, credential owner, allowed environments, read-only validation, rotation plan, and unresolved tenant questions. Identify assumptions, owners, expirations, and evidence gaps explicitly.

Examples

  • Prepare Expense API access without placing a secret in the repository.
  • Document an Okta SCIM handoff while leaving provisioning disabled.

Validation

Verify the evidence date, tenant, credential provenance, least privilege, secret storage, revocation owner, and absence of live values in artifacts. Record expected and observed results, including fail-closed behavior.

Resources

  • Current first-party evidence map — recheck dated sources and the selected tenant's in-account contract before relying on mutable endpoints, fields, entitlements, limits, or delivery behavior.
  • Record tenant observations as environment-specific evidence, never universal Navan guarantees.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a secure and well-documented workflow for integrating with the Navan API using OAuth 2.0. It adheres to security best practices for credential management, such as using environment variables and ensuring secrets are excluded from version control via .gitignore. All external dependencies and network operations target well-known, trusted services.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<tenant> <integration-surface> <environment>
version
1.9.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "navan",
  "access"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live or external Navan actions require network access and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/navan-install-auth