Agent skill · software engineering · jeremylongshore
brightdata-debug-bundle
Assemble a Bright Data support bundle that preserves diagnostic value while excluding credentials, target data, and secret-bearing URLs. Use when escalating a persistent proxy, Browser API, snapshot, or delivery incident. Trigger with: "build a Bright Data debug bundle", "prepare evidence for Bright Data support", "redact a Bright Data incident".
Why this skill is useful
Adds an executable script for collecting Bright Data diagnostic information that isn't available in public documentation.
What it needs
Requires curl, nc 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 Redacted Support Bundle Overview Build a deterministic manifest of configuration shape, timestamps, versions, provider codes, and operation identifiers. Default-deny all raw headers and payloads, then include only explicitly allowlisted diagnostic fields. Prerequisites A run receipt and named incident owner A private output directory with a retention deadline A redaction policy covering URLs, credentials, cookies, headers, and target data Instructions Step 1: Inventory inputs Read the receipt and Grep candidate logs for secret names, proxy URLs, Bearer values, cookies, query strings, and target content before copying anything. Step 2: Create the manifest Write a small metadata file with product, zone alias, client/runtime version, UTC window, operation ID, state, and current provider error fields. Step 3: Redact and validate Use Edit only to remove disallowed material from the private bundle. Use Bash(python:) to scan for configured secret values and forbidden keys; fail closed if any match remains. Step 4: Seal the evidence Record sorted file hashes, owner, purpose, recipient, and deletion time. Transmit only through the approved private support channel; never attach it to a public issue. Tool Discipline Use Read and Grep for discovery and pre-copy review. Use Write and Edit only inside the exact private bundle path. Use Bash(python:) for local redaction and checksum checks; it must not upload the bundle or call Bright Data. Output Private manifest plus allowlisted redacted diagnostics Zero-secret scan and sorted file-hash receipt Named recipient, retention deadline, and deletion owner Examples Include Proxy-Status, x-brd-err-code, a rounded UTC window, and an opaque snapshot ID. Exclude proxy username/password, API key, target URL query, response body, cookies, and collected records. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/brightdata-debug-bundle