Agent skill · software engineering · jeremylongshore
algolia-hello-world
Create a minimal Algolia JavaScript v5 indexing and search proof using a disposable index. Use when verifying credentials, learning the client boundary, or proving first connectivity. Trigger with "Algolia hello world", "first Algolia search", or "test Algolia setup".
Why this skill is useful
Provides specific commands and patterns for integrating with Algolia's API that the AI wouldn't reliably generate on its own.
What it needs
Requires algoliasearch 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 Verified First Search Overview This skill proves the smallest complete write-read-cleanup cycle: create known records, wait for the indexing task, query one record, and remove the disposable index after review. 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 the installed algoliasearch v5 client; methods such as saveObjects, waitForTask, and searchSingleIndex are called on the client. Assign explicit objectID values so verification is deterministic. Use a new disposable index, never an existing production index. Treat cleanup as an observed task with its own result. Authentication Use a custom backend key restricted to the disposable index and necessary operations. The browser should never receive this write credential. Instructions 1. Confirm the package version, application ID, credential source, and validated disposable index name. 2. Create two non-sensitive records with stable object IDs. 3. Save the records and retain the returned task ID. 4. Wait for that task, then search for one unique value with searchSingleIndex. 5. Assert the expected object ID and record the request metadata without secrets. 6. After human confirmation, delete the disposable index and verify cleanup. Approval Boundaries Do not use a production index, copy an Admin key into source, or delete an index until its exact disposable name is displayed and approved. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-hello-world--242280