npx skills add https://github.com/composiohq/awesome-claude-skills
ranbot-ai/awesome-skills
proxiedmail-automation
Automate Proxiedmail tasks via Rube MCP (Composio). Always search tools first for current schemas.
Installation
npx skills add ranbot-ai/awesome-skills --skill proxiedmail-automation
Also in this package
Other skills from ranbot-ai/awesome-skills · top by installs.
npx skills add ranbot-ai/awesome-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md3,140 B -
docs
SUMMARY.md128 B
History
- First seen on skills.sh
- First recorded snapshot · 1 installs
SKILL.md
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 (RUBESEARCHTOOLS available)
- Active Proxiedmail connection via
RUBEMANAGECONNECTIONSwith toolkitproxiedmail - Always call
RUBESEARCHTOOLSfirst 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
RUBESEARCHTOOLSresponds - Call
RUBEMANAGECONNECTIONSwith toolkitproxiedmail - 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
RUBESEARCHTOOLS - Check connection: Verify
RUBEMANAGECONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBEMULTIEXECUTE_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 | RUBESEARCHTOOLS with Proxiedmail-specific use case |
| Connect | RUBEMANAGECONNECTIONS with toolkit proxiedmail |
| Execute | RUBEMULTIEXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBEREMOTEWORKBENCH with runcomposiotool() |
| Full schema | RUBEGETTOOL_SCHEMAS for tools with schemaRef |
Powered by Composio