conversion-tools-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/conversion-tools-automation --openclawConversion Tools Automation via Rube MCP
Automate Conversion Tools operations through Composio's Conversion Tools toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/conversion_tools
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Conversion Tools connection via
RUBE_MANAGE_CONNECTIONSwith toolkitconversion_tools - 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 toolkitconversion_tools - 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: "Conversion Tools 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 Conversion Tools task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["conversion_tools"]
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 Conversion Tools-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit conversion_tools |
| 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/conversion-tools-automation/SKILL.mdView on GitHub Overview
Automates Conversion Tools operations through Composio's Rube MCP, enabling discovery, connection management, and execution against current tool schemas. It emphasizes always querying available tools first to stay aligned with the latest workflows.
How This Skill Works
The workflow begins by calling RUBE_SEARCH_TOOLS to fetch available tools and their input schemas. It then validates an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the conversion_tools toolkit, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using schema-compliant arguments and including memory. This enables automated, repeatable conversions without hardcoding tool slugs.
When to Use It
- Starting a new Conversion Tools task when schemas may have changed.
- Ensuring the conversion_tools connection is ACTIVE before executing any tool.
- Discovering available tools for a specific conversion use case before calling tools.
- Automating multiple tool executions in a single session with memory handling.
- Handling pagination to fetch all available tool schemas and avoid missing options.
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS responds to fetch current conversion tool schemas.
- Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit 'conversion_tools' and ensure the status is ACTIVE.
- Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing schema-compliant arguments and memory: {}.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the search results.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new ones for new tasks.
Example Use Cases
- Discover a tool with RUBE_SEARCH_TOOLS for a conversion, then run it with RUBE_MULTI_EXECUTE_TOOL using the slug and returned arguments.
- Connect to conversion_tools with RUBE_MANAGE_CONNECTIONS and execute a tool after confirming ACTIVE.
- Run a sequence of conversions in one session, reusing the same session_id to save overhead.
- Fetch all tool schemas by handling pagination tokens with RUBE_SEARCH_TOOLS until complete.
- Bulk process: use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk conversions.
