---
name: algolia-core-workflow-b
description: >-
  Build a reliable Algolia indexing pipeline for full replacements, incremental updates, settings, synonyms, and rules. Use when a source of truth must publish deterministic search state. Trigger with "Algolia indexing workflow", "replace index records", or "sync Algolia".
argument-hint: "[repository-path] [source-dataset] [index-name]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - indexing
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-core-workflow-b
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-b
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-b/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-b`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/algolia-core-workflow-b`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-b) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/algolia-core-workflow-b`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/algolia-core-workflow-b --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-core-workflow-b --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Algolia Indexing Contract

## Overview

This skill designs the write path from an authoritative dataset to Algolia. It separates record transformation, validation, transport, task completion, and publication so a failed run cannot silently leave ambiguous search state.

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

- Generate stable `objectID` values from source identities and reject duplicates before upload.
- Choose `saveObjects` for bounded upserts and `replaceAllObjects` only for an intentional full-state replacement.
- Wait for returned task IDs before verification or traffic cutover.
- Version settings, synonyms, and rules as reviewable inputs; do not infer them from production state during deployment.

## Authentication

Run indexing only from a trusted backend with a custom key restricted to the target indices and required write ACLs. Keep search-only keys out of indexing jobs.

## Instructions

1. Identify the source of truth, deletion semantics, index aliases or replicas, and acceptable publication window.
2. Transform and validate records locally, including size, required fields, stable IDs, and prohibited data.
3. Select incremental or full replacement based on source deletion guarantees and rollback needs.
4. Submit bounded batches, retain task IDs, and wait for completion with an overall timeout.
5. Verify counts, sentinel records, settings hashes, and representative queries.
6. Record the source snapshot, target index, completed tasks, and rollback or prior-index path.

## Approval Boundaries

Do not run a full replacement, delete records, change settings, or swap a production target until the source snapshot and rollback plan are approved.

## Output

Return the data contract, operation choice, validation report, task receipts, post-write checks, deletion behavior, and rollback instructions.

## Error Handling

| Condition | Response |
|---|---|
| Duplicate objectID | Fail before upload and report source records. |
| Partial batch failure | Stop publication and preserve successful task IDs. |
| Task timeout | Do not assume failure or success; query task state. |
| Verification mismatch | Keep the prior production target and investigate. |

## Examples

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

Input:

```text
source=snapshot-2026-09-10; mode=full-replacement; target=products_next
```

Expected handoff:

```text
records=48012; tasks=49-complete; sentinel-query=pass; cutover=pending-approval
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-b/references/official-docs.md)
- [JavaScript API client](https://www.algolia.com/doc/libraries/javascript)
- [Indexing guidance](https://www.algolia.com/doc/guides/sending-and-managing-data)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
