Agent skill · software engineering · jeremylongshore
algolia-upgrade-migration
Migrate an Algolia JavaScript client integration from v4 to v5 with inventory, compatibility tests, and rollback. Use when removing initIndex, updating client methods, or reconciling mixed major versions. Trigger with "upgrade Algolia v5", "remove initIndex", or "Algolia SDK migration".
Why this skill is useful
Provides specific migration commands and patterns for upgrading from Algolia v4 to v5 that the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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 v4 to v5 Upgrade Overview This skill follows the official v5 migration contract and the repository's pinned dependency graph. It treats import, method, parameter, response, wait, and test changes as one controlled migration. 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 Version 5 removes initIndex; methods live on the client and receive indexName. Upgrade search-only imports and multi-search calls according to the official guide, not a mechanical rename. Replace chained write waits with the documented v5 wait helpers and retain task IDs. Check all Algolia packages, frameworks, wrappers, mocks, generated types, and examples for major-version coupling. Authentication Do not change key privilege during an SDK upgrade. Use existing least-privilege test credentials only for safe verification targets. Instructions 1. Inventory package versions, imports, initIndex, client wrappers, methods, waits, mocks, and runtime targets. 2. Read the current official v5 migration guide and installed types for every used method. 3. Update the dependency and lockfile through the repository's package manager. 4. Migrate one boundary at a time, adapting parameters, responses, tasks, and errors. 5. Run type, unit, integration, build, and representative query tests; use a disposable index for writes. 6. Record compatibility gaps, final versions, release notes, rollback commit, and follow-up cleanup. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-upgrade-migration