Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-migration-deep-dive

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-migration-deep-dive

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈74 tokens for metadata: the name and description. ≈837 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈297 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Approval Boundaries

Do not overwrite the current production index, declare relevance equivalence from a few queries, or retire the source system before rollback expiry.

Output

Return the capability map, data transform, gap register, backfill evidence, query comparison, cutover plan, acceptance decision, and rollback procedure.

Error Handling

Condition Response
Unsupported query feature Document the gap and design an approved product alternative.
Record counts differ Reconcile filtering, deletes, and source snapshot boundaries.
Relevance regresses Keep source traffic and tune against the approved query set.
Rollback data drifts Define dual-write or replay before cutover.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

source=legacy-search; snapshot=snap-184; target=products_algolia_next

Expected handoff:

records=reconciled; query-suite=198/200; two-gaps=owner-review; cutover=not-started

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a structured framework for migrating search systems to Algolia, prioritizing safety, data integrity, and best practices for secret management. No malicious patterns or security risks were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [source-system] [target-index]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "migration"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-migration-deep-dive