$ ~/registry/skill/composiohq-composio-skills-revolt-automation

SKILL

revolt-automation

Name: revolt-automation
Author: Composio

Automate common Revolt tasks and collaboration workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially an open-source instruction/prompt template with no embedded local code execution or file access. The main security considerations come from connecting to the remote Rube MCP service and authorizing a Revolt account, which introduces normal third-party data egress and account access considerations.

CredentialsCaution

The material says 'no API keys needed,' but it still requires establishing an ACTIVE `revolt` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link. That implies third-party account tokens/session authorization are involved. No explicit secret harvesting is shown, but there is the normal risk surface of granting Revolt access to the Rube/Composio side.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing Revolt actions through Composio/Rube. Search queries, session IDs, tool arguments, and related workflow data are likely sent to that remote service. No unrelated or hidden exfiltration endpoint is evident, but normal data egress to the declared third-party service exists.

Code executionLow risk

Based on the provided material, this is a prompt-only skill consisting of workflow instructions and call sequences. It does not include code or install steps that would start local processes, run scripts, or request system-level privileges. Its capabilities depend on external MCP tools rather than local execution.

Data accessCaution

There is no indication of local filesystem, database, or OS resource access. However, once the Revolt connection is authorized, the remote tools may read or modify Revolt-side resources within the granted scope. The exact data access depends on the external tool schemas and the user's authorization, and the material does not show a clear least-privilege boundary.

Supply chainCaution

Positive factors: the skill is listed in a GitHub open-source repository with high community adoption (~64.7k stars), which lowers risk. However, the license is unspecified, maintenance status is unknown, and actual operation depends on externally hosted Rube/Composio services. As a result, auditability mainly covers the skill text itself, not the backend service, so some supply-chain caution remains warranted.

Recommendations

Only connect this MCP if you trust `rube.app` / Composio, and review their privacy, logging, and data-handling practices.
When authorizing Revolt, use a least-privilege account or test environment where possible instead of granting access to highly sensitive servers or organizations.
Before execution, inspect the current schemas and operations returned by `RUBE_SEARCH_TOOLS` to verify the expected read/write scope.
If your organization has compliance requirements, confirm the external MCP service's hosting region, auditability, and token/connection revocation process.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "revolt-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/revolt-automation/SKILL.md
2. Save it as ~/.claude/skills/revolt-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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`

Powered by Composio

Automate Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_