Agent skill · software engineering · jeremylongshore
algolia-install-auth
Install and verify the Algolia JavaScript v5 client with least-privilege credential separation. Use when bootstrapping a backend, browser search client, or environment configuration. Trigger with "install Algolia", "configure Algolia auth", or "Algolia API key setup".
Why this skill is useful
Provides specific commands and configuration patterns for integrating Algolia with Node.js/TypeScript 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 Install and Authentication Overview This skill establishes the package and credential boundary before feature work. It distinguishes the application ID from API keys and separates browser search from trusted write operations. 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 Inspect and follow the repository's package manager and lockfile rather than installing an unpinned latest package. Use algoliasearch v5 imports and client-level methods; do not introduce the removed initIndex pattern. Expose only a search-only or appropriately secured key in browser configuration. Use custom keys with minimum ACLs and index restrictions for backend jobs. Authentication Load credentials through the repository's approved secret mechanism. Never print values, commit .env files, or use the Admin key as the default backend credential. Instructions 1. Inspect runtime, package manager, lockfile, existing wrappers, and environment conventions. 2. Select a compatible pinned v5 version and add it through the native package workflow. 3. Define separate environment names for application ID, browser search key, and server write key. 4. Create one client factory per trust boundary and reject missing configuration without echoing values. 5. Verify browser search with a read-only query and backend writes only against a disposable index. 6. Scan built assets and source history for accidental write-key exposure. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-install-auth--ebfe77