Do I always need to call RUBE_SEARCH_TOOLS before executing a Smartproxy tool?

Yes. It fetches the current tool slugs and input schemas to avoid hardcoding.

How do I ensure the Smartproxy connection is ready?

Call RUBE_MANAGE_CONNECTIONS for the 'smartproxy' toolkit and verify the status is ACTIVE before any execution.

What if tool schemas change or I get a mismatch?

RUBE_SEARCH_TOOLS should be re-run to obtain updated slugs and field names; always use the provided memory object in RUBE_MULTI_EXECUTE_TOOL.

smartproxy-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Smartproxy Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/smartproxy

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Smartproxy connection via RUBE_MANAGE_CONNECTIONS with toolkit smartproxy
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 smartproxy
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: "Smartproxy 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 Smartproxy task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["smartproxy"]
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 Smartproxy-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `smartproxy`
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/smartproxy-automation/SKILL.mdView on GitHub

Overview

Automate Smartproxy operations through Composio's Smartproxy toolkit via Rube MCP. It orchestrates tool discovery, confirms an ACTIVE connection, and executes tool calls using up-to-date schemas. Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and arguments.

How This Skill Works

Discover available tools with RUBE_SEARCH_TOOLS for your Smartproxy use_case; verify the Smartproxy connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE; execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including memory and session_id.

When to Use It

Setting up automated Smartproxy workflows with up-to-date tool schemas
Running a Smartproxy operation after a schema update
Verifying an ACTIVE connection before executing any workflow
Reusing session IDs across a multi-step workflow for consistency
Performing bulk Smartproxy actions with RUBE_REMOTE_WORKBENCH when needed

Quick Start

Step 1: Add the rube MCP endpoint (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_MANAGE_CONNECTIONS for toolkit 'smartproxy' and confirm the connection status is ACTIVE
Step 3: Run RUBE_SEARCH_TOOLS to discover the tool slugs, then execute a selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from tool search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and manage pagination tokens when listing tools

Example Use Cases

Discover Smartproxy tools with RUBE_SEARCH_TOOLS and execute a chosen tool slug with proper arguments
Establish an ACTIVE Smartproxy connection using RUBE_MANAGE_CONNECTIONS before running a tool
Create a multi-step workflow that reuses a session_id across steps
Perform bulk actions by invoking multiple tools via RUBE_REMOTE_WORKBENCH.run_composio_tool
Update automation promptly after RUBE_SEARCH_TOOLS shows new tool schemas and adjust slugs accordingly

Frequently Asked Questions

Add this skill to your agents