toneden-automation
by ComposioHQtoneden-automation is a Claude skill for Toneden Workflow Automation through Composio Rube MCP. It guides agents to install the skill, connect Rube, search current Toneden tool schemas, verify authorization, and run workflows with fewer guessed inputs.
This skill scores 66/100, which makes it acceptable but limited for directory listing. Directory users can understand when to use it and how an agent should start Toneden automation through Rube MCP, but it provides relatively little Toneden-specific workflow substance beyond connection setup and tool discovery, so users should expect the live Rube schemas to carry much of the operational detail.
- Valid skill frontmatter with a clear automation target: Toneden operations through Composio's Rube MCP toolkit.
- Includes essential prerequisites and setup flow: connect Rube MCP, use RUBE_MANAGE_CONNECTIONS with toolkit "toneden", and confirm ACTIVE status before execution.
- Strong triggerability guardrail: repeatedly instructs agents to call RUBE_SEARCH_TOOLS first to retrieve current tool slugs, schemas, plans, and pitfalls.
- No support files, scripts, references, or README beyond SKILL.md, so adoption depends almost entirely on the brief in-file instructions.
- The guidance is mostly a generic Rube MCP/tool-discovery pattern and does not show concrete Toneden task examples or expected outputs.
Overview of toneden-automation skill
What toneden-automation is for
toneden-automation is a Claude skill for running Toneden workflows through Composio’s Rube MCP server. Its main job is not to hard-code one Toneden action, but to guide the agent to discover the current Toneden tool schema first, check authentication, and then execute the right Rube tool with fewer assumptions.
Best-fit users and workflows
This skill is best for users who already work with Toneden and want AI-assisted Workflow Automation for recurring platform tasks. It fits teams that need a Claude agent to inspect available Toneden operations, confirm an active connection, and run actions through Composio rather than manually navigating APIs or dashboards.
What makes this skill different
The key differentiator is its “search tools first” pattern. Instead of relying on stale parameter names, the toneden-automation skill instructs the agent to call RUBE_SEARCH_TOOLS before execution, then use RUBE_MANAGE_CONNECTIONS to verify Toneden access. That matters because MCP tool schemas can change, and a generic prompt may hallucinate tool names or inputs.
Adoption constraints to know
The skill depends on Rube MCP and an active Toneden connection. It does not include helper scripts, local code, reference files, or a standalone installer inside the skill folder. Install value comes from the workflow instructions in SKILL.md, so it is most useful in an MCP-enabled client where Rube tools are actually available.
How to Use toneden-automation skill
toneden-automation install context
To add the skill from the directory repository, use:
npx skills add ComposioHQ/awesome-claude-skills --skill toneden-automation
Then configure Rube MCP in your client by adding https://rube.app/mcp as an MCP server. The upstream skill says no API key is required for the server endpoint, but Toneden authorization still must be completed through Rube’s connection flow.
Required setup before running a task
Before asking for Toneden work, verify three things:
RUBE_SEARCH_TOOLSis available in the client.RUBE_MANAGE_CONNECTIONScan inspect toolkit connections.- The
tonedentoolkit connection isACTIVE.
A practical setup prompt is: “Use toneden-automation. First search Rube tools for Toneden campaign operations, then check RUBE_MANAGE_CONNECTIONS for toolkit toneden. If the connection is not active, stop and give me the auth link or next connection step.”
Turning a rough goal into a strong prompt
Weak prompt: “Automate my Toneden task.”
Stronger prompt: “Use toneden-automation for Workflow Automation. I want to perform this Toneden task: [describe the exact action]. First call RUBE_SEARCH_TOOLS for that use case and use the returned schema only. Check the Toneden connection status before execution. If required fields are missing, ask me before calling the final tool.”
This improves output because the agent has a specific use case, a discovery requirement, a connection check, and a rule against guessing missing parameters.
Files to inspect first
Start with composio-skills/toneden-automation/SKILL.md. It contains the full operational pattern: prerequisites, Rube MCP setup, tool discovery, connection checks, and execution flow. There are no bundled scripts/, resources/, references/, or README.md files in the skill folder, so the main source of truth is the skill file plus the live schemas returned by Rube.
toneden-automation skill FAQ
Is toneden-automation useful without Rube MCP?
No. The skill is designed around Rube MCP tools, especially RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. Without those tools available in your AI client, toneden-automation becomes guidance text rather than an executable automation workflow.
How is this better than an ordinary Toneden prompt?
An ordinary prompt may ask the model to infer a Toneden API shape from memory. The toneden-automation skill instead pushes the agent to discover current Composio tool schemas before acting. That reduces failed calls caused by outdated field names, missing required inputs, or unavailable operations.
Is this suitable for beginners?
Yes, if the beginner can connect Rube MCP and follow an authorization link for Toneden. It is not a no-code tutorial for Toneden itself. Users still need to know what Toneden task they want performed and be ready to provide account-specific details when the discovered schema requires them.
When should I not use this skill?
Do not use it for tasks outside Toneden, for clients that cannot run MCP tools, or for workflows where you need local scripts, batch files, or custom business logic included in the repository. It is also a poor fit if you need guaranteed dry-run behavior and the discovered Rube tool does not provide a safe preview mode.
How to Improve toneden-automation skill
Improve toneden-automation inputs
The best results come from precise operational context. Include the Toneden object or workflow type, the desired outcome, any identifiers you already know, and whether the agent should ask before making changes. For example: “Find the current Toneden tools for managing [campaign/link/audience/etc.], list required fields, then wait for my confirmation before executing.”
Avoid common failure modes
The main failure modes are skipping tool discovery, assuming a connection is active, and inventing inputs that were not returned by RUBE_SEARCH_TOOLS. To reduce these risks, explicitly tell the agent: “Do not call an execution tool until you have searched tools for this exact use case and confirmed the toneden connection is active.”
Iterate after the first tool search
Treat the first Rube search as planning, not completion. Ask the agent to summarize available tool slugs, required fields, optional fields, and risks before execution. If the returned schema is too broad, narrow the use case and search again with more specific wording.
Add project-specific guardrails
For production use, wrap the toneden-automation guide with your own rules: require confirmation before destructive changes, define naming conventions, specify which Toneden accounts or campaigns are in scope, and log the final tool call inputs. These guardrails make the skill safer for recurring automation without changing its core Rube MCP workflow.