Skip to main content
brightdata-debug-bundle Collect Bright Data debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Bright Data problems.
Trigger with phrases like "brightdata debug", "brightdata support bundle",
"collect brightdata logs", "brightdata diagnostic".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill brightdata-debug-bundle명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
jeremylongshore
jeremylongshore/claude-code-plugins-plus-skills
GitHub 저장소 열기 name brightdata-debug-bundle description Collect Bright Data debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Bright Data problems.
Trigger with phrases like "brightdata debug", "brightdata support bundle",
"collect brightdata logs", "brightdata diagnostic".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep version 1.6.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","scraping","data","brightdata"] compatibility Designed for Claude Code
Bright Data Debug Bundle
Overview
Collect all diagnostic information needed for Bright Data support tickets: proxy connectivity, zone status, response headers, and error logs.
Prerequisites
Bright Data zone credentials configured
curl available
Permission to collect environment info
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="brightdata-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== Bright Data Debug Bundle ===" | tee "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date -u) " | tee -a "$BUNDLE_DIR /summary.txt"
echo "" >> "$BUNDLE_DIR /summary.txt"
Step 2: Collect Environment and Connectivity
echo "--- Runtime ---" >> "$BUNDLE_DIR /summary.txt"
node --version >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Node.js: not found" >> "$BUNDLE_DIR /summary.txt"
python3 --version >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Python: not found" >> "$BUNDLE_DIR /summary.txt"
echo
"--- Credentials ---"
"$BUNDLE_DIR /summary.txt"
echo
"BRIGHTDATA_CUSTOMER_ID: ${BRIGHTDATA_CUSTOMER_ID:+[SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"BRIGHTDATA_ZONE: ${BRIGHTDATA_ZONE:-[NOT SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"BRIGHTDATA_ZONE_PASSWORD: ${BRIGHTDATA_ZONE_PASSWORD:+[SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"BRIGHTDATA_API_TOKEN: ${BRIGHTDATA_API_TOKEN:+[SET]} "
"$BUNDLE_DIR /summary.txt"
echo
"--- SSL Certificate ---"
"$BUNDLE_DIR /summary.txt"
if
"./brd-ca.crt"
then
in
"$BUNDLE_DIR /summary.txt"
else
echo
"brd-ca.crt: NOT FOUND"
"$BUNDLE_DIR /summary.txt"
fi
Step 3: Test Proxy Connectivity with Verbose Headers
echo "--- Proxy Test ---" >> "$BUNDLE_DIR /summary.txt"
PROXY_USER="brd-customer-${BRIGHTDATA_CUSTOMER_ID} -zone-${BRIGHTDATA_ZONE} "
curl -x "http://${PROXY_USER} :${BRIGHTDATA_ZONE_PASSWORD} @brd.superproxy.io:33335" \
-s -D "$BUNDLE_DIR /proxy-headers.txt" \
-o "$BUNDLE_DIR /proxy-response.txt" \
-w "HTTP %{http_code} in %{time_total}s\n" \
https://lumtest.com/myip.json 2>> "$BUNDLE_DIR /summary.txt" || echo "Proxy FAILED" >> "$BUNDLE_DIR /summary.txt"
grep -i "x-luminati\|x-brd" "$BUNDLE_DIR /proxy-headers.txt" >> "$BUNDLE_DIR /summary.txt" 2>/dev/null || true
echo "--- Direct Connectivity ---" >> "$BUNDLE_DIR /summary.txt"
curl -s -o /dev/null -w "brightdata.com: HTTP %{http_code}\n" https://brightdata.com >> "$BUNDLE_DIR /summary.txt"
curl -s -o /dev/null -w "status page: HTTP %{http_code}\n" >> "$BUNDLE_DIR /summary.txt"
echo "--- Port Connectivity ---" >> "$BUNDLE_DIR /summary.txt"
nc -zv brd.superproxy.io 33335 >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Port 33335: BLOCKED" >> "$BUNDLE_DIR /summary.txt"
nc -zv brd.superproxy.io 9222 >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Port 9222: BLOCKED" >> "$BUNDLE_DIR /summary.txt"
Step 4: Check Zone Status via API
if [ -n "${BRIGHTDATA_API_TOKEN:-} " ]; then
echo "--- Zone Status ---" >> "$BUNDLE_DIR /summary.txt"
curl -s -H "Authorization: Bearer ${BRIGHTDATA_API_TOKEN} " \
"https://api.brightdata.com/zone/get_active_zones" \
| python3 -m json.tool >> "$BUNDLE_DIR /zone-status.json" 2>/dev/null || true
fi
Step 5: Package and Report
if [ -d "logs" ]; then
grep -i "brightdata\|proxy\|502\|407\|luminati" logs/*.log 2>/dev/null \
| tail -100 | sed 's/password=[^ ]*/password=***REDACTED***/g' \
>> "$BUNDLE_DIR /error-logs.txt"
fi
tar -czf "$BUNDLE_DIR .tar.gz" "$BUNDLE_DIR "
echo ""
echo "Bundle created: $BUNDLE_DIR .tar.gz"
echo "Contents:"
ls -la "$BUNDLE_DIR /"
echo ""
echo "REVIEW FOR SENSITIVE DATA BEFORE SHARING"
Output
summary.txt — credentials check, connectivity results, error headersproxy-headers.txt — full proxy response headers with X-Luminati diagnosticsproxy-response.txt — proxy test response bodyzone-status.json — zone configuration and statuserror-logs.txt — recent errors (passwords redacted)
Sensitive Data Checklist ALWAYS REDACT before sharing:
API tokens and zone passwords
Customer IDs
Target URLs (if confidential)
Error codes and X-Luminati headers
Response timing
Runtime versions
Port connectivity results
Resources
Next Steps For rate limit issues, see brightdata-rate-limits.
