Agent skill · data analytics · jeremylongshore
exa-observability
Instrument Exa calls with content-free metrics, traces, cost, and asynchronous lifecycle signals that support diagnosis without logging retrieved text. Use when operating or reviewing this Exa boundary. Trigger with "Exa observability", "review Exa observability", or "fix Exa observability".
Why this skill is useful
Provides specific metrics tracking and monitoring patterns for Exa API integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires datadog, opentelemetry, prometheus installed locally. Requires pagerduty, slack account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Operational Telemetry Overview Instrument Exa calls with content-free metrics, traces, cost, and asynchronous lifecycle signals that support diagnosis without logging retrieved text. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Exa responses expose request IDs and often costDollars; errors expose status and tags; Contents exposes per-URL statuses. Agent, Monitor, Webset, and Batch operations add IDs, states, queues, events, and terminal outcomes that must be reconciled separately. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Define service-level objectives for each endpoint and asynchronous product. 2. Emit endpoint, status, tag, latency, attempt, result count, and request ID safely. 3. Measure Contents status mix and freshness mode rather than logging page content. 4. Track run age, terminal state, webhook lag, queue depth, and reconciliation drift. 5. Attribute cost by environment, workload, key, product, and owner. 6. Alert on error-class shifts, stalled state, throttling, overload, credit risk, and missing events. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-observability