Agent skill · data analytics · jeremylongshore
algolia-observability
Instrument an Algolia integration for actionable availability, latency, freshness, relevance, and event-health signals. Use when defining dashboards, alerts, traces, or service objectives. Trigger with "monitor Algolia", "Algolia metrics", or "search observability".
Why this skill is useful
Adds executable scripts for monitoring Algolia search performance and error tracking that aren't covered in public documentation.
What it needs
Requires express, prom-client installed locally. Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia Search Observability Overview This skill instruments the application-owned search journey rather than substituting generic provider claims. It connects client outcomes, request IDs, index publication, source freshness, and product-level relevance indicators. Prerequisites A named repository, environment, and Algolia application or index in scope The local lockfile and installed client types as implementation authority A safe read-only query or explicitly disposable test target Current first-party documentation for any provider behavior that affects the change Tool Discipline Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan. Current Contract Derive thresholds and objectives from the product SLO and measured baseline; do not use universal latency numbers. Separate application latency from Algolia request latency and rendering time. Track source snapshot to completed indexing task to searchable sentinel for freshness. Treat event delivery and query-ID coverage as their own health surface. Authentication Telemetry must exclude API keys, raw personal data, sensitive queries, and unrestricted record payloads. Use approved read-only monitoring access where provider data is needed. Instructions 1. Define the user journey, owned SLOs, current baseline, and incident-routing owner. 2. Instrument operation, outcome, duration, index alias, environment, SDK version, request ID, and bounded retry count. 3. Add freshness markers linking source snapshot, task completion, and searchable sentinel. 4. Measure no-result and event coverage using privacy-reviewed aggregation. 5. Build dashboards and alerts from sustained error-budget or baseline deviation, not a copied threshold. 6. Test telemetry during success, denial, timeout, stale-index, and event-failure scenarios. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-observability