---
name: algolia-security-basics
description: >-
  Audit and harden Algolia credentials, record exposure, index restrictions, and tenant search controls. Use when reviewing frontend keys, backend ACLs, key rotation, or data visibility. Trigger with "secure Algolia", "Algolia key audit", or "Algolia security review".
argument-hint: "[repository-path] [application-id]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.8.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - saas
  - algolia
  - security
model: inherit
effort: medium
compatibility: Designed for Claude Code
title: algolia-security-basics
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-security-basics
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-security-basics/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/algolia-security-basics`. 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-security-basics`, 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-security-basics) 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-security-basics`. 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-security-basics --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/algolia-security-basics --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 Security Baseline

## Overview

This skill reviews the actual security boundary of an Algolia integration. A browser search-only key is intentionally visible, so record contents, index restrictions, secured-key design, and abuse controls remain essential.

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

- Never index data that must remain secret merely because an attribute is not displayed.
- Use custom main keys with minimum ACLs and restrictions; rotate long-lived keys under an owned policy.
- Generate secured keys on a trusted backend and require restrictions appropriate to the user or tenant.
- Treat referer restrictions, rate limits, filters, and ACLs as layers whose current behavior must be verified.

## Authentication

Inspect key metadata without exporting secret values. Admin credentials stay out of application defaults, browser bundles, logs, support artifacts, and developer examples.

## Instructions

1. Inventory every application ID, environment variable, client constructor, key owner, ACL, restriction, and exposed index.
2. Scan source, built assets, history, logs, and documentation for write-capable key exposure.
3. Review record fields and index settings for data a search-only client could retrieve or scrape.
4. Map backend operations to custom key ACLs and tenant search to secured-key restrictions.
5. Test allowed and denied paths, including cross-index and cross-tenant attempts.
6. Document rotation, revocation, incident response, ownership, exceptions, and retest dates.

## Approval Boundaries

Do not rotate or revoke production keys, alter index restrictions, or remove access until dependencies and recovery paths are verified.

## Output

Return the key and actor inventory, exposure findings, data-visibility review, allowed/denied tests, remediation plan, rotation procedure, and residual risks.

## Error Handling

| Condition | Response |
|---|---|
| Write key found in browser | Contain and rotate through the incident process. |
| Search key exposes sensitive records | Remove the data and review index design. |
| Tenant restriction bypassed | Disable affected path and correct server-generated restrictions. |
| Key owner unknown | Treat it as orphaned and investigate before revocation. |

## Examples

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

Input:

```text
app=APP…9X; actors=browser,indexer,ops; indices=products_*
```

Expected handoff:

```text
browser=search-only; indexer=custom-minimum; tenant-denial=pass; exposed-write-key=none
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/algolia-security-basics/references/official-docs.md)
- [API keys](https://www.algolia.com/doc/guides/security/api-keys)
- [Secured API keys](https://www.algolia.com/doc/guides/building-search-ui/going-further/api-keys-security/react)
- [Security best practices](https://www.algolia.com/doc/guides/security/security-best-practices)
