superchat-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/superchat-automation --openclawFiles (1)
SKILL.md
2.9 KB
Superchat Automation via Rube MCP
Automate Superchat operations through Composio's Superchat toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/superchat
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Superchat connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsuperchat - 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 toolkitsuperchat - 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: "Superchat 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 Superchat task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["superchat"]
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 Superchat-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit superchat |
| 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/superchat-automation/SKILL.mdView on GitHub Overview
Automate Superchat operations through Composio's Superchat toolkit via Rube MCP. It stresses always searching for current tool schemas before execution to avoid hardcoding slugs or fields. This makes routine Superchat actions faster, more reliable, and easier to maintain.
How This Skill Works
Discover available tools with RUBE_SEARCH_TOOLS for your Superchat use case, then verify the connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. When ready, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session ID, using the discovered tool slug and schema-compliant arguments.
When to Use It
- When a new Superchat arrives and you want an automated acknowledgment or response using a tool discovered at runtime.
- When you need to fetch donor data or metadata before replying to personalize the interaction.
- When you must chain actions (e.g., fetch data, then post a reply) using the correct, up-to-date tool schemas.
- When performing batch or bulk processing across multiple Superchat events in a single workflow.
- When tool schemas may have changed; re-run RUBE_SEARCH_TOOLS to refresh slugs and required fields.
Quick Start
- Step 1: Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Verify availability: Run RUBE_SEARCH_TOOLS and confirm tool schemas for your Superchat use case are returned.
- Step 3: Connect and execute: Call RUBE_MANAGE_CONNECTIONS with toolkit 'superchat', then run RUBE_MULTI_EXECUTE_TOOL using a discovered tool slug and memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas and avoid hardcoding slugs or arguments.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing any tools.
- Use exact field names and types from the tool schemas returned by the search results.
- Include an explicit memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Reuse session IDs within a workflow to preserve context; generate a new session for separate workflows.
Example Use Cases
- Example 1: A new Superchat triggers an automated acknowledgment. Discover tools with RUBE_SEARCH_TOOLS, select the appropriate tool slug from the results, verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute the tool via RUBE_MULTI_EXECUTE_TOOL using required arguments and memory.
- Example 2: Retrieve donor metadata from a discovered tool (tool slug obtained from search), then compose a personalized reply. Ensure the input matches the tool’s schema and include memory and the current session_id.
- Example 3: Batch process several Superchat events by running multiple tools in one session using RUBE_REMOTE_WORKBENCH, ensuring you fetch current tool slugs first and supply memory for each execution.
- Example 4: After reconnecting a previously inactive Rube MCP connection, re-check with RUBE_MANAGE_CONNECTIONS and only proceed when status is ACTIVE, then execute the intended tool.
- Example 5: Tool schemas change over time. Before running workflows, re-run RUBE_SEARCH_TOOLS to refresh tool slugs and required fields to avoid failures.
Frequently Asked Questions
Add this skill to your agents
