Agent skill · software engineering · jeremylongshore
algolia-ci-integration
Build and review a bounded CI gate for Algolia index configuration and disposable-index smoke tests. Use when search changes need pull-request evidence without mutating production. Trigger with "Algolia CI", "test Algolia in GitHub Actions", or "search deployment gate".
Why this skill is useful
Adds a complete CI/CD pipeline for Algolia integration, including executable scripts for index validation and automated reindexing that aren't in public docs.
What it needs
Requires gh, npm 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 CI Integration Overview This skill adds a deterministic CI lane for code that owns Algolia records, settings, or query behavior. It separates offline contract tests from an optional network smoke test against an explicitly disposable index. 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 Pin the Node dependency and runner version already supported by the repository. Keep production application IDs, index names, and write credentials out of pull-request workflows. Name disposable indices with a run-specific suffix and record their cleanup result. Test the exact client methods used by the application; for JavaScript v5, index operations live on the client. Authentication Use a repository secret containing a custom key limited to the disposable index and required ACLs. Do not use an Admin key or expose any write key to forked pull requests. Instructions 1. Map the package manager, test runner, Algolia wrapper, and current CI event permissions. 2. Add offline tests for record shaping, settings serialization, and query contracts. 3. Make the live smoke job opt-in or protected, with a unique non-production index name. 4. Create records, wait for the task, perform one known query, and collect request IDs on failure. 5. Delete the disposable index in a guaranteed cleanup step and report cleanup failure separately. 6. Verify untrusted forks cannot read secrets or execute the credentialed job. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-ci-integration