Agent skill · software engineering · jeremylongshore
algolia-multi-env-setup
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".
Why this skill is useful
Provides specific commands and configurations for setting up Algolia across multiple environments that the AI wouldn't reliably generate on its own.
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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-multi-env-setup