What do I need to start using brightdata-automation?

An active Rube MCP connection (RUBE_SEARCH_TOOLS) and an active Brightdata connection via RUBE_MANAGE_CONNECTIONS with the brightdata toolkit; the MCP endpoint must be configured.

Can I reuse a session across steps?

Yes, reuse session IDs within a workflow to preserve context; generate a new session for new runs.

How do I handle changing tool schemas?

Always search for tools first (RUBE_SEARCH_TOOLS) and use the returned slugs and input schemas; do not hardcode.

brightdata-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/brightdata-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Brightdata Automation via Rube MCP

Automate Brightdata operations through Composio's Brightdata toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/brightdata

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Brightdata connection via RUBE_MANAGE_CONNECTIONS with toolkit brightdata
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit brightdata
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Brightdata operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Brightdata task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["brightdata"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Brightdata-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `brightdata`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/brightdata-automation/SKILL.mdView on GitHub

Overview

This skill automates Brightdata operations through Composio's Brightdata toolkit using Rube MCP. It requires discovering current tool schemas with RUBE_SEARCH_TOOLS before actions and managing Brightdata connections with RUBE_MANAGE_CONNECTIONS. This keeps automations aligned with live tool definitions and improves reliability.

How This Skill Works

The workflow starts by querying available tools with RUBE_SEARCH_TOOLS to retrieve tool slugs and input schemas. It then checks the Brightdata connection status via RUBE_MANAGE_CONNECTIONS and proceeds only when ACTIVE. Finally, it executes a selected tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact arguments from the schema, memory payload, and the active session_id.

When to Use It

When you need up-to-date Brightdata tool schemas before running tasks.
When establishing or renewing a Brightdata connection using the toolkit.
When you want to execute a discovered tool with the exact required arguments.
When you want to reuse a session ID across a multi-step workflow.
When performing bulk Brightdata operations or chaining multiple tools via the remote bench.

Quick Start

Step 1: Ensure Rube MCP is connected and fetch current Brightdata tool schemas with RUBE_SEARCH_TOOLS.
Step 2: Connect or verify an ACTIVE Brightdata connection using RUBE_MANAGE_CONNECTIONS with toolkit 'brightdata'.
Step 3: Execute the discovered tool via RUBE_MULTI_EXECUTE_TOOL, including memory and the session_id from previous steps.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs.

Example Use Cases

Discover Brightdata operation tools with RUBE_SEARCH_TOOLS, then execute a chosen task after confirming the connection is ACTIVE.
Set up a new Brightdata connection using RUBE_MANAGE_CONNECTIONS and run a data collection workflow.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before execution.
Perform bulk Brightdata actions via RUBE_REMOTE_WORKBENCH and run_composio_tool with a prepared memory payload.
Run an end-to-end pipeline: RUBE_SEARCH_TOOLS -> RUBE_MANAGE_CONNECTIONS -> RUBE_MULTI_EXECUTE_TOOL for a discovered slug.

Frequently Asked Questions

Add this skill to your agents