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

/algolia-security-basics

@820dfc8
Run it yourself

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

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-security-basics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈73 tokens for metadata: the name and description. ≈876 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.6% 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 ≈292 characters, or 3.6%.

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

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

Expected handoff:

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

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.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill audits Algolia security settings in a repository, including API key exposure and ACL configurations. It carries a low risk of indirect prompt injection because it processes repository content and external documentation without explicit delimiters to isolate data from instructions.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-security-basics