Skill

revolt-automation

Automates Revolt tasks via Rube MCP (Composio) toolkit. Discovers tools dynamically with RUBE_SEARCH_TOOLS, manages connections, and executes workflows.

automation

npx claudepluginhub lunartech-x/superpowers --plugin superpowers

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

SKILL.md

Similar Skills

discordbot-automation

Automates Discord bot tasks via Composio toolkit and Rube MCP. Discovers tools dynamically, manages connections, and executes operations like sending messages or managing channels.

superpowers

discord-automation

36.4k

Automates Discord tasks including sending messages, DMs, managing channels, roles, webhooks, and reactions via Rube MCP and Composio toolkits. Requires active Discord connections.

antigravity-awesome-skills

discord-automation

2.7k

Automates Discord tasks: send messages/DMs, manage channels/roles/webhooks/reactions via Composio toolkits and Rube MCP. Requires active Discord connections.

all-skills

Stats

Stars13

Forks2

Last CommitMar 29, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Revolt 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_CONNECTIONS with toolkit revolt
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 revolt
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_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 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`