Agent skill · software engineering · jeremylongshore
brightdata-ci-integration
Build an offline-default CI contract lane for Bright Data and isolate any authorized live probe behind protected controls. Use when adding provider checks to pull requests or release workflows. Trigger with: "test Bright Data in CI", "add a Bright Data contract job", "secure the live CI probe".
Why this skill is useful
Adds a complete CI/CD pipeline setup for Bright Data with GitHub Actions, including executable scripts and integration tests that enhance the AI's capabilities in automating scraping tasks.
What it needs
Requires npm installed locally. Requires brightdata, github 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 CI Contract Lane Overview Keep pull-request verification credential-free and deterministic. Test the Bright Data adapter against fixtures by default, then place any necessary live probe in an independent protected job with a dedicated credential, approved target, and one-operation budget. Prerequisites A repository test command and representative sanitized success and failure fixtures The CI workflow and Bright Data adapter paths Maintainer approval before creating an optional live lane Instructions Step 1: Audit the workflow boundary Read the workflow and Grep for secrets, direct provider calls, artifact uploads, and execution from untrusted forks. Map every test to either the offline contract lane or the protected live lane. Step 2: Add the required offline lane Write or Edit the workflow so the required job runs npm ci and npm run test:brightdata:contract with BRIGHTDATAMODE=fixture. Cover success, authentication denial, policy denial, 429, provider 5xx, malformed output, and redaction without network access. Step 3: Isolate the optional live lane Make the live job independent of fork and pull-request execution. Require a protected environment, maintainer authorization, an approved public target, a dedicated least-privilege secret, a single-operation ceiling, a timeout, and redacted logs. Step 4: Prove negative behavior Use Bash(npm:) to run contract tests with missing and sentinel credentials. Confirm the offline job remains green without secrets and that failure artifacts contain neither credentials nor collected payloads. Tool Discipline Use Read and Grep to inspect workflows, adapters, and secret references. Use Write and Edit for the workflow, fixtures, tests, and runbook. Use Bash(npm:) only for dependency installation and repository test commands; do not use it to make live Bright Data requests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-ci-integration