home / skills / composiohq / awesome-claude-skills / smartproxy-automation

smartproxy-automation skill

/smartproxy-automation

This skill automates Smartproxy tasks via Rube MCP, discovering current tool schemas first to ensure up-to-date executions.

npx playbooks add skill composiohq/awesome-claude-skills --skill smartproxy-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: smartproxy-automation
description: "Automate Smartproxy tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Smartproxy Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/smartproxy](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `smartproxy`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Smartproxy tasks through Composio’s Smartproxy toolkit using Rube MCP. It guides discovery of current tool schemas, manages Smartproxy connections, and executes toolkit actions reliably. The workflow enforces live schema checks and connection validation to avoid breakage.

How this skill works

The skill always starts by calling RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It then verifies or establishes a Smartproxy connection via RUBE_MANAGE_CONNECTIONS and runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, supplying schema-compliant arguments and an explicit memory object. Session IDs are reused within a workflow and regenerated for new workflows; pagination tokens are honored when fetching large results.

When to use it

  • Automate Smartproxy provisioning, configuration, or analytics tasks.
  • Run batch or bulk proxy operations that require Composio toolkit orchestration.
  • Ensure safe execution when tool schemas may have changed since last run.
  • Integrate Smartproxy actions into larger Claude or agent-driven workflows.
  • Perform repeatable workflows that must validate connection status before execution.

Best practices

  • Always call RUBE_SEARCH_TOOLS first—never hardcode tool slugs or request shapes.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the smartproxy toolkit before running tools.
  • Supply exact field names and types from the returned schemas; follow required/optional flags.
  • Always include a memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls.
  • Reuse a session ID for a single workflow and generate new session IDs for separate workflows.
  • Watch for pagination tokens and continue fetching until responses are complete.

Example use cases

  • Discover available Smartproxy actions and run a one-off IP rotation or test endpoint.
  • Bulk-update proxy rules across accounts using RUBE_REMOTE_WORKBENCH and run_composio_tool().
  • Embed Smartproxy setup as part of a CI flow: connect, validate ACTIVE status, then provision resources.
  • Automate monitoring operations that pull paginated logs or metrics from the toolkit and aggregate results.
  • Create an agent that queries tool schemas dynamically and builds form inputs for downstream automation.

FAQ

Why must I call RUBE_SEARCH_TOOLS before executing anything?

Tool schemas and slugs change frequently; RUBE_SEARCH_TOOLS returns current schemas and recommended plans to ensure your inputs and tool selections are valid.

What happens if the Smartproxy connection is not ACTIVE?

RUBE_MANAGE_CONNECTIONS will return an auth link or instructions. Complete the auth flow and confirm ACTIVE status before running tool executions to avoid failures.