What is proxiedmail-automation?

A skill to automate Proxiedmail tasks using Composio's toolkit through Rube MCP, with schema-first discovery.

What are the prerequisites?

Rube MCP must be connected, a Proxiedmail connection active via RUBE_MANAGE_CONNECTIONS with the proxiedmail toolkit, and always call RUBE_SEARCH_TOOLS before workflows.

What if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas; avoid hardcoding slugs or arguments.

proxiedmail-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Proxiedmail Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/proxiedmail

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["proxiedmail"]
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 Proxiedmail-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `proxiedmail`
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/proxiedmail-automation/SKILL.md

View on GitHub

Overview

Automate Proxiedmail operations using Composio's Proxiedmail toolkit through Rube MCP. It requires an active Rube MCP connection and a Proxiedmail connection configured with RUBE_MANAGE_CONNECTIONS, plus always refreshing tool schemas with RUBE_SEARCH_TOOLS before running workflows.

How This Skill Works

Begin by discovering available Proxiedmail tools with RUBE_SEARCH_TOOLS, then verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. When ready, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the required arguments, including a memory object and a session_id to support continuity.

When to Use It

When you need up-to-date tool schemas before running Proxiedmail tasks
When establishing a new Proxiedmail integration via Rube MCP
When validating that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
When performing multi-step Proxiedmail workflows or bulk operations
When troubleshooting tool schemas or session handling by re-searching tools

Quick Start

Step 1: Add Rube MCP endpoint via https://rube.app/mcp to your client
Step 2: Verify connectivity with RUBE_SEARCH_TOOLS and activate proxiedmail via RUBE_MANAGE_CONNECTIONS
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
Use exact field names and types from the search results
Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow and handle pagination when available

Example Use Cases

Discover available Proxiedmail tools and run a task with the discovered tool slug
Set up a new Proxiedmail connection and execute a workflow once ACTIVE
Run a multi-tool workflow by selecting discovered tools and reusing the session
Fetch tool schemas repeatedly to handle changes in slugs and fields (pagination tokens)
Debug failures by re-searching tools and correcting arguments to match the schema

Frequently Asked Questions

Add this skill to your agents