Agent skill · marketing growth · jeremylongshore
algolia-webhooks-events
Implement and validate Algolia click, conversion, and view events while separating them from source-to-index synchronization. Use when adding Insights, query attribution, or event-driven record updates. Trigger with "Algolia Insights", "track search conversion", or "sync database to Algolia".
Why this skill is useful
Provides specific implementation details for integrating Algolia's Insights API for event tracking that the AI wouldn't reliably generate on its own.
What it needs
Requires algoliasearch, search-insights 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 Search Events and Source Sync Overview This skill corrects a common category error: user interaction events go to the Insights API, while database or business events drive an application-owned indexing pipeline. These flows have different identity, delivery, privacy, and retry contracts. 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 Use the dedicated search-insights client or supported framework integration for browser events; it is not the Search API client. Set clickAnalytics when a search-related event needs a returned query ID. Use a stable pseudonymous user token and preserve query ID, object IDs, positions, and event names as required. Design source-to-index updates as idempotent writes with ordering, dead-letter, replay, and reconciliation. Authentication Browser events use the documented Insights credential pattern and must not contain write-capable keys or personal identifiers. Index sync uses a separate restricted backend key. Instructions 1. Classify the requested flow as user interaction telemetry, source-data synchronization, or both. 2. Map consent, user identity, query ID, object IDs, event taxonomy, and downstream feature consumers. 3. Implement events with the pinned search-insights or framework API and validate payloads using provider tooling. 4. Implement source sync separately with stable IDs, idempotency, bounded retry, dead-letter handling, and task waits. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-webhooks-events