algolia-common-errors
/algolia-common-errors
Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed".
Triggers from the description
Arguments
/algolia-common-errors [repository-path] [error-or-request-id]
Original author description
Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed".
How it works
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Examples
SKILL.md preview
--- name: algolia-common-errors description: >- Diagnose Algolia request, credential, index, task, and query failures from concrete evidence. Use when an integration returns 4xx or 5xx responses, stale results, or unexpected empty hits. Trigger with "debug Algolia error", "Algolia 403", or "Algolia search failed". argument-hint: "[repository-path] [error-or-request-id]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.8.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: - saas - algolia - debugging model: inherit effort: medium compatibility: Designed for Claude Code --- # Algolia Error Triage ## Overview This skill turns an Algolia symptom into a reproducible diagnosis. It favors the response status, message, request ID, client version, operation, and target index over generic error folklore. ## 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 - A 403 is an authorization fact, not proof that an unrestricted key is required. - A successful write is asynchronous; compare the returned task ID and wait behavior before calling data stale. - A 404 can identify a missing index, application, route, or regional endpoint; preserve the full response. - A 429 must be interpreted from the returned message and current plan or key restrictions, not from a guessed universal quota. ## Authentication Inspect only redacted key metadata and ACL intent. Never print, paste, or replace a credential with an Admin key merely to make a failing request succeed. ## Instructions 1. Capture the smallest failing call, status, message, request ID, application ID suffix, index name, and package version. 2. Classify the operation as search, indexing, settings, key management, analytics, or events. 3. Compare the operation with the intended key ACLs and index restrictions. 4. Reproduce against a safe test index or read-only query with the same client boundary. 5. Check task completion, index spelling, filters, attributes, and environment routing in that order. 6. Apply one correction, rerun the minimal reproduction, and record before-and-after evidence. ## Approval Boundaries Do not broaden ACLs, rotate keys, change production settings, or replay writes until the target and failure class are confirmed. ## Output Return the symptom, evidence, root-cause hypothesis, ruled-out alternatives, minimum fix, verification result, and any remaining uncertainty. ## Error Handling | Condition | Response | |---|---| | 401 or 403 | Verify application/key pairing and required ACL; do not escalate privilege blindly. | | 404 | Confirm endpoint, application, and exact index name. | | 429 | Honor the response and measure request pressure before adding bounded retry. | | Stale result | Wait for the specific task and verify the queried index. | ## Examples Use this compact input and expected handoff to calibrate scope and evidence quality. Input: ```text operation=saveObjects; status=403; index=products_stage ``` Expected handoff: ```text cause=missing-addObject-ACL; fix=request-scoped-key; admin-key-used=no ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [API keys](https://www.algolia.com/doc/guides/security/api-keys) - [JavaScript API client](https://www.algolia.com/doc/libraries/javascript) - [Algolia status](https://status.algolia.com/)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 1 KB
Versions
The database has no other skills named algolia-common-errors.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d20a11db218b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100algolia-sdk-patterns
Create or review a typed application adapter around the Algolia JavaScript v5 client. Use when client calls, index names, errors, task waits, and credential usage are scattered. Trigger with "Algolia SDK patterns", "Algolia client wrapper", or "refactor search client". - 100algolia-reference-architecture
Design or review an Algolia search architecture across source data, indexing, query, UI, events, and operations. Use when establishing system boundaries or evaluating an existing integration. Trigger with "Algolia architecture", "design search platform", or "review Algolia integration". - 100algolia-audit
Entry point for auditing, reviewing, or health-checking an EXISTING Algolia implementation. Use when the ask sounds like: "audit our search", "review our setup", "is this configured correctly", "health check", "we inherited this implementation", "something seems off with… - 100algolia-quickstart
Use this skill to set up and provision Algolia from scratch: create a new Algolia account, sign up, log in / authenticate the Algolia CLI, or provision a new application to obtain an App ID and API key. Trigger when a user is getting started with Algolia and has no account, no… - 90algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality. - 90algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.