$ ~/registry/skill/composiohq-composio-skills-smartproxy-automation

SKILL

smartproxy-automation

Name: smartproxy-automation
Author: Composio

Automate Smartproxy workflows via Rube MCP for proxy search and task execution.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially an open-source prompt/instruction set, with no direct local code execution, no explicit system privilege requests, and no built-in secret requirement. The main consideration is its reliance on remote Rube MCP and Smartproxy connection flows, so actual data egress and authorization boundaries depend on those external services.

CredentialsCaution

The material says the skill itself needs “no API keys,” but real use requires activating a `smartproxy` connection via `RUBE_MANAGE_CONNECTIONS` and completing a returned auth link, implying credentials/authorization are likely delegated between Rube/Composio and Smartproxy. No explicit credential-abuse red flag is shown, but there is still normal third-party token handling and misconfiguration risk.

Network egressCaution

The README explicitly requires connecting to the remote MCP endpoint `https://rube.app/mcp` and executing actions through Composio’s Smartproxy toolkit; therefore user inputs, tool arguments, session IDs, and related operational data may be sent through the Rube/Composio/Smartproxy path. The document does not disclose more detailed data flows or unrelated endpoints, so this appears to be ordinary egress aligned with the stated functionality.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description that mainly instructs use of existing MCP tools (such as `RUBE_SEARCH_TOOLS` and `RUBE_MULTI_EXECUTE_TOOL`), with no indication that the skill itself starts local processes, runs scripts, or gains shell/system-level execution.

Data accessLow risk

The material does not show the skill directly reading or writing local files, databases, the clipboard, or other host resources; its data access appears limited to Smartproxy-related operations via remote MCP tools. Any broader business-data exposure would depend on the external MCP/toolchain permissions, not on the skill text itself.

Supply chainLow risk

The source is a GitHub open-source repository with very strong community adoption (64.7k stars), which materially lowers supply-chain risk; the visible content is also just auditable README/prompt material. Remaining caveats are the unspecified license and unknown maintenance status, so the upstream repository and actual dependent services should still be verified for ongoing maintenance.

Recommendations

Before enabling it, verify the privacy policy, data retention, and authorization scope of Rube MCP, Composio, and Smartproxy.
Use a least-privilege Smartproxy account/connection and regularly review or revoke third-party authorizations that are no longer needed.
Avoid sending unnecessary sensitive data in tool arguments, especially customer data, internal identifiers, and bulk configuration content.
Prefer pinning a trusted repository version or snapshot, and additionally verify the real maintenance status of `rube.app/mcp` and the related toolchain.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "smartproxy-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/smartproxy-automation/SKILL.md
2. Save it as ~/.claude/skills/smartproxy-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Agenty tasks via Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_