revolt-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/revolt-automation --openclawRevolt Automation via Rube MCP
Automate Revolt operations through Composio's Revolt toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/revolt
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Revolt connection via
RUBE_MANAGE_CONNECTIONSwith toolkitrevolt - 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 toolkitrevolt - 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: "Revolt 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 Revolt task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["revolt"]
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 Revolt-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit revolt |
| 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/revolt-automation/SKILL.mdView on GitHub Overview
Revolt Automation via Rube MCP lets you automate Revolt operations using Composio's Revolt toolkit. It emphasizes fetching current tool schemas with RUBE_SEARCH_TOOLS before each run and maintaining an ACTIVE Revolt connection via RUBE_MANAGE_CONNECTIONS. This makes Revolt workflows repeatable and resilient across schema changes.
How This Skill Works
Tools are discovered with RUBE_SEARCH_TOOLS to fetch current schemas and execution plans. Next, verify the Revolt connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL, passing the discovered slug and a memory payload.
When to Use It
- Automate a Revolt workflow by chaining tool executions in a single session
- When Revolt tool schemas change and you need fresh slugs and inputs
- Integrate Revolt tasks into larger Composio automation pipelines
- Onboard a new Revolt integration by validating discovery and connection first
- Perform bulk or repetitive Revolt operations across multiple sessions
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current Revolt tool schemas
- Step 3: Use RUBE_MANAGE_CONNECTIONS to activate the revolt toolkit and run RUBE_MULTI_EXECUTE_TOOL with a discovered slug
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any tool to get current slugs and schemas
- Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
- Match field names and types exactly to the discovered schema and avoid hardcoding slugs
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
- Reuse session IDs within a workflow and paginate responses until complete
Example Use Cases
- Onboard a Revolt integration by discovering tools, validating the connection, then running a setup tool
- Run a chained workflow: discover tools, check connection, execute two Revolt tools in order
- Fetch tool schemas with RUBE_GET_TOOL_SCHEMAS and execute the corresponding Revolt task
- Bulk run multiple Revolt operations in a single session using RUBE_MULTI_EXECUTE_TOOL
- Perform periodic Revolt maintenance by validating schemas and ensuring ACTIVE connections
