---
name: algolia-multi-env-setup
description: >-
  Design isolated Algolia development, staging, preview, and production targets with explicit promotion rules. Use when environments share credentials or index names, or previews need bounded search data. Trigger with "Algolia environments", "Algolia staging setup", or "preview index".
argument-hint: "[repository-path] [environment-map]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - environments
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-multi-env-setup
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-multi-env-setup
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-multi-env-setup/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-multi-env-setup`. 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-multi-env-setup`, 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-multi-env-setup) 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-multi-env-setup`. 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-multi-env-setup --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-multi-env-setup --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 Multi-Environment Setup

## Overview

This skill makes environment isolation an application-owned contract. It does not assume one provider topology: separate applications, index namespaces, or a combination may be selected from security, data, cost, and operational requirements.

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

- Map every runtime environment to an explicit application ID, index namespace, credential owner, and data classification.
- Prevent preview or branch input from selecting an arbitrary production index.
- Promote versioned settings and transforms through review rather than copying unknown live state.
- Define lifecycle and cleanup for ephemeral indices before creating them.

## Authentication

Use separate custom keys and secret scopes for each environment. Browser builds receive only the search credential for their resolved environment.

## Instructions

1. Inventory applications, indices, replicas, keys, deployment environments, data sources, and retention rules.
2. Choose isolation boundaries based on blast radius, data policy, feature parity, and verified current commercial terms.
3. Implement an allowlisted environment resolver with no production fallback for unknown values.
4. Define reproducible record, settings, synonym, and rule promotion artifacts.
5. Test cross-environment denial, preview naming, cleanup, and production-selection safeguards.
6. Document owners, rotation, promotion, rollback, retention, and orphan-index review.

## Approval Boundaries

Do not create applications, copy production data, share keys, or delete preview indices until topology and data-policy owners approve.

## Output

Return the environment matrix, selected topology and tradeoffs, configuration resolver, key scopes, promotion flow, isolation tests, and lifecycle controls.

## Error Handling

| Condition | Response |
|---|---|
| Unknown environment | Fail closed instead of selecting production. |
| Preview requests production data | Reject unless an explicit approved sanitized source exists. |
| Settings drift | Rebuild from versioned artifacts and review the diff. |
| Orphan cleanup uncertain | Report candidates without deleting them. |

## Examples

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

Input:

```text
env=preview-482; app=nonprod; index=preview_482_products; data=synthetic
```

Expected handoff:

```text
resolver=allowlisted; prod-fallback=none; cleanup-after=reviewed-policy
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-multi-env-setup/references/official-docs.md)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
- [Sending and managing data](https://www.algolia.com/doc/guides/sending-and-managing-data)
- [Algolia pricing](https://www.algolia.com/pricing/)
