What is Cults Automation via Rube MCP?

It is a workflow pattern that automates Cults operations using Composio's Cults toolkit, discovering current tool schemas and ensuring an ACTIVE connection before execution.

Do I need API keys to use MCP?

No API keys are needed; you add the MCP server endpoint and rely on RUBE_SEARCH_TOOLS to fetch tool schemas and manage connections.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change frequently. Calling RUBE_SEARCH_TOOLS ensures you use up-to-date tool slugs and exact argument schemas for execution.

cults-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Cults Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cults

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Cults connection via RUBE_MANAGE_CONNECTIONS with toolkit cults
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 cults
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: "Cults 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 Cults task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["cults"]
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 Cults-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `cults`
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/cults-automation/SKILL.mdView on GitHub

Overview

Cults Automation via Rube MCP automates Cults operations using Composio's Cults toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and verifying an ACTIVE Cults connection before executing workflows.

How This Skill Works

First, discover available Cults tools using RUBE_SEARCH_TOOLS for your desired use_case. Next, verify the Cults connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing the required arguments, a memory object, and a session_id.

When to Use It

You want to automate Cults operations while tool schemas can change frequently.
You need to chain multiple Cults tasks in a single workflow with a shared session.
You must confirm an ACTIVE Cults connection before execution.
You need to handle pagination or multiple results when discovering tools.
You’re integrating Cults tasks into a larger automation pipeline.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["cults"] and confirm the status is ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing the tool slug, required arguments, a memory object, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool schemas.
Verify the Cults connection is ACTIVE with RUBE_MANAGE_CONNECTIONS prior to execution.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover Cults operations tools with RUBE_SEARCH_TOOLS for a specific use_case and select a tool slug from the results.
Establish the Cults toolkit connection via RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE.
Execute the selected tool using RUBE_MULTI_EXECUTE_TOOL with the correct arguments derived from the schema and a memory payload.
Reuse the same session_id across multiple steps to chain tools in a single automation workflow.
When tool discovery returns many results, handle pagination tokens to fetch all available tools.

Frequently Asked Questions

Add this skill to your agents