Agent skill · software engineering · jeremylongshore
algolia-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".
Why this skill is useful
Provides specific implementation patterns and error handling for Algolia SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires algoliasearch installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia JavaScript v5 SDK Boundary Overview This skill centralizes the application contract around the installed v5 client without hiding important provider results. It keeps search, writes, task waits, and error metadata testable and explicit. 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 Create clients at trust boundaries and inject them into adapters rather than constructing them in every call site. For v5, call operations on the client and pass indexName; do not restore initIndex. Return typed application results while preserving request IDs, task IDs, and provider error context. Put retry, timeout, batching, and index resolution policies in one reviewed layer. Authentication Accept credentials from the approved runtime configuration and never expose them through adapter return values, exceptions, logs, or browser/server boundary mistakes. Instructions 1. Inventory every SDK import, installed version, client construction, index name, and direct call. 2. Group use cases into search, indexing, configuration, events, analytics, or administration boundaries. 3. Define typed inputs and outputs plus explicit timeout, task-wait, and error behavior. 4. Implement the smallest adapter and migrate one caller with contract tests. 5. Test success, authorization denial, timeout, stale task, malformed filters, and cancellation. 6. Migrate remaining callers incrementally and remove duplicate credential or retry logic. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-sdk-patterns