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

SKILL

enginemailer-automation

Name: enginemailer-automation
Author: Composio

Automate Enginemailer marketing email workflows through Rube MCP with current tool schemas.

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 a prompt/documentation-style wrapper from a public GitHub source with strong community adoption, and it does not itself declare local execution, file access, or built-in secret requirements. Caution is still warranted because its intended use is to connect through Rube MCP and drive Enginemailer operations, so actual data egress, authorization scope, and execution behavior depend on the connected Rube/Composio toolchain.

CredentialsCaution

The material says the skill itself needs 'no API keys', but the README explicitly requires establishing an ACTIVE Enginemailer connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link. So while the skill does not directly collect secrets, it still depends on third-party OAuth/connection credentials, with ordinary risks around account authorization and linking the wrong workspace.

Network egressCaution

The README requires adding the remote MCP endpoint `https://rube.app/mcp` and using the Composio/Enginemailer toolchain for discovery, connection, and execution; task arguments, session information, and potentially email-operation data would be sent to that remote service as part of the workflow. No clearly unrelated or hidden exfiltration endpoint is stated, but the actual egress scope depends on the Rube/Composio backend.

Code executionLow risk

Based on the provided material, this is a prompt/instruction-style skill that does not declare starting local processes, running scripts, or invoking system-level capabilities; it mainly instructs the user to call MCP tools. From the skill text itself, there is no direct request for code execution privileges.

Data accessCaution

The skill itself does not declare reading local files or broad access to local machine data, but it is intended to automate Enginemailer operations and supports session reuse, bulk execution, and remote workbench calls, which would typically involve email-related business data. The material does not define a least-privilege boundary, so the effective data scope depends on the authorized Enginemailer account and the capabilities exposed by Rube.

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; the object is also classified as prompt-only by the system. The missing license declaration and unknown maintenance status leave some governance gaps, but the available material does not show closed-source delivery, malicious installation steps, or injection-like red flags.

Recommendations

Only connect to `https://rube.app/mcp` if you trust the Rube/Composio service, and review its privacy and data-handling practices.
Use a least-privilege Enginemailer account or a test workspace for authorization instead of granting broad production access.
Verify the tool list and parameter meanings returned by `RUBE_SEARCH_TOOLS` before execution to avoid mistakes caused by changing schemas.
Regularly review and revoke Rube/Enginemailer connection grants and sessions that are no longer needed.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Enginemailer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/enginemailer

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["enginemailer"]
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 Enginemailer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `enginemailer`
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 SMTP2GO email sending and management tasks through Rube MCP.

ComposioGet→

$ loading_