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

/algolia-install-auth

@820dfc8
Run it yourself

Install and verify the Algolia JavaScript v5 client with least-privilege credential separation. Use when bootstrapping a backend, browser search client, or environment configuration. Trigger with "install Algolia", "configure Algolia auth", or "Algolia API key setup".

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

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. ≈841 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 ≈291 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 Install and Authentication

Overview

This skill establishes the package and credential boundary before feature work. It distinguishes the application ID from API keys and separates browser search from trusted write operations.

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

  • Inspect and follow the repository's package manager and lockfile rather than installing an unpinned latest package.
  • Use algoliasearch v5 imports and client-level methods; do not introduce the removed initIndex pattern.
  • Expose only a search-only or appropriately secured key in browser configuration.
  • Use custom keys with minimum ACLs and index restrictions for backend jobs.

Authentication

Load credentials through the repository's approved secret mechanism. Never print values, commit .env files, or use the Admin key as the default backend credential.

Instructions

  1. Inspect runtime, package manager, lockfile, existing wrappers, and environment conventions.
  2. Select a compatible pinned v5 version and add it through the native package workflow.
  3. Define separate environment names for application ID, browser search key, and server write key.
  4. Create one client factory per trust boundary and reject missing configuration without echoing values.
  5. Verify browser search with a read-only query and backend writes only against a disposable index.
  6. Scan built assets and source history for accidental write-key exposure.

Approval Boundaries

Do not install dependencies, create provider keys, alter secret stores, or rotate existing credentials outside the repository and account scope provided.

Output

Return the dependency diff, client factories, environment-name contract, key/ACL matrix, verification results, secret-scan evidence, and remaining setup actions.

Error Handling

Condition Response
v4 API appears in code Use the official v5 migration guide before mixing patterns.
Key rejected Verify application pairing, ACL, restriction, and environment.
Write key enters browser build Stop, remove it, and rotate if exposed.
No safe test index Limit verification to read-only search.

Examples

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

Input:

runtime=node; package-manager=pnpm; client-major=5; browser=search-only

Expected handoff:

read-check=pass; write-check=disposable-index-only; 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.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides standard instructions for installing and configuring the official Algolia JavaScript client. It includes security best practices such as using environment variables for credentials and protecting them with .gitignore. No malicious patterns or security risks were identified.

  • 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 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[project-path] [runtime]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "authentication"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-install-auth