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

/algolia-common-errors

@820dfc8
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.6% 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 ≈291 characters, or 3.6%.

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

operation=saveObjects; status=403; index=products_stage

Expected handoff:

cause=missing-addObject-ACL; fix=request-scoped-key; admin-key-used=no

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

    The skill provides diagnostic instructions and code snippets for troubleshooting Algolia API errors. It uses standard API calls to Algolia's official domains and follows safe practices for handling credentials.

  • 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] [error-or-request-id]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "debugging"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-common-errors