Agent skill · data analytics · jeremylongshore
navan-data-handling
Manage Navan personal, corporate, travel, payment, receipt, profile, and location data across integrations. Use when defining collection, sharing, retention, or AI access. Trigger with "Navan data handling", "Navan privacy", or "classify Navan data".
Why this skill is useful
Provides specific data extraction and transformation patterns for Navan's booking and transaction data that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires airbyte, fivetran, 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 Travel and Expense Data Governance Overview Manage Navan personal, corporate, travel, payment, receipt, profile, and location data across integrations. 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's privacy policy distinguishes Corporate Customer Data from other information and names itinerary, profile, passport, loyalty, payment, receipt, location, support, and usage data. Corporate customers remain responsible for lawful instructions and user rights where they act as controller. Authentication Restrict access by purpose, role, tenant, environment, and data class. Third-party AI or MCP connections can process Navan personal information and therefore require an explicit approved boundary. Instructions 1. Inventory fields from source through every processor, store, artifact, and human workflow. 2. Classify controller/processor role, purpose, legal basis, jurisdiction, and sensitivity with counsel or privacy owner. 3. Minimize collection and separate business travel from personal travel information. 4. Set retention, deletion, access, portability, correction, and incident procedures. 5. Redact logs, fixtures, prompts, analytics, support bundles, and test artifacts. 6. Verify downstream contracts, access reviews, deletion propagation, and evidence. 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-data-handling--766ff0