Agent skill · software engineering · jeremylongshore
algolia-debug-bundle
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".
Why this skill is useful
Adds an executable script that automates the collection of Algolia diagnostic data, which is not commonly available in public documentation.
What it needs
Requires curl, jq, node, npm 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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-debug-bundle