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

/algolia-multi-env-setup

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-multi-env-setup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈77 tokens for metadata: the name and description. ≈844 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 ≈310 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 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:

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

Expected handoff:

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

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 provides a secure framework for configuring Algolia development, staging, and production environments. It emphasizes security best practices, such as credential isolation and preventing accidental production data access, while utilizing official Algolia documentation and verified packages.

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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-multi-env-setup