Plan a Bright Data collection deployment by splitting requests, scraper jobs, snapshot downloads, validation, and delivery into bounded workers. Define queues, permissions, resource limits, approved destinations, rollout checks, and rollback steps in deployment manifests.
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".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
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.
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.
Stream large snapshots to bounded storage, validate schema before downstream use, quarantine unexpected content, and require an approved destination before invoking /datasets/v3/deliver/SNAPSHOT_ID.
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.
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.
A trigger worker creates one approved scraper job, a poller records state transitions, a downloader streams the completed snapshot to quarantine, a validator enforces the schema, and a delivery worker releases only accepted records to an approved destination.
| Failure | Meaning | Response |
|---|---|---|
| One worker holds every credential | Blast radius is too large | Split identities and secret scopes |
| Download memory grows with snapshot size | Transfer is unbounded | Stream with byte ceilings and backpressure |
| Delivery destination is runtime input | Exfiltration boundary is open | Resolve destinations from an approved manifest |
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.