Agent skill · software engineering · jeremylongshore
brightdata-deploy-integration
Design and review a bounded Bright Data worker deployment with separate proxy, Browser API, scraper, snapshot, and delivery responsibilities. Use when preparing a runtime topology or deployment manifest. Trigger with: "deploy this Bright Data worker", "design Bright Data queues", "review the Bright Data deployment".
Why this skill is useful
Provides specific deployment scripts and configurations for Bright Data integrations across multiple cloud platforms that the AI wouldn't generate on its own.
What it needs
Requires fly, gcloud, vercel 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 Worker Deployment Overview Deploy collection as bounded workers instead of one privileged process. Separate synchronous proxy or Browser API requests from scraper triggers, snapshot polling, downloads, and destination delivery so each stage has its own authority, queue, resource ceiling, and rollback. Prerequisites An approved workload manifest naming targets, fields, products, and destinations Managed secret references and environment-specific Bright Data resources Queue, object-storage, quarantine, and observability facilities Instructions Step 1: Inventory runtime responsibilities Read the application and Grep for proxy requests, Browser API sessions, /datasets/v3/trigger, progress checks, snapshot downloads, and delivery calls. Assign each responsibility to the smallest worker role. Step 2: Define admission and isolation Write or Edit deployment manifests with separate queues and identities for request, browser, trigger, poll, download, validate, and delivery workers. Add target allowlists, byte and record ceilings, timeouts, concurrency bounds, and dead-letter routing. Step 3: Protect data movement Stream large snapshots to bounded storage, validate schema before downstream use, quarantine unexpected content, and require an approved destination before invoking /datasets/v3/deliver/SNAPSHOTID. Step 4: Make rollout reversible Specify health signals, queue-depth and error-class alerts, canary capacity, drain behavior, rollback version, secret revocation, and replay rules. Produce manifests and a deployment plan; do not initiate production traffic from this skill. Tool Discipline Use Read and Grep for topology and configuration discovery. Use Write and Edit for deployment manifests, queue contracts, policies, tests, and runbooks. This skill does not deploy, rotate credentials, create zones, or send provider requests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-deploy-integration--4f97d1