Agent skill · software engineering · jeremylongshore
algolia-core-workflow-a
Implement or review a single-index Algolia search contract with filters, facets, pagination, and highlighting. Use when building product or content search against the JavaScript v5 client. Trigger with "Algolia search workflow", "add facets", or "searchSingleIndex".
Why this skill is useful
Provides specific Algolia search implementation patterns and configurations that the AI wouldn't reliably generate on its own.
What it needs
Requires 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 Search Contract Overview This skill defines the read path between application input and Algolia search results. It keeps query construction, allowed filters, pagination, and result projection explicit so UI behavior can be tested independently. 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 Use searchSingleIndex for one index and pass indexName plus searchParams on the v5 client. Treat filters and facet filters as structured application inputs; do not concatenate untrusted syntax. Request only attributes the interface needs and preserve objectID as the stable result identity. Enable click analytics only when the product also implements the query ID and event contract. Authentication Browser search should use the search-only key or a backend-generated secured key. Write-capable credentials remain server-side. Instructions 1. Inspect the installed client version, index settings, record schema, and current UI query state. 2. Define a typed search input with bounded query length, page, hits per page, filters, and facets. 3. Translate application filters through an allowlist rather than accepting raw filter strings. 4. Call the v5 search boundary and map hits into the application result type. 5. Test empty query, no results, special characters, pagination edges, and unavailable facets. 6. Verify returned attributes do not disclose fields the interface should not expose. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-core-workflow-a