remote-retrieval-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/remote-retrieval-automation --openclawRemote Retrieval Automation via Rube MCP
Automate Remote Retrieval operations through Composio's Remote Retrieval toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/remote_retrieval
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Remote Retrieval connection via
RUBE_MANAGE_CONNECTIONSwith toolkitremote_retrieval - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitremote_retrieval - 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: "Remote Retrieval 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 Remote Retrieval task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["remote_retrieval"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Remote Retrieval-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit remote_retrieval |
| 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/remote-retrieval-automation/SKILL.mdView on GitHub Overview
Automate Remote Retrieval operations through Composio's Rube MCP toolkit. Always search tools first to get current tool schemas, ensuring inputs stay up-to-date before execution. This skill streamlines connecting to Remote Retrieval and running tools safely.
How This Skill Works
The workflow relies on RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas, then uses RUBE_MANAGE_CONNECTIONS to activate the remote_retrieval toolkit. Once a tool slug is chosen, RUBE_MULTI_EXECUTE_TOOL runs with the required arguments and a memory payload, guided by the discovered schema and session ID. Always ensure the connection is ACTIVE and include the memory field, as documented by the core workflow.
When to Use It
- Setting up a new Remote Retrieval workflow and verifying the Rube MCP connection is ACTIVE
- Discovering tools first to fetch current schemas before selecting a tool slug
- Executing a discovered tool with the correct arguments and memory payload
- Reusing session IDs within related Remote Retrieval tasks to maintain context
- Handling pagination tokens during tool discovery and continuing to fetch until complete
Quick Start
- Step 1: Verify RUBE MCP is available by adding the MCP server (https://rube.app/mcp) and calling RUBE_SEARCH_TOOLS
- Step 2: Establish a connection with RUBE_MANAGE_CONNECTIONS using toolkit 'remote_retrieval' and ensure status is ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory
Best Practices
- Always call RUBE_SEARCH_TOOLS before any execution to get up-to-date tool schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
- Use exact field names and types from the search results; avoid hardcoding slugs
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
- Reuse session IDs within a workflow and fetch new ones only for new workflows
Example Use Cases
- Discover tools with RUBE_SEARCH_TOOLS for Remote Retrieval operations, then execute a selected tool slug with the proper arguments and memory
- Connect to the Remote Retrieval toolkit via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status before executing
- Run a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the correct tool_slug and memory payload
- Use RUBE_REMOTE_WORKBENCH to perform bulk Remote Retrieval operations via run_composio_tool()
- Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to review schemaRef before integration
