Agent skill · data analytics · jeremylongshore
brightdata-core-workflow-b
Analyze and operate the Bright Data Web Scraper API async snapshot lifecycle with terminal-state and delivery controls. Use when collecting an approved batch, polling a snapshot, or downloading large structured results. Trigger with: "run a Bright Data dataset job", "poll a Bright Data snapshot", "download Web Scraper API results".
Why this skill is useful
Adds specific commands and workflows for using Bright Data's SERP and Web Scraper APIs that the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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 Async Snapshot Pipeline Overview Implement the documented trigger, progress, and download lifecycle as a state machine. Keep dataset identifiers and approved inputs separate from the API key; cap polling, validate terminal states, and stream results rather than loading arbitrary payloads into memory. Prerequisites A reviewed dataset ID and approved public input manifest A named-user Bright Data API key in the runtime secret manager A retention, schema, maximum-record, and maximum-byte policy Instructions Step 1: Validate the manifest Read the requested dataset/inputs and Grep for disallowed target classes or fields. Hash the approved input manifest before submission. Step 2: Trigger once Use Bash(curl:) only against the fixed Bright Data API origin with the API key as a Bearer header. Step 3: Poll deliberately Persist the returned snapshotid; poll GET /datasets/v3/progress/SNAPSHOTID with bounded attempts and provider-directed delay. Handle ready, failed, empty, expired, and still-building states explicitly. Step 4: Download and verify Stream GET /datasets/v3/snapshot/SNAPSHOTID in the approved format. Use parts for large results, hold format/compression parameters constant, enforce byte/record ceilings, and validate the schema before promotion. Tool Discipline Use Read and Grep for policy and schema checks. Use Write and Edit only for the manifest, state machine, tests, and redacted receipt. Use Bash(curl:) for fixed-origin Bright Data API calls after authorization; never print the Bearer value or raw result data. Output Input-manifest hash and snapshot identifier Bounded state-transition log without target data or credentials Schema/size validation and a promoted-or-quarantined result Examples Submit a small approved URL batch, record the returned snapshot ID, poll until ready, and stream JSON to quarantine. Reject a response whose schema, record count, or byte count exceeds the manifest even if the provider marks it ready. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-core-workflow-b--0b62d8