Do I need an active Msg91 connection?

Yes. You must have an active Msg91 connection configured via RUBE_MANAGE_CONNECTIONS before executing tools.

Why call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Always fetch current tool slugs and input schemas to avoid hardcoding and errors.

How do I actually run a tool?

After discovering a tool via RUBE_SEARCH_TOOLS and establishing an ACTIVE connection, call RUBE_MULTI_EXECUTE_TOOL with the tool_slug, the required arguments from the schema, a memory object, and a session_id.

msg91-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/msg91-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Msg91 Automation via Rube MCP

Automate Msg91 operations through Composio's Msg91 toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/msg91

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Msg91 connection via RUBE_MANAGE_CONNECTIONS with toolkit msg91
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit msg91
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: "Msg91 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 Msg91 task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["msg91"]
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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 Msg91-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `msg91`
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/msg91-automation/SKILL.mdView on GitHub

Overview

Automates Msg91 tasks through Composio's Msg91 toolkit using Rube MCP. It relies on live tool schemas discovered at runtime, so always call RUBE_SEARCH_TOOLS first to ensure correct inputs and slugs before execution.

How This Skill Works

Connect Rube MCP and Msg91, then discover available Msg91 tools with RUBE_SEARCH_TOOLS to get current input schemas. Establish a Msg91 toolkit connection with RUBE_MANAGE_CONNECTIONS, ensure the status is ACTIVE, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, including a memory object and a session_id.

When to Use It

Need to automate a Msg91 operation and require up-to-date tool schemas before proceeding
Setting up or re-authenticating the Msg91 toolkit connection via RUBE_MANAGE_CONNECTIONS
Executing a discovered Msg91 tool as part of a single automated workflow using RUBE_MULTI_EXECUTE_TOOL
Batching multiple Msg91 actions in a sequence within a single session or campaign
Handling schema changes or tool additions by refreshing schemas with RUBE_SEARCH_TOOLS instead of hardcoding slugs

Quick Start

Step 1: Verify Rube MCP is connected and run RUBE_SEARCH_TOOLS to fetch current Msg91 tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["msg91"] and ensure the session is ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and schema-compliant arguments, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use exact field names and types from the search results in tool arguments
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a single workflow and generate new ones for new workflows

Example Use Cases

Discover Msg91 operation tools with RUBE_SEARCH_TOOLS, connect the msg91 toolkit via RUBE_MANAGE_CONNECTIONS, and execute a basic SMS send tool slug using RUBE_MULTI_EXECUTE_TOOL
Run a sequence of Msg91 actions in one flow by executing multiple discovered tool slugs within the same session (e.g., setup then send)
If the Msg91 connection becomes INACTIVE, re-authenticate using the auth link from RUBE_MANAGE_CONNECTIONS and retry
Fetch all available Msg91 tools using RUBE_SEARCH_TOOLS and handle pagination tokens if multiple pages are returned
Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk Msg91 operations across many recipients or campaigns

Frequently Asked Questions

Add this skill to your agents