Agent skill · software engineering · jeremylongshore
brightdata-reference-architecture
Create a governed Bright Data collection architecture with separate control, collection, quarantine, validation, and delivery trust zones. Use when designing or reviewing a production topology. Trigger with: "architect a Bright Data system", "draw Bright Data trust boundaries", "review collection architecture".
Why this skill is useful
Provides specific project structure and integration patterns for Bright Data applications that the AI wouldn't generate reliably on its own.
What it needs
Requires node 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 Governed Collection Architecture Overview Design collection as a policy-governed data pipeline, not a direct application call. Separate human approval and configuration from collection workers, then quarantine and validate all results before any trusted consumer or external destination receives them. Prerequisites Approved purpose, targets, fields, products, retention, recipients, and owners Current proxy, Browser API, scraper, snapshot, and delivery requirements Platform identity, queue, storage, policy, and observability capabilities Instructions Step 1: Discover the existing planes Read design and runtime files and Grep for Bright Data credentials, zones, API endpoints, browser sessions, queues, snapshot storage, and downstream destinations. Mark every trust transition and uncontrolled shortcut. Step 2: Define the topology Write or Edit an architecture with these responsibilities: Keep proxy and Browser API credentials in worker-specific secret bindings and REST API keys in authorized control-plane identities. Step 3: Apply cross-cutting controls Specify target and destination allowlists, least privilege, environment isolation, job and byte ceilings, backpressure, idempotency, schema validation, retention, deletion, redaction, audit evidence, and independent emergency stop. Step 4: Challenge the design Test policy denial, revoked credentials, 429, provider 5xx, browser timeout, snapshot failure or expiry, schema drift, duplicate delivery, storage exhaustion, and downstream outage. Require an owner and recovery decision for each path. Tool Discipline Use Read and Grep for topology discovery and evidence gathering. Use Write and Edit for diagrams, threat models, contracts, tests, and architecture decisions. This skill does not provision Bright Data resources or initiate collection. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-reference-architecture