brightdata-automation

Automate Brightdata operations through Rube MCP toolkits for data collection and management workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill brightdata-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brightdata-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/brightdata-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill brightdata-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Brightdata infrastructure by providing a standardized, automated interface for tool discovery, connection management, and execution of data operations.

Core Features & Use Cases

  • Automated Tool Discovery: Dynamically fetch current tool schemas and execution plans via Rube MCP to ensure compatibility.
  • Connection Lifecycle Management: Verify and maintain active Brightdata connections to prevent execution failures.
  • Multi-Tool Execution: Orchestrate complex workflows by chaining multiple Brightdata tools within a single session.

Quick Start

Use the brightdata-automation skill to discover available tools and execute a data collection task for my target website.

Frequently Asked Questions about brightdata-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Brightdata tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve current tool slugs, input schemas, and recommended execution plans for your Brightdata tasks.

How do I verify my Brightdata connection status?

Use the RUBE_MANAGE_CONNECTIONS function with the 'brightdata' toolkit parameter to check if your connection is currently ACTIVE before attempting any tool execution.

Can I reuse session IDs for multiple tasks?

Yes, you should reuse session IDs within a single logical workflow to maintain state, but generate new session IDs when starting entirely new, unrelated automation tasks.

What should I do if tool execution fails?

First, verify your connection status using RUBE_MANAGE_CONNECTIONS. If active, re-run RUBE_SEARCH_TOOLS to ensure your tool slugs and arguments still match the latest schema requirements.