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

SKILL

proxiedmail-automation

Name: proxiedmail-automation
Author: Composio

Automate Proxiedmail email tasks and workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt wrapper with relatively strong source credibility, and no clear red flags for local execution or local file access. The main concern is that it relies on remote Rube MCP and a Proxiedmail connection, so actual data access and egress occur through those external service paths.

CredentialsCaution

The material says the skill itself needs no API key, but it does require establishing an ACTIVE `proxiedmail` connection via `RUBE_MANAGE_CONNECTIONS` and completing an external authorization flow; this implies third-party account tokens or session grants. This is a normal integration risk, with no explicit signs of credential abuse.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing actions through the Composio/Proxiedmail toolchain; user requests and related business data may therefore be sent to Rube/Composio/Proxiedmail. This is a clear egress path, but the endpoints appear related to the stated function, with no evidence of unrelated or covert exfiltration.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no executable scripts, install commands, or local process-launch steps; it also does not claim direct access to local system capabilities. No local code execution surface is evident.

Data accessCaution

The skill itself does not declare local file or system access, but its purpose is to 'Automate Proxiedmail operations' and it requires connecting an external Proxiedmail account; therefore it is expected to access data within that account scope. The material does not show excessive local over-privilege beyond the stated purpose.

Supply chainLow risk

The source is a public open-source GitHub repository with strong community adoption (64.7k stars), which are clear risk-reducing signals. Although the license is undeclared and maintenance status is unknown, the current material does not show closed-source opacity, untrusted origin, or obvious supply-chain injection red flags.

Recommendations

Before adoption, verify the privacy policies, data retention practices, and audit logging capabilities of `rube.app/mcp`, Composio, and Proxiedmail.
Grant only the minimum permissions needed for the `proxiedmail` connection, and review/revoke authorizations regularly.
In a controlled environment, test `RUBE_SEARCH_TOOLS` and the actual tool schemas with sanitized or test data before using real account data.
Further verify repository maintenance activity, release history, and licensing before putting it into production workflows.

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 "proxiedmail-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/proxiedmail-automation/SKILL.md
2. Save it as ~/.claude/skills/proxiedmail-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Mailsoftly email tasks and workflows through Rube MCP.

ComposioGet→

$ loading_