Agent skill · software engineering · jeremylongshore
juicebox-webhooks-events
Handle Juicebox webhooks and events.
Why this skill is useful
Provides specific implementation patterns and webhook handling for Juicebox API that the AI wouldn't reliably generate on its own.
What it needs
Requires express installed locally. Requires juicebox account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Juicebox Webhooks & Events Overview Juicebox delivers webhook notifications for AI-powered people search and analysis workflows. Subscribe to events for completed analyses, updated datasets, ready exports, and quota warnings to build automated pipelines that react to Juicebox intelligence in real time without polling the API. Webhook Registration Signature Verification Event Handler Event Types Event Payload Fields Use Case ------- --------------- ---------- analysis.completed analysisid, resultcount, query Fetch and process search results dataset.updated datasetid, recordsadded, totalrecords Refresh downstream dashboards export.ready exportid, downloadurl, format Auto-download CSV/JSON exports quota.warning usagepercent, resetdate, plantier Alert admin before limit hit search.alert alertid, newmatches, criteria Notify on new candidate matches Retry & Idempotency Error Handling Issue Cause Fix ------- ------- ----- Signature mismatch Secret rotated without updating handler Re-fetch secret from Juicebox dashboard Empty resultcount Analysis timed out Check analysis status before processing Export link expired Download URL has 1-hour TTL Fetch immediately on export.ready event Quota exceeded API calls after limit hit Implement backoff until resetdate Prerequisites A secret-manager webhook secret, event-origin allowlist, replay-window policy, source-authority check, suppression policy, and opaque event ledger. Instructions 1. Authenticate origin before parsing, validate timestamp/event ID, and reject unknown sources, stale deliveries, and malformed payloads. 2. Store only a bounded redacted envelope and use event ID plus target revision as the idempotency key. 3. Verify source authority, suppression, and destination before enqueueing enrichment; quarantine uncertainty instead of exporting or enriching a contact. 4. Canary one sandbox source, observe aggregate policy probes, then promote or disable the consumer. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/juicebox-webhooks-events