Agent skill · software engineering · jeremylongshore
algolia-local-dev-loop
Create a fast local development loop for Algolia record transforms and search behavior without contaminating shared indices. Use when iterating on search code, fixtures, or client wrappers. Trigger with "Algolia local development", "mock Algolia", or "test search locally".
Why this skill is useful
Adds specific scripts for seeding Algolia with test data and mocking the client in tests, which are not commonly found in public documentation.
What it needs
Requires node 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 Local Development Loop Overview This skill combines deterministic offline tests with an optional disposable-index integration test. It makes the local loop useful without pretending a mock reproduces provider ranking, task timing, or authorization. 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 Keep record transformation and query construction in pure functions that can be tested offline. Mock only the application-owned client boundary, not internal SDK implementation details. Use unique disposable index names for live checks and never reuse production credentials. Wait for write tasks and clean up live fixtures explicitly. Authentication Offline tests need no credential. Optional live tests use a custom key restricted to the disposable prefix and are disabled when credentials are absent. Instructions 1. Inspect the current client wrapper, package scripts, fixtures, and test framework. 2. Extract pure record-shaping and query-building functions with focused unit tests. 3. Create a typed adapter and mock its application-level responses and failures. 4. Add an opt-in live test that validates a generated disposable index name. 5. Write known records, wait, query, assert, and clean up while retaining task receipts. 6. Document how developers select offline versus live mode and how stale test indices are reported. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-local-dev-loop