Review a Bright Data release candidate against workload approval, data controls, reliability, cost, observability, and rollback evidence. Define failure checks and canary thresholds, then record whether the integration is ready for production promotion.
Gate a Bright Data integration for production with authorization, reliability, cost, data, and rollback evidence. Use when promoting a proxy, Browser API, scraper, snapshot, or delivery workload. Trigger with: "production checklist for Bright Data", "approve this Bright Data rollout", "review a Bright Data release".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Make production promotion a fail-closed evidence decision. A green connectivity test is insufficient without target authorization, schema and data controls, secret ownership, backpressure, observability, and a tested rollback.
Read approvals and Grep runtime configuration for unlisted targets, fields, products, zones, or delivery destinations. Verify public-data scope and recipient and retention decisions.
Confirm secret-manager binding, environment isolation, egress allowlists, redirect denial, byte, record, and job ceilings, adaptive backpressure, redacted telemetry, and idempotent processing.
Write or Edit tests for revoked credentials, policy 403, 429, provider 5xx, snapshot failure or expiry, malformed schema, oversized delivery, duplicate delivery, and downstream outage.
Run a bounded approved canary through the deployment workflow. Compare authorization, success, error, latency, cost, and data-quality thresholds; promote only with a rollback receipt.
Use Read and Grep for release-evidence inspection. Use Write and Edit for missing tests, manifests, runbooks, and the decision record. This skill does not change production credentials, zones, traffic, or delivery destinations.
Release one worker with a low job and byte ceiling and an approved test target. Promote only after duplicate delivery, policy denial, secret redaction, schema quarantine, and rollback drills all produce their expected receipts.
| Failure | Meaning | Response |
|---|---|---|
| A required owner has not approved | Release authority is incomplete | Keep the candidate staged |
| Rollback depends on an untested old zone | Recovery is speculative | Run the rollback drill before promotion |
| Canary produces unexpected fields | Data contract drifted | Quarantine results and fail the gate |
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.