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

/algolia-upgrade-migration

@820dfc8
Run it yourself

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

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.9% 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 ≈315 characters, or 3.9%.

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

Approval Boundaries

Do not combine the SDK upgrade with relevance, index schema, credential, or broad architectural changes unless separately scoped and tested.

Output

Return the usage inventory, official mapping, dependency diff, migrated boundaries, test evidence, remaining v4 patterns, compatibility notes, and rollback.

Error Handling

Condition Response
initIndex remains Locate the call or generated artifact and migrate it.
Method signature differs Follow installed v5 types and current official reference.
Mock passes but live test fails Correct the application adapter contract.
Rollback changes lockfile only Revert source and lockfile as one unit.

Examples

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

Input:

from=algoliasearch-4; to=pinned-5; initIndex-calls=9; wrappers=2

Expected handoff:

initIndex=0; typecheck=pass; integration=pass; disposable-write-cleaned=yes

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

    This skill assists in migrating Algolia integrations from v4 to v5 by analyzing local code and fetching official documentation. It poses a low-severity risk of indirect prompt injection because it processes external documentation to guide code modifications in the local environment.

  • 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] [package-name]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "upgrade"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

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