EM

emailable-automation

Automates Emailable operations using the Rube MCP (Composio) framework. Follows a discovery-first workflow to ensure schema compliance.

Install

mkdir -p .claude/skills/emailable-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11286" && unzip -o skill.zip -d .claude/skills/emailable-automation && rm skill.zip

Installs to .claude/skills/emailable-automation

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Automate Emailable tasks via Rube MCP (Composio). Always search tools first for current schemas.
96 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Discover available Emailable tools using RUBE_SEARCH_TOOLS
  • Manage Emailable API connections via RUBE_MANAGE_CONNECTIONS
  • Execute Emailable operations with RUBE_MULTI_EXECUTE_TOOL
  • Handle pagination in Emailable API responses
  • Utilize RUBE_REMOTE_WORKBENCH for bulk operations

How it works

The skill interacts with Composio's Emailable toolkit through Rube MCP, first discovering tools and verifying connections, then executing operations with schema-compliant arguments.

Inputs & outputs

You give it
A query for Emailable operations or connection management
You get back
Tool schemas, connection status, or execution results

When to use emailable-automation

  • Verify email addresses programmatically
  • Manage Emailable API connections
  • Retrieve email validation results for user registration workflows

About this skill

Emailable Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/emailable

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Emailable connection via RUBE_MANAGE_CONNECTIONS with toolkit emailable
  • 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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit emailable
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Emailable 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 Emailable task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["emailable"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Emailable-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit emailable
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

When not to use it

  • When tool schemas or arguments are hardcoded without prior discovery
  • When the Emailable connection status is not active
  • When session IDs are not reused within a workflow

Prerequisites

Rube MCP must be connectedActive Emailable connection via RUBE_MANAGE_CONNECTIONS

Limitations

  • Requires explicit tool discovery before execution
  • Demands active connection status verification
  • Enforces schema compliance for arguments

How it compares

This workflow ensures current tool schemas and active connections are verified before execution, unlike directly calling an API with potentially outdated information.

Compared to similar skills

emailable-automation side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
emailable-automation (this skill)03moNo flagsIntermediate
telegram-bot-builder1066moReviewIntermediate
reddit-api34moReviewIntermediate
juicebox-install-auth227dReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

reddit-api

alinaqi

Reddit API with PRAW (Python) and Snoowrap (Node.js)

334

juicebox-install-auth

jeremylongshore

Install and configure Juicebox SDK/CLI authentication. Use when setting up a new Juicebox integration, configuring API keys, or initializing Juicebox in your project. Trigger with phrases like "install juicebox", "setup juicebox", "juicebox auth", "configure juicebox API key".

28

lindy-sdk-patterns

jeremylongshore

Lindy AI SDK best practices and common patterns. Use when learning SDK patterns, optimizing API usage, or implementing advanced agent features. Trigger with phrases like "lindy SDK patterns", "lindy best practices", "lindy API patterns", "lindy code patterns".

14

windsurf-mcp-integration

jeremylongshore

Manage integrate MCP servers with Windsurf for extended capabilities. Activate when users mention "mcp integration", "model context protocol", "external tools", "mcp server", or "cascade tools". Handles MCP server configuration and integration. Use when working with windsurf mcp integration functionality. Trigger with phrases like "windsurf mcp integration", "windsurf integration", "windsurf".

14

groq-webhooks-events

jeremylongshore

Implement Groq webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Groq event notifications securely. Trigger with phrases like "groq webhook", "groq events", "groq webhook signature", "handle groq events", "groq notifications".

10

Search skills

Search the agent skills registry