Agent skill · software engineering · jeremylongshore
brightdata-hello-world
Prove one authorized Bright Data proxy request and capture a redacted connectivity receipt. Use when validating a new zone, testing egress, or separating proxy failures from target failures. Trigger with: "test my Bright Data proxy", "verify this zone", "run a safe Bright Data smoke test".
Why this skill is useful
Provides specific code examples for integrating with Bright Data's Web Unlocker proxy that are not widely known.
What it needs
Requires axios, dotenv, requests 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 Authorized First Request Overview Run the smallest possible request against Bright Data's test endpoint. Keep proxy credentials out of the URL and process output, inspect current x-brd- and Proxy-Status headers, and stop after one bounded proof. Prerequisites An active non-production proxy zone and zone username/password Authorization to reach geo.brdtest.com from the test environment A log sink configured to redact authorization and proxy credentials Instructions Step 1: Confirm the target Read the runbook and Grep the allowlist for geo.brdtest.com. Refuse arbitrary or authenticated targets for this proof. Step 2: Run one request Pass proxy authentication separately from the proxy host so the credential does not appear in the URL. Step 3: Classify the response Record the HTTP status plus redacted Proxy-Status, x-brd-err-code, x-brd-error, and x-brd-err-msg values. Never retain the proxy authorization header or full username. Step 4: Close the proof Store the timestamp, zone alias, target, result class, and owner decision. A successful test proves connectivity only; it does not authorize production collection. Tool Discipline Use Read and Grep to confirm the approved target and redaction policy. Use Bash(curl:) for exactly the bounded Bright Data test request shown here. Do not write target content, rotate identities, or retry policy denials. Output One connectivity result tied to a zone alias and approved target Redacted provider error metadata when the request fails A clear pass, retry-later, or owner-escalation decision Examples Use a dedicated development zone and run one request to geo.brdtest.com. A 200 with expected provider metadata is a connectivity pass. A 407 is an access failure; a policy 403 is a stop condition, not a reason to switch networks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-hello-world--9a4f2a