algolia-multi-env-setup
Configure Algolia across dev/staging/production: index prefixing, per-environment API keys, settings-as-code, and environment isolation guards. "algolia environment setup", "algolia config by env". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Algolia Multi-Environment Setup ## Overview Algolia doesn't have built-in environment separation. You either use **separate Algolia applications** (strongest isolation) or **index prefixing** within one application (simpler). This skill covers both approaches. ## Environment Strategies | Strategy | Isolation | Cost | Complexity | |----------|-----------|------|------------| | Index prefixing | S
What does the algolia-multi-env-setup skill do?
Configure Algolia across dev/staging/production: index prefixing, per-environment API keys, settings-as-code, and environment isolation guards. "algolia environment setup", "algolia config by env". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill algolia-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.