Brd Browser Debug

by brightdatae825f02fbcd7No license264 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated yesterday

Debug Bright Data Scraping Browser sessions using the Browser Sessions API. Use this skill when the user encounters a Bright Data browser session error, puppeteer stack trace, failed scraper run, or asks about session bandwidth, duration, captchas, or connection issues. Also use when a Bright Data scraper produces unexpected results such as empty data, 0 items found, missing products, or fewer results than expected — session data can reveal whether the issue is network/proxy-side (blocks, captchas, redirects, timeouts) or client-side (selectors, extraction logic). Triggers on phrases like 'why did my session fail', 'debug my bright data session', 'check my scraping browser sessions', 'how much bandwidth did my scraper use', 'got 0 results', 'found 0', 'scraper returned empty', 'scraper not working', 'script didn't work', or when a Bright Data error code or brd.superproxy.io stack trace appears in the conversation. Requires BRIGHTDATA_API_KEY environment variable.

Instructions onlySoftware Development
  1. e825f02fbcd7Currentcommit e825f02Published Oct 8, 2026

Source and attribution

Source:brightdata/skillsinskills/brd-browser-debugat commite825f02

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal