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

/algolia-webhooks-events

@820dfc8
Run it yourself

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".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈80 tokens for metadata: the name and description. ≈899 when used: this file. ≈333 more on demand in 1 file.

Description uses 4.0% 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 ≈319 characters, or 4.0%.

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 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. Test missing query ID, duplicate delivery, consent denial, offline clients, reordered source events, and replay.
  6. Measure event validity and index reconciliation, then document ownership and rollback.

Approval Boundaries

Do not send personal identifiers as user tokens, invent attribution when query IDs are absent, or treat interaction events as database webhooks.

Output

Return the flow classification, event and sync contracts, credential boundaries, validation results, retry and replay behavior, privacy decisions, and operational ownership.

Error Handling

Condition Response
Query ID missing Send only an appropriate non-search event or fix search attribution.
Consent denied Do not emit the event.
Duplicate source event Use idempotent version or event identity handling.
Validation rejects payload Correct the contract before enabling downstream features.

Examples

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

Input:

flow=search-clicks+catalog-updates; client=search-insights-2.17.3; consent=required

Expected handoff:

events=validated; queryID-coverage=measured; sync=idempotent; dead-letter=tested

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 technical instructions for implementing Algolia search events and data synchronization. It incorporates security best practices such as separating credential scopes and preventing the exfiltration of personal identifiers.

  • 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 yesterday.

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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-webhooks-events