Agent skill · marketing growth · jeremylongshore
algolia-incident-runbook
Diagnose and manage an Algolia-backed search incident with evidence, containment, and reversible recovery. Use when users see failed, stale, slow, or irrelevant search results. Trigger with "Algolia incident", "search outage", or "Algolia degraded".
Why this skill is useful
Adds a comprehensive incident response script for Algolia outages, including executable Bash commands and TypeScript code for emergency key creation.
What it needs
Requires curl, jq 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 Incident Runbook Overview This skill runs a product-owned incident process without assuming the provider is or is not at fault. Severity and response targets come from the organization's runbook, while diagnosis uses application, provider, and data-pipeline evidence. 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 Separate availability, authorization, freshness, latency, relevance, and event-collection symptoms. Check provider status as one signal, not as the root-cause conclusion. Preserve request IDs, task IDs, deployment SHAs, settings changes, and source snapshots. Prefer traffic rollback, prior index targets, or feature degradation paths that are already tested. Authentication Use read-only or narrowly scoped incident credentials. Never paste keys into tickets, chat, commands, screenshots, or diagnostic bundles. Instructions 1. Declare incident owner, affected journey, start time, severity source, and current user impact. 2. Freeze unrelated changes and capture recent releases, indexing runs, key changes, and provider status. 3. Run a known read-only query and compare application, direct client, and source-of-truth results. 4. Classify the failure surface and choose the smallest reversible containment. 5. Verify recovery with synthetic and representative user queries, not only HTTP success. 6. Record timeline, evidence, decisions, cleanup, follow-up owners, and rollback readiness. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-incident-runbook