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

SKILL

mailsoftly-automation

Name: mailsoftly-automation
Author: Composio

Automate Mailsoftly 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-style wrapper with no directly declared API keys or local execution, and its high community adoption is a positive trust signal. Main caution is that it depends on external Rube MCP/Composio connections and remote tool execution, so actual data egress and permissions depend on the underlying service and the connected Mailsoftly account.

CredentialsCaution

The material says the skill itself needs no keys, but it requires establishing a Mailsoftly connection via `RUBE_MANAGE_CONNECTIONS` and completing external auth, implying credentials are managed or brokered by Rube/Composio. No explicit credential-abuse red flag is shown, but third-party credential handling remains a caution.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing actions through the Composio/Mailsoftly toolchain, so task arguments, session IDs, connection state, and related business data are likely sent to that remote service. The endpoint appears aligned with the stated purpose, with no unrelated or unknown egress target, but normal remote data egress exists.

Code executionLow risk

Per the provided checks, this project is prompt-only; the material does not describe installing executables locally, running scripts, or invoking the system shell. Its role is to guide use of existing MCP tools rather than grant additional local code execution.

Data accessCaution

The skill is meant to automate Mailsoftly operations and can execute remote tools via `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, so accessible data depends on the permissions of the connected Mailsoftly account. There is no indication of local filesystem access or unrelated permissions, but normal read/write or operational access to Mailsoftly business data should be expected.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), which is a strong positive signal; the material also matches a skill-wrapper/documentation pattern and is reasonably auditable. Missing license information and unknown maintenance status add minor uncertainty, but not enough to make it high risk.

Recommendations

Enable it only when Mailsoftly automation is needed, and authorize with a least-privileged Mailsoftly account.
Before connecting to `https://rube.app/mcp`, review Rube/Composio privacy, data retention, and credential-handling practices.
Avoid sending highly sensitive email content or customer data through this path unless compliance and encryption controls are confirmed.
Prefer pinned/auditable versions and keep watching the upstream repository and underlying MCP service for maintenance changes.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Mailsoftly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailsoftly

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mailsoftly"]
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 Mailsoftly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mailsoftly`
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 Bigmailer email marketing tasks and workflows through Rube MCP.

ComposioGet→

$ loading_