verifiedemail-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/verifiedemail-automation --openclawVerifiedemail Automation via Rube MCP
Automate Verifiedemail operations through Composio's Verifiedemail toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/verifiedemail
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Verifiedemail connection via
RUBE_MANAGE_CONNECTIONSwith toolkitverifiedemail - 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 toolkitverifiedemail - 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: "Verifiedemail 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 Verifiedemail task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["verifiedemail"]
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 Verifiedemail-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit verifiedemail |
| 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/verifiedemail-automation/SKILL.mdView on GitHub Overview
This skill automates Verifiedemail operations through Composio's Verifiedemail toolkit using the Rube MCP integration. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE Verifiedemail connection with RUBE_MANAGE_CONNECTIONS, and executing tools via RUBE_MULTI_EXECUTE_TOOL.
How This Skill Works
The workflow begins by discovering tools with RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas. Then it validates the connection with RUBE_MANAGE_CONNECTIONS and executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing memory and session_id per the discovered schema. Always reference live tool schemas rather than hardcoding values. The discovery step returns tool slugs, input schemas, recommended execution plans, and known pitfalls.
When to Use It
- When you need to run a Verifiedemail workflow without manual steps and want the latest tool schemas.
- When setting up a new Verifiedemail integration and must verify RUBE_SEARCH_TOOLS shows current tools.
- When you want to ensure the Verifiedemail connection is ACTIVE before any workflow.
- When you need to execute a discovered tool.slug with exact schema-compliant arguments via RUBE_MULTI_EXECUTE_TOOL.
- When you want to reuse a session_id across steps and handle pagination as you fetch tools.
Quick Start
- Step 1: 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.
- Step 2: Verify MCP availability by confirming RUBE_SEARCH_TOOLS responds and lists Verifiedemail tools.
- Step 3: Manage the connection with RUBE_MANAGE_CONNECTIONS (toolkit: verifiedemail) and then run tools with RUBE_MULTI_EXECUTE_TOOL after ensuring ACTIVE.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens when listing tools.
Example Use Cases
- Discover tools for Verifiedemail and execute a 'send_verification_email' task with recipient, subject, and template using RUBE_MULTI_EXECUTE_TOOL.
- Check verification status via a 'check_status' tool after sending verification.
- Run multiple Verifiedemail tasks in a single session by reusing session_id and memory.
- Set up or refresh Verifiedemail connection via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE before automation.
- If tool schemas change, re-run RUBE_SEARCH_TOOLS before executing any tools to avoid broken slugs.
