Individual skill
brightdata-common-errors
Analyze Bright Data proxy and dataset failures using current provider codes without bypassing policy controls. Use when diagnosing 407, 403, 429, 502, snapshot, or delivery failures. Trigger with: "diagnose a Bright Data error", "what does this x-brd code mean", "triage a failed snapshot".
plugins/saas-packs/brightdata-pack/skills/brightdata-common-errors/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- web-data Declared skill tag
- bright-data Declared skill tag
- common-errors Declared skill tag
- operations Declared skill tag
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,505 bytesreferences/official-docs.mddoc · 684 bytes
Read excerpt
# Bright Data Failure Triage
## Overview
Separate provider, target, client, and policy failures using HTTP status, `Proxy-Status`, and current `x-brd-*` fields. Never treat an access or compliance denial as a cue to rotate products, regions, or identities.
## Prerequisites
- A redacted response or snapshot receipt
- The zone, product, operation ID, and approved target class
- Access to the current Bright Data error catalog and network-status page
## Instructions
### Step 1: Collect minimal evidence