Agent skill · data analytics · jeremylongshore
navan-observability
Observe Navan integrations with content-free signals that support reconciliation and incidents. Use when defining logs, metrics, traces, and alerts. Trigger with "monitor Navan", "Navan observability", or "alert on Navan sync".
Why this skill is useful
Provides specific patterns and structured logging implementations for monitoring Navan API integrations that are not commonly found in public documentation.
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 Integration Observability Overview Observe Navan integrations with content-free signals that support reconciliation and incidents. 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 Operational signals should identify tenant alias, environment, surface, contract revision, window, stage, counts, timing, status class, and reconciliation state without exposing travel, payment, receipt, credential, or free-text content. Authentication Telemetry backends receive no Navan secrets or authorization metadata. Restrict sensitive correlation mappings and raw evidence to the approved incident boundary. Instructions 1. Define freshness, completeness, correctness, latency, and recovery objectives. 2. Emit structured stage events with bounded labels and content-free identifiers. 3. Measure source reads, accepted records, quarantine, destination acknowledgements, and reconciliation deltas. 4. Alert on stalled checkpoints, repeated denial, contract drift, queue age, and unexplained totals. 5. Link alerts to status checks, runbooks, owners, and evidence locations. 6. Test dashboards and paging with synthetic failures. 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 New telemetry processors, raw payload capture, sensitive label expansion, production tracing, and on-call routing changes require approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-observability--43b22e