Check whether an approved Bright Data proxy zone can reach the designated test endpoint with one bounded request. The skill records a redacted connectivity result and provider error details, helping distinguish proxy access problems from other failures.
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".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
geo.brdtest.com from the test environmentRead the runbook and Grep the allowlist for geo.brdtest.com. Refuse arbitrary or authenticated targets for this proof.
Pass proxy authentication separately from the proxy host so the credential does not appear in the URL.
# 33335 is Bright Data's documented proxy gateway port.
curl --silent --show-error --include \
--proxy http://brd.superproxy.io:33335 \
--proxy-user "$BRIGHTDATA_PROXY_USERNAME:$BRIGHTDATA_PROXY_PASSWORD" \
https://geo.brdtest.com/welcome.txt
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.
Store the timestamp, zone alias, target, result class, and owner decision. A successful test proves connectivity only; it does not authorize production collection.
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.
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.
| Failure | Meaning | Response |
|---|---|---|
407 with client_10000 or related code | Invalid or missing zone credentials | Verify the zone binding without printing credentials |
| Policy 403 | Target or network is not permitted | Stop and escalate to the authorization owner |
| 429 | Account, target, or per-IP throttling | Stop the smoke test and follow the rate-control workflow |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.