mailsoftly-automation
Automates Mailsoftly tasks by integrating with the Rube MCP/Composio toolkit.
Install
mkdir -p .claude/skills/mailsoftly-automation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16968" && unzip -o skill.zip -d .claude/skills/mailsoftly-automation && rm skill.zipInstalls to .claude/skills/mailsoftly-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 Mailsoftly tasks via Rube MCP (Composio). Always search tools first for current schemas. Use when you need help with mailsoftly automation.Key capabilities
- →Search for current Mailsoftly tool schemas
- →Manage Mailsoftly connections via Rube MCP
- →Execute Mailsoftly operations using discovered tools
- →Verify Rube MCP availability and connection status
- →Handle schema compliance for tool arguments
How it works
The skill uses RUBE_SEARCH_TOOLS to discover Mailsoftly tool schemas, RUBE_MANAGE_CONNECTIONS to ensure an active connection, and RUBE_MULTI_EXECUTE_TOOL to perform Mailsoftly operations.
Inputs & outputs
When to use mailsoftly-automation
- →Automate email campaigns
- →Manage mailing lists
- →Execute email workflows
About this skill
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_CONNECTIONSwith toolkitmailsoftly - 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 toolkitmailsoftly - 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_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 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
When not to use it
- →When hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
- →When the Rube MCP is not connected
- →When the Mailsoftly connection is not active
Prerequisites
Limitations
- →Always search tools first for current schemas
- →Check connection status before running any workflows
- →Use exact field names and types from the search results for schema compliance
How it compares
This skill automates Mailsoftly tasks by dynamically discovering tool schemas and managing connections through Rube MCP, ensuring adaptability to schema changes and reliable execution, unlike static API calls.
Compared to similar skills
mailsoftly-automation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mailsoftly-automation (this skill) | 0 | 2mo | No flags | Intermediate |
| gmail-manager | 27 | 4mo | Review | Intermediate |
| mailchimp-automation | 2 | 4mo | No flags | Intermediate |
| action-creator | 2 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by anubhavg-icpl
View all by anubhavg-icpl →You might also like
gmail-manager
jeffvincent
Manage Gmail - send, read, search emails, manage labels and drafts. Use when user wants to interact with their Gmail account for email operations.
mailchimp-automation
sickn33
Automate Mailchimp email marketing including campaigns, audiences, subscribers, segments, and analytics via Rube MCP (Composio). Always search tools first for current schemas.
action-creator
anthropics
Creates user-specific one-click action templates that execute email operations when clicked in the chat interface. Use when user wants reusable actions for their specific workflows (send payment reminder to ACME Corp, forward bugs to engineering, archive old newsletters from specific sources).
gmcli
badlogic
Gmail CLI for searching emails, reading threads, sending messages, managing drafts, and handling labels/attachments.
convertkit-automation
Zidong-LLC
Automate ConvertKit (Kit) tasks via Rube MCP (Composio): manage subscribers, tags, broadcasts, and broadcast stats. Always search tools first for current schemas.
send-message
gitduk
Send a message to a Telegram chat via the Bot API directly. Self-contained — reads its own .env at the skill root and has no dependency on any Telegram plugin. Use when the user asks to push a Telegram notification to their phone, test the bot token, send from a hook or one-shot script, or 给 telegra