Agent skill · software engineering · jeremylongshore
algolia-deploy-integration
Plan and verify deployment of an Algolia-backed application with separated browser and server credentials. Use when releasing search code, index configuration, or event instrumentation. Trigger with "deploy Algolia", "Algolia production rollout", or "search release checklist".
Why this skill is useful
Adds executable scripts for deploying Algolia apps with proper API key management and frontend integration that aren't in public docs.
What it needs
Requires fly, gcloud, npm, vercel installed locally. Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia Deployment Integration Overview This skill coordinates application deployment with the Algolia assets it depends on. It treats code, records, settings, keys, and events as separate release surfaces with explicit ordering and rollback. 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 The browser receives only a search-only or secured key; write-capable keys stay in trusted server or job environments. Pin application and index names per environment rather than deriving production targets from branch names. Complete indexing tasks and representative queries before routing production traffic. Deploy event instrumentation only after user-token, consent, query ID, and validation behavior are reviewed. Authentication Provision custom least-privilege keys through the approved secret store. Never place Admin keys in static build variables, client bundles, deployment logs, or preview environments. Instructions 1. Map the deploy platform, runtime boundaries, environment variables, index targets, and current rollback mechanism. 2. Verify client packages and API usage against the pinned lockfile and current first-party docs. 3. Prepare or verify target records, settings, synonyms, and rules before the application cutover. 4. Deploy server and browser configuration with credential separation and redacted logging. 5. Run a read-only health check plus representative search tests against the intended target. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-deploy-integration