---
name: algolia-debug-bundle
description: >-
  Collect a bounded, secret-safe Algolia diagnostic bundle for an incident or support escalation. Use when a reproducible search or indexing failure needs portable evidence. Trigger with "Algolia debug bundle", "collect Algolia diagnostics", or "Algolia support evidence".
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
  - diagnostics
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-debug-bundle
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-debug-bundle
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-debug-bundle/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-debug-bundle`. 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-debug-bundle`, 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-debug-bundle) 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-debug-bundle`. 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-debug-bundle --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-debug-bundle --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 Redacted Debug Bundle

## Overview

This skill assembles code, configuration shape, client versions, redacted request evidence, task IDs, and reproduction steps without copying API keys, full records, or unrestricted account data.

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

- Prefer local configuration names and hashes over live secret or key inspection.
- Collect the smallest failing request and response; redact credentials, personal data, and unrelated record fields.
- Include timestamps, regions or hosts, request IDs, task IDs, and client versions when available.
- Create a manifest before sharing so reviewers can see every included file and redaction rule.

## Authentication

Do not fetch, print, validate, or transmit secret values. If a support workflow needs account evidence, use a separately approved read-only credential and preserve only redacted results.

## Instructions

1. Define the incident, recipient, allowed data classes, time window, and maximum bundle size.
2. Inspect local dependencies, wrapper code, environment variable names, index configuration, and recent relevant logs.
3. Reproduce one safe read or disposable-index operation and capture redacted request metadata.
4. Scan every artifact for keys, tokens, emails, user tokens, record payloads, and unrelated secrets.
5. Build a plain-text manifest with collection source, hash, redaction action, and omission reason.
6. Review the manifest and bundle contents before any external transfer.

## Approval Boundaries

Do not use an Admin key for diagnosis, archive an entire environment, collect production records wholesale, or send the bundle automatically.

## Output

Return the reproduction, dependency versions, redacted evidence, artifact manifest, secret-scan result, omitted evidence, and a human-approved handoff path.

## Error Handling

| Condition | Response |
|---|---|
| Potential secret found | Remove the artifact or redact it, then rescan. |
| Reproduction mutates production | Stop and move to a disposable target. |
| Bundle exceeds limit | Narrow the time window and fields. |
| Required evidence is sensitive | Describe the gap and request an approved channel. |

## Examples

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

Input:

```text
incident=ALG-42; window=10m; target=products_readonly; bundle-limit=5MB
```

Expected handoff:

```text
artifacts=7; secret-scan=pass; production-records=0; transfer=pending-review
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-debug-bundle/references/official-docs.md)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
- [Security best practices](https://www.algolia.com/doc/guides/security/security-best-practices)
- [Algolia status](https://status.algolia.com/)
