$ loading_
Automate MX Technologies tasks via Rube MCP, searching tool schemas first.
This skill itself is an open-source prompt-style wrapper, but it is designed to connect to remote services via Rube MCP and operate MX Technologies workflows, so the overall posture is caution rather than high risk. No direct malicious indicators are present in the material, but it relies on third-party MCP/Composio infrastructure to handle workflow and connection state.
The material says the skill itself needs 'no API key', but it requires an ACTIVE `mx_technologies` connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth link flow; this implies the real credentials may be brokered by Rube/Composio. There is no explicit evidence of plaintext credential exposure or abuse, but third-party managed authorization is inherently sensitive.
The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and interacting with Composio/MX Technologies-related services to search tools, manage connections, and execute operations. User task descriptions, arguments, session IDs, and potentially business data are therefore sent through this third-party endpoint; this is expected behavior, but the material does not describe data minimization or retention controls.
The system flags it as `prompt-only`, and the provided content is mainly operational guidance and call patterns, with no local install script, shell command, or instruction to execute arbitrary code on the host. The main execution surface is on the remote MCP tool side, not within this skill package itself.
This skill is intended to 'Automate MX Technologies operations' and can invoke remote tools through `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`; by design, it may access connection data and business resources within the MX Technologies account. The material does not claim local file access and does not request system-level data beyond its stated purpose, but the scope of remote business data access should still be reviewed under least-privilege principles.
The source is an open GitHub repository, the system marks it as `open-source`, and community adoption is high (about 64.9k stars), all of which materially lower supply-chain risk. The skill material itself is auditable; although the license is unspecified, maintenance status is unknown, and it depends on external Rube/Composio services, there are no signs of closed-source payloads, impersonated origin, or other clear supply-chain red flags.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "mx-technologies-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/mx-technologies-automation/SKILL.md 2. Save it as ~/.claude/skills/mx-technologies-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate MX Technologies operations through Composio's MX Technologies toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/mx_technologies
RUBE_MANAGE_CONNECTIONS with toolkit mx_technologiesRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit mx_technologiesAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "MX Technologies operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific MX Technologies task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["mx_technologies"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with MX Technologies-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit mx_technologies |
| 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 Mem tasks through Rube MCP after checking current tool schemas first.
Automate OpenAI API tasks for text, embeddings, images, and model listing.
Manage Toggl Track time entries, projects, clients, and tags with natural language.
Automate Telnyx communication and number management tasks through Rube MCP.
Automate Tally tasks through Rube MCP for faster finance and data workflows.
Build complex multi-component web artifacts with React, Tailwind, and shadcn/ui.
Automate Autom workflows via Rube MCP while checking current tool schemas first.
Automate Moxie tasks through Rube MCP after checking current tool schemas.
Automate Mx Toolbox network and email diagnostic tasks through Rube MCP.
Automate Composio tasks via Rube MCP with tool schema lookup first.
Automate AI/ML API workflows via Rube MCP, checking latest tool schemas first.
Automate Amazon tasks through Rube MCP after checking current tool schemas.