Agent skill · software engineering · jeremylongshore
algolia-migration-deep-dive
Plan and execute a reversible migration from another search system or legacy index design to Algolia. Use when translating schemas, queries, relevance behavior, or production traffic. Trigger with "migrate to Algolia", "Algolia cutover", or "search engine migration".
Why this skill is useful
Adds executable scripts and detailed migration patterns for transitioning to Algolia that are not commonly found in public documentation.
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 Migration Overview This skill treats migration as a measured compatibility program: source data, query semantics, ranking, filters, UI behavior, traffic, and rollback are assessed separately before cutover. 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 Preserve the source system as the rollback authority until acceptance criteria pass. Translate capabilities from observed queries and product journeys, not feature-name similarity. Build a new target index and avoid in-place destructive conversion. Compare relevance with a representative, owner-approved query set and explicit tolerances. Authentication Use separate least-privilege credentials for source reads, Algolia writes, and browser search. Keep all secret material outside migration artifacts. Instructions 1. Inventory source schema, analyzers, queries, filters, facets, ranking behavior, traffic, and operational constraints. 2. Define the Algolia record model, stable IDs, settings, synonyms, rules, and unsupported semantic gaps. 3. Backfill a new target index from a reproducible source snapshot and retain task receipts. 4. Run structural checks, representative query comparisons, latency observations, and UI acceptance tests. 5. Shadow or canary traffic when available, with named rollback thresholds and owners. 6. Cut over only after approval, then reconcile drift and retain the rollback window. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-migration-deep-dive