Claude Code skill pack for Bright Data (18 skills)
Installation
Open Claude Code and run this command:
/plugin install brightdata-pack@claude-code-plugins-plus
Use --global to install for all projects, or --project for current project only.
Skills (18)
Configure Bright Data CI/CD integration with GitHub Actions and testing.
Bright Data CI Integration
Overview
Set up CI/CD pipelines for Bright Data integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- Bright Data test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
Create .github/workflows/brightdata-integration.yml:
name: Bright Data Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
BRIGHTDATA_API_KEY: ${{ secrets.BRIGHTDATA_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
BRIGHTDATA_API_KEY: ${{ secrets.BRIGHTDATA_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
Step 2: Configure Secrets
gh secret set BRIGHTDATA_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
describe('Bright Data Integration', () => {
it.skipIf(!process.env.BRIGHTDATA_API_KEY)('should connect', async () => {
const client = getBright DataClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
Output
- Automated test pipeline
- PR checks configured
- Coverage reports uploaded
- Release workflow ready
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
Examples
Release Workflow
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
BRIGHTDATA_API_KEY: ${{ secrets.BRIGHTDATA_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Bright Data production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
Branch Protection
required_status_checks:
- "test"
- "brightdata-integration"
Resources
Diagnose and fix Bright Data common errors and exceptions.
Bright Data Common Errors
Overview
Quick reference for the top 10 most common Bright Data errors and their solutions.
Prerequisites
- Bright Data SDK installed
- API credentials configured
- Access to error logs
Instructions
Step 1: Identify the Error
Check error message and code in your logs or console.
Step 2: Find Matching Error Below
Match your error to one of the documented cases.
Step 3: Apply Solution
Follow the solution steps for your specific error.
Output
- Identified error cause
- Applied fix
- Verified resolution
Error Handling
Authentication Failed
Error Message:
Authentication error: Invalid API key
Cause: API key is missing, expired, or invalid.
Solution:
# Verify API key is set
echo $BRIGHTDATA_API_KEY
Rate Limit Exceeded
Error Message:
Rate limit exceeded. Please retry after X seconds.
Cause: Too many requests in a short period.
Solution:
Implement exponential backoff. See brightdata-rate-limits skill.
Network Timeout
Error Message:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
// Increase timeout
const client = new Client({ timeout: 60000 });
Examples
Quick Diagnostic Commands
# Check Bright Data status
curl -s https://status.brightdata.com
# Verify API connectivity
curl -I https://api.brightdata.com
# Check local configuration
env | grep BRIGHTDATA
Escalation Path
- Collect evidence with
brightdata-debug-bundle - Check Bright Data status page
- Contact support with request ID
Resources
Next Steps
For comprehensive debugging, see brightdata-debug-bundle.
Execute Bright Data primary workflow: Core Workflow A.
Bright Data Core Workflow A
Overview
Primary money-path workflow for Bright Data. This is the most common use case.
Prerequisites
- Completed
brightdata-install-authsetup - Understanding of Bright Data core concepts
- Valid API credentials configured
Instructions
Step 1: Initialize
// Step 1 implementation
Step 2: Execute
// Step 2 implementation
Step 3: Finalize
// Step 3 implementation
Output
- Completed Core Workflow A execution
- Expected results from Bright Data API
- Success confirmation or error details
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Error 1 | Cause | Solution |
| Error 2 | Cause | Solution |
Examples
Complete Workflow
// Complete workflow example
Common Variations
- Variation 1: Description
- Variation 2: Description
Resources
Next Steps
For secondary workflow, see brightdata-core-workflow-b.
Execute Bright Data secondary workflow: Core Workflow B.
Bright Data Core Workflow B
Overview
Secondary workflow for Bright Data. Complements the primary workflow.
Prerequisites
- Completed
brightdata-install-authsetup - Familiarity with
brightdata-core-workflow-a - Valid API credentials configured
Instructions
Step 1: Setup
// Step 1 implementation
Step 2: Process
// Step 2 implementation
Step 3: Complete
// Step 3 implementation
Output
- Completed Core Workflow B execution
- Results from Bright Data API
- Success confirmation or error details
Error Handling
| Aspect | Workflow A | Workflow B |
|---|---|---|
| Use Case | Primary | Secondary |
| Complexity | Medium | Lower |
| Performance | Standard | Optimized |
Examples
Complete Workflow
// Complete workflow example
Error Recovery
// Error handling code
Resources
Next Steps
For common errors, see brightdata-common-errors.
Optimize Bright Data costs through tier selection, sampling, and usage monitoring.
Bright Data Cost Tuning
Overview
Optimize Bright Data costs through smart tier selection, sampling, and usage monitoring.
Prerequisites
- Access to Bright Data billing dashboard
- Understanding of current usage patterns
- Database for usage tracking (optional)
- Alerting system configured (optional)
Pricing Tiers
| Tier | Monthly Cost | Included | Overage |
|---|---|---|---|
| Free | $0 | 1,000 requests | N/A |
| Pro | $99 | 100,000 requests | $0.001/request |
| Enterprise | Custom | Unlimited | Volume discounts |
Cost Estimation
interface UsageEstimate {
requestsPerMonth: number;
tier: string;
estimatedCost: number;
recommendation?: string;
}
function estimateBright DataCost(requestsPerMonth: number): UsageEstimate {
if (requestsPerMonth <= 1000) {
return { requestsPerMonth, tier: 'Free', estimatedCost: 0 };
}
if (requestsPerMonth <= 100000) {
return { requestsPerMonth, tier: 'Pro', estimatedCost: 99 };
}
const proOverage = (requestsPerMonth - 100000) * 0.001;
const proCost = 99 + proOverage;
return {
requestsPerMonth,
tier: 'Pro (with overage)',
estimatedCost: proCost,
recommendation: proCost > 500
? 'Consider Enterprise tier for volume discounts'
: undefined,
};
}
Usage Monitoring
class Bright DataUsageMonitor {
private requestCount = 0;
private bytesTransferred = 0;
private alertThreshold: number;
constructor(monthlyBudget: number) {
this.alertThreshold = monthlyBudget * 0.8; // 80% warning
}
track(request: { bytes: number }) {
this.requestCount++;
this.bytesTransferred += request.bytes;
if (this.estimatedCost() > this.alertThreshold) {
this.sendAlert('Approaching Bright Data budget limit');
}
}
estimatedCost(): number {
return estimateBright DataCost(this.requestCount).estimatedCost;
}
private sendAlert(message: string) {
// Send to Slack, email, PagerDuty, etc.
}
}
Cost Reduction Strategies
Step 1: Request Sampling
function shouldSample(samplingRate = 0.1): boolean {
return Math.random() < samplingRate;
}
// Use for non-critical telemetry
if (shouldSample(0.1)) { // 10% sample
await brightdataClient.trackEvent(event);
}
Step 2: Batching Requests
// Instead of N individual calls
await Promise.all(ids.map(id => brightdataClient.get(id)));
// Use batch endpoint (1 call)
await brightdataClient.batchGet(ids);
Step 3: Caching (from P16)
- Cache frequently
Collect Bright Data debug evidence for support tickets and troubleshooting.
Bright Data Debug Bundle
Overview
Collect all necessary diagnostic information for Bright Data support tickets.
Prerequisites
- Bright Data SDK installed
- Access to application logs
- Permission to collect environment info
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
# brightdata-debug-bundle.sh
BUNDLE_DIR="brightdata-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"
echo "=== Bright Data Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"
Step 2: Collect Environment Info
# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "BRIGHTDATA_API_KEY: ${BRIGHTDATA_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"
Step 3: Gather SDK and Logs
# SDK version
npm list @brightdata/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"
# Recent logs (redacted)
grep -i "brightdata" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"
# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"
# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.brightdata.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
Step 4: Package Bundle
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
Output
brightdata-debug-YYYYMMDD-HHMMSS.tar.gzarchive containing:summary.txt- Environment and SDK infologs.txt- Recent redacted logsconfig-redacted.txt- Configuration (secrets removed)
Error Handling
| Item | Purpose | Included | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Environment versions | Compatibility check | ✓ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SDK version | Version-specific bugs | ✓ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Error logs (redacted) | Root cause analysis | ✓ | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Config (redacted) | Configuration issues
Deploy Bright Data integrations to Vercel, Fly.
ReadWriteEditBash(vercel:*)Bash(fly:*)Bash(gcloud:*)
Bright Data Deploy IntegrationOverviewDeploy Bright Data-powered applications to popular platforms with proper secrets management. Prerequisites
Vercel DeploymentEnvironment Setup
vercel.json Configuration
Fly.io Deploymentfly.toml
Secrets
Google Cloud RunDockerfile
Deploy Script
Environment Configuration Pattern
Health Check EndpointCreate a minimal working Bright Data example.
ReadWriteEdit
Bright Data Hello WorldOverviewMinimal working example demonstrating core Bright Data functionality. Prerequisites
InstructionsStep 1: Create Entry FileCreate a new file for your hello world example. Step 2: Import and Initialize Client
Step 3: Make Your First API Call
Output
Error Handling
ExamplesTypeScript Example
Python Example
ResourcesNext StepsProceed to Install and configure Bright Data SDK/CLI authentication.
ReadWriteEditBash(npm:*)Bash(pip:*)Grep
Bright Data Install & AuthOverviewSet up Bright Data SDK/CLI and configure authentication credentials. Prerequisites
InstructionsStep 1: Install SDK
Step 2: Configure Authentication
Step 3: Verify Connection
Output
Error Handling
ExamplesTypeScript Setup
Python Setup
ResourcesNext StepsAfter successful auth, proceed to Configure Bright Data local development with hot reload and testing.
ReadWriteEditBash(npm:*)Bash(pnpm:*)Grep
Bright Data Local Dev LoopOverviewSet up a fast, reproducible local development workflow for Bright Data. Prerequisites
InstructionsStep 1: Create Project Structure
Step 2: Configure Environment
Step 3: Setup Hot Reload
Step 4: Configure Testing
Output
Error Handling
ExamplesMock Bright Data Responses
Debug Mode
ResourcesOptimize Bright Data API performance with caching, batching, and connection pooling.
ReadWriteEdit
Bright Data Performance TuningOverviewOptimize Bright Data API performance with caching, batching, and connection pooling. Prerequisites
Latency Benchmarks
Caching StrategyResponse Caching
Redis Caching (Distributed)
Request Batching
Connection Optimization
Pagination OptimizationExecute Bright Data production deployment checklist and rollback procedures.
ReadBash(kubectl:*)Bash(curl:*)Grep
Bright Data Production ChecklistOverviewComplete checklist for deploying Bright Data integrations to production. Prerequisites
InstructionsStep 1: Pre-Deployment Configuration
Step 2: Code Quality Verification
Step 3: Infrastructure Setup
Step 4: Documentation Requirements
Step 5: Deploy with Gradual Rollout
Output
Error Handling
ExamplesHealth Check ImplementationImplement Bright Data rate limiting, backoff, and idempotency patterns.
ReadWriteEdit
Bright Data Rate LimitsOverviewHandle Bright Data rate limits gracefully with exponential backoff and idempotency. Prerequisites
InstructionsStep 1: Understand Rate Limit Tiers
Step 2: Implement Exponential Backoff with Jitter
Step 3: Add Idempotency Keys
Output
Error Handling
|