$ loading_
Automate SMS alert workflows through Rube MCP for faster notifications and responses.
This is an open-source, widely adopted prompt-only skill wrapper with no embedded executable code, secrets, or local permission requests in the provided material. The main concern is that it directs users to connect to remote Rube MCP/Composio services and perform SMS Alert actions through external integrations, which is a normal external-tool caution rather than a concrete high-risk red flag.
The material says there are 'no API keys,' but it still requires establishing an external `sms_alert` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link when inactive. This implies credentials are likely handled in the Rube/Composio connection flow. The docs do not specify credential type, storage, or scope, creating normal third-party auth/token-management concerns, but no explicit abuse red flag is shown.
The skill is not purely local: it instructs users to add `https://rube.app/mcp` as an MCP server and references Composio tooling/docs. User prompts, session IDs, tool arguments, and potentially SMS Alert data may flow through the remote MCP and related integrations. The remote destinations are broadly identifiable in the material (Rube/Composio), so this is declared network egress rather than evidence of exfiltration to unknown or unrelated endpoints.
Per the objective checks, this is a prompt-only skill. The README only describes how to call external MCP tools and does not include scripts, install commands, local process launch steps, or system command execution. Based on the visible material, it does not request local code-execution privileges beyond the stated behavior.
The material does not claim direct local file or system access, but through remote capabilities such as `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH`, it may query or act on connected SMS Alert account/data. The effective data-access scope depends on the external tool schemas and the granted connection permissions; the docs do not define strict least-privilege boundaries, so external account/data exposure should be reviewed.
The source is an open GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk; the artifact itself is only a skill/documentation wrapper with no visible binaries or install-time dependencies. Caveats remain: no license is stated, maintenance status is unknown, and real execution depends on third-party Rube/Composio services, so ongoing trust in those upstream services still matters.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "sms-alert-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/sms-alert-automation/SKILL.md 2. Save it as ~/.claude/skills/sms-alert-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate SMS Alert operations through Composio's SMS Alert toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/sms_alert
RUBE_MANAGE_CONNECTIONS with toolkit sms_alertRUBE_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 sms_alertAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "SMS Alert 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 SMS Alert task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["sms_alert"]
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 SMS Alert-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit sms_alert |
| 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 file and format conversion tasks via Rube MCP with schema lookup first.
Automate CustomJS tasks through Rube MCP for faster scripted workflows.
Automate Cloudlayer tasks via Rube MCP after checking current tool schemas.
Automate Byteforms form tasks and workflow actions through Rube MCP.
Automate Dadata Ru lookups, validation, and data tasks through Rube MCP.
Automate Dialpad calling and collaboration tasks through Rube MCP workflows.
Automate Agent Mail workflows through Rube MCP with schema-aware tool discovery.
Automate Msg91 workflows like messaging, templates, and delivery operations via Rube MCP.
Automate MailerSend sending and management tasks through Rube MCP workflows.
Automate SMTP2GO email sending and management tasks through Rube MCP.
Automate Pushover notification tasks and message workflows via Rube MCP.
Automate Sendbird tasks via Rube MCP with schema lookup first.