algolia-observability
Set up observability for Algolia: Prometheus metrics for search latency/errors, OpenTelemetry tracing, structured logging, and Grafana dashboards. "monitor algolia", "algolia alerts", "algolia tracing", "algolia dashboard". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-observability --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Algolia Observability ## Overview Algolia provides built-in analytics in the dashboard, but production systems need application-level observability: latency histograms, error rate counters, distributed traces, and alerts. This skill instruments the `algoliasearch` v5 client with Prometheus, OpenTelemetry, and structured logging. ## Key Metrics to Track | Metric | Type | Why It Matters | |-------
What does the algolia-observability skill do?
Set up observability for Algolia: Prometheus metrics for search latency/errors, OpenTelemetry tracing, structured logging, and Grafana dashboards. "monitor algolia", "algolia alerts", "algolia tracing", "algolia dashboard". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-observability --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.