Agent skill · data analytics · jeremylongshore
cohere-observability
Instrument Cohere requests, streams, retrieval, tools, limits, quality, and cost with low-cardinality telemetry and safe traces. Use when monitoring a Cohere service. Trigger with "Cohere observability", "Cohere metrics", or "monitor Cohere".
Why this skill is useful
Adds executable scripts for Prometheus metrics and OpenTelemetry tracing specifically tailored for Cohere API v2, which are not commonly found in public documentation.
What it needs
Requires cohere-ai, opentelemetry-sdk, prometheus installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Cohere Observability Overview Expose enough evidence to separate application, retrieval, model, capacity, and provider failures without logging credentials or customer content. Prerequisites The target repository, runtime, environment, and accountable owner An approved Cohere team and key for any live verification Current quality, security, privacy, capacity, and change-control requirements Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current Cohere primary documentation. Use Write or Edit only when the user requested implementation and the exact target files are known; never write credentials or customer content. Current Contract Measure queue, retrieval, provider, first-event, completion, and tool durations separately. Label metrics with bounded dimensions such as endpoint, operation, resolved model, environment, outcome, and retry class. Keep prompts, documents, embeddings, keys, and raw tool arguments out of telemetry by default. Pair operational metrics with sampled quality, citation, and safety evaluations. Authentication Use an environment-specific key injected from an approved secret manager. Never print, persist, commit, or place COAPIKEY in an example. Confirm access with the least costly bounded operation appropriate to the task, and treat key creation, rotation, revocation, role changes, and production-capacity requests as owner-approved actions. Instructions 1. Define service objectives and an allowlist of telemetry fields before instrumenting. 2. Create counters for requests, outcomes, retries, throttles, circuit transitions, and tool decisions. 3. Create histograms for queue, retrieval, provider, first-event, completion, and end-to-end duration. 4. Record usage and cost units without tenant names or unbounded request IDs as metric labels. 5. Build alerts for availability, sustained throttling, queue age, latency, quality, and spend. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cohere-observability