Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-incident-runbook

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈69 tokens for metadata: the name and description. ≈850 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈276 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

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

Expected handoff:

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

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured runbook for diagnosing and managing search incidents related to Algolia. It follows security best practices for credential management, change control, and data verification.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [incident-id]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "incident-response"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-incident-runbook