---
name: algolia-incident-runbook
description: >-
  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".
argument-hint: "[repository-path] [incident-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - incident-response
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-incident-runbook
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/algolia-incident-runbook`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/algolia-incident-runbook`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/algolia-incident-runbook --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-incident-runbook --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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.

## Approval Boundaries

Do not invent severity targets, rotate credentials, rebuild production, change relevance settings, or delete an index without the incident commander's approval.

## Output

Return the incident classification, timeline, evidence links, containment action, recovery checks, customer impact, unresolved risks, and follow-up tasks.

## Error Handling

| Condition | Response |
|---|---|
| Provider status unclear | Continue application and data-path diagnosis while monitoring official status. |
| Credential suspected exposed | Escalate rotation through the approved secret process. |
| Freshness mismatch | Trace source snapshot and task completion before reindexing. |
| Recovery changes relevance | Rollback or obtain product-owner acceptance. |

## Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

```text
incident=SEV-from-company-runbook; symptom=stale-products; provider-status=operational
```

Expected handoff:

```text
cause=indexing-task-failed; containment=previous-index; verification=12/12-queries-pass
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook/references/official-docs.md)
- [Algolia status](https://status.algolia.com/)
- [Monitoring API](https://www.algolia.com/doc/rest-api/monitoring)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
