Agent skill · software engineering · jeremylongshore
brightdata-webhooks-events
Build a secure receiver and replay contract for Bright Data snapshot delivery without assuming provider IPs, payload size, or retry timing. Use when accepting webhook-style dataset delivery. Trigger with: "receive a Bright Data snapshot", "secure Bright Data delivery", "design Bright Data webhook handling".
Why this skill is useful
Provides specific implementation patterns for handling Bright Data webhooks and signature validation that the AI wouldn't reliably generate on its own.
What it needs
Requires express installed locally. Requires brightdata account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Bright Data Snapshot Delivery Receiver Overview Treat snapshot delivery as an untrusted, repeatable data-transfer event. Configure delivery with the current POST /datasets/v3/deliver/SNAPSHOTID API, authenticate the managed destination, stream the body, validate it, and make downstream processing idempotent. Prerequisites A completed approved snapshot and its expected schema A managed HTTPS endpoint with destination authentication Durable quarantine storage and a replay ledger Instructions Step 1: Establish the delivery contract Read the receiver and Grep for body buffering, unauthenticated routes, hard-coded provider IPs, guessed retry schedules, and direct writes to trusted tables. Record the expected schema, format, destination, and ownership. Step 2: Configure an approved destination Write or Edit the integration so an authorized control-plane client requests POST /datasets/v3/deliver/SNAPSHOTID with type=webhook and managed destination authentication. Never place destination credentials in the URL or logs. Step 3: Receive defensively Stream the request into bounded quarantine storage. Authenticate before processing, cap bytes and duration, compute a digest, validate format and schema, and derive an idempotency key from trusted delivery context plus content digest. Step 4: Acknowledge and replay safely Acknowledge only after durable acceptance. Make duplicates no-ops, quarantine malformed or oversized content, and replay from retained evidence through the same validator. Do not invent provider retry or source-IP guarantees. Tool Discipline Use Read and Grep to inspect receiver, routing, and storage code. Use Write and Edit for receiver logic, validation, idempotency, fixtures, and the replay runbook. This skill does not invoke delivery or expose a public endpoint. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-webhooks-events--3f1f21