sendfox-automation
by ComposioHQsendfox-automation automates Sendfox operations through Composio Rube MCP. Use it to discover current Sendfox tool schemas, verify an ACTIVE connection, and execute approved email campaign or contact workflows safely.
This skill scores 68/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a complete Sendfox automation package. Directory users get enough information to understand when to install it, how an agent should trigger Rube tool discovery, and what connection prerequisites are required, but they should expect limited bundled examples and little task-specific operational depth.
- Valid skill frontmatter clearly declares the `sendfox-automation` purpose and `rube` MCP requirement.
- Prerequisites and setup steps explain how to connect Rube MCP, manage the Sendfox connection, and verify ACTIVE status before use.
- The skill repeatedly instructs agents to call `RUBE_SEARCH_TOOLS` first, which should reduce schema drift and improve correct tool triggering.
- Execution depends on external Rube MCP discovery and an active Sendfox connection; the skill does not include local scripts or bundled references.
- Workflow guidance is mostly pattern-based rather than task-specific, so users may still need to infer exact Sendfox operations after tool discovery.
Overview of sendfox-automation skill
What sendfox-automation does
sendfox-automation is a Claude skill for automating Sendfox email marketing tasks through Composio’s Rube MCP server. Instead of hard-coding Sendfox API calls, the skill instructs the agent to discover the current Sendfox tool schemas with RUBE_SEARCH_TOOLS, verify the Sendfox connection, and then execute the right Rube tool for the requested email campaign or contact-management task.
Best fit for Sendfox campaign operators
This sendfox-automation skill is most useful if you already use Sendfox and want an AI agent to help with operational work such as finding available Sendfox actions, preparing workflow steps, managing connection status, or executing supported Sendfox operations through Composio. It fits marketers, founders, newsletter operators, and automation builders who want Claude to act inside a connected tool environment rather than only draft email copy.
Main differentiator: schema discovery first
The important design choice is that the skill tells the agent to search available tools before taking action. That matters because MCP tool schemas can change, and Sendfox capabilities exposed through Rube may differ from what a user assumes. The skill is therefore more reliable than a static prompt that guesses parameter names, but it still depends on the live Rube MCP connection and an active Sendfox authorization.
What to inspect before installing
The repository path is composio-skills/sendfox-automation in ComposioHQ/awesome-claude-skills. The main file to read is SKILL.md; there are no bundled scripts, examples, metadata files, or reference folders in the current skill directory. That makes the skill lightweight, but it also means you should expect to supply your own campaign goals, audience details, approval rules, and Sendfox account context.
How to Use sendfox-automation skill
sendfox-automation install and MCP setup
Install the skill from the Composio skill collection with npx skills add ComposioHQ/awesome-claude-skills --skill sendfox-automation. The skill requires Rube MCP, so your Claude-compatible client must have https://rube.app/mcp configured as an MCP server. After setup, confirm RUBE_SEARCH_TOOLS is available, then use RUBE_MANAGE_CONNECTIONS with toolkit sendfox to connect or verify the Sendfox account. Do not ask the agent to run Sendfox actions until the connection status is ACTIVE.
Inputs the skill needs from you
For good sendfox-automation usage, provide the business goal, the exact Sendfox object or workflow you want changed, and the safety constraints. A weak prompt is: “Automate my newsletter.” A stronger prompt is: “Use sendfox-automation to discover current Sendfox tools, verify the Sendfox connection, then prepare a workflow to add new leads from my launch list to the correct Sendfox list. Do not send any campaign or email without showing the proposed action, target list, required fields, and asking for approval.”
Recommended workflow for Email Campaigns
For sendfox-automation for Email Campaigns, treat the skill as an operations layer, not just a copywriter. Start by asking it to call RUBE_SEARCH_TOOLS for your specific use case, such as list management, campaign creation, contact lookup, or email sending. Next, have it summarize the returned tool slugs, required fields, and risks. Then provide campaign-specific details: list name, segment, sender identity, subject line, draft body, scheduling preference, suppression rules, and approval threshold. Only after review should the agent execute the selected Rube action.
Files and commands to read first
Read SKILL.md before use because it contains the core sequence: discover tools, check connection, execute workflow, and handle schema changes. There is no separate README.md or helper script in this skill directory, so the practical source of truth is the live result from RUBE_SEARCH_TOOLS. If the agent suggests a Sendfox parameter before discovering tools, redirect it: “Search current Sendfox tools first and use only the schema returned by Rube.”
sendfox-automation skill FAQ
Is sendfox-automation beginner friendly?
Yes, if you are comfortable connecting an MCP server and authorizing Sendfox through Composio. It is not a one-click Sendfox tutorial. Beginners should start with read-only or low-risk tasks, such as discovering available tools and checking connection status, before asking the agent to create contacts, modify lists, or prepare campaign sends.
How is it better than an ordinary Claude prompt?
A normal prompt can draft campaign ideas or explain Sendfox concepts, but it cannot reliably know the current Rube tool schema. The sendfox-automation skill gives Claude a repeatable operating pattern: search tools first, verify the Sendfox connection, use the returned schema, and avoid guessing. That reduces failed calls and makes automation safer.
When should I not use this skill?
Do not use it if you do not have a Sendfox account, cannot connect Rube MCP, or need a fully documented local script with tests and fixtures. The skill is also not the right place to store compliance policy, brand voice, or campaign approval rules; you should provide those in your prompt or maintain them elsewhere.
Does it send emails automatically?
It can help operate Sendfox through available Rube tools, but whether an email is sent depends on the tools discovered and the instructions you approve. For production campaigns, explicitly require a preview and confirmation step before any send, schedule, import, delete, or bulk update action.
How to Improve sendfox-automation skill
Give stronger campaign and account context
The fastest way to improve sendfox-automation results is to provide concrete context: list names, contact fields, campaign objective, audience segment, required exclusions, desired outcome, and what must never happen. For example, specify “update only contacts tagged webinar-2026, do not create duplicate contacts, and ask before changing subscription status.”
Prevent common failure modes
The main failure mode is schema guessing. If the agent tries to infer tool names or parameters, tell it to rerun RUBE_SEARCH_TOOLS for the exact use case. Another risk is acting before authorization is complete, so require a RUBE_MANAGE_CONNECTIONS check. For bulk operations, ask for a dry-run summary: target count, fields affected, irreversible actions, and rollback options.
Iterate after the first output
After the first plan, do not approve immediately. Ask the agent to compare the plan against the discovered schema, identify missing required fields, and separate safe read operations from write operations. For email campaign work, request a final approval checklist covering audience, subject, content, timing, unsubscribe compliance, and whether the action sends now or only creates a draft.
Extend sendfox-automation for your team
Because the current repository includes only SKILL.md, teams can improve the sendfox-automation skill by adding local operating rules outside the upstream skill: campaign approval policy, naming conventions, list hygiene rules, sample prompts, and brand-safe send procedures. Keep those additions separate from live tool schemas; the skill’s best practice is still to discover the current Rube Sendfox tools at runtime.