sms-alert-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/sms-alert-automation --openclawFiles (1)
SKILL.md
2.9 KB
SMS Alert Automation via Rube MCP
Automate SMS Alert operations through Composio's SMS Alert toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/sms_alert
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active SMS Alert connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsms_alert - 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 toolkitsms_alert - 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: "SMS Alert 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 SMS Alert task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["sms_alert"]
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 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/sms-alert-automation/SKILL.mdView on GitHub Overview
Automate SMS Alert operations via Composio's SMS Alert toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas, validating connections, and executing the appropriate SMS actions with exact schema guidance.
How This Skill Works
Start by discovering available SMS alert tools with RUBE_SEARCH_TOOLS to fetch slugs and input schemas. Then verify the sms_alert connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the memory payload and session_id from the discovery step.
When to Use It
- Setting up a fresh SMS alert workflow and you need the latest tool schemas before building the automation
- Validating that the sms_alert connection is ACTIVE prior to triggering any alerts
- Executing a discovered SMS alert tool with the exact arguments from the tool schema
- Updating an existing workflow after tool schemas change or new tools are introduced
- Running bulk or batch SMS alerts by leveraging multi-tool execution or remote bench workflows
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm current tool schemas
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit sms_alert and, when ACTIVE, execute a tool via RUBE_MULTI_EXECUTE_TOOL using discovered slug and memory
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas
- Check that the RUBE_MANAGE_CONNECTIONS status shows ACTIVE before any execution
- Use exact field names and types from the search results to avoid schema errors
- Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
- Reuse a session_id within a workflow and generate a new one for new workflows
Example Use Cases
- Example 1: Discover tools with RUBE_SEARCH_TOOLS for SMS Alert operations, then execute TOOL_SLUG_FROM_SEARCH with arguments sourced from the results
- Example 2: Connect to the sms_alert toolkit using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before triggering any alerts
- Example 3: After a schema update, re-run RUBE_SEARCH_TOOLS to fetch the new tool_slugs and adjust your automation accordingly
- Example 4: Send alerts to multiple recipients in a single run by using RUBE_MULTI_EXECUTE_TOOL with a populated memory payload
- Example 5: Inspect a tool’s full schema with RUBE_GET_TOOL_SCHEMAS to understand required fields and types for a new workflow
Frequently Asked Questions
Add this skill to your agents
