cults-automation

Automate Cults tasks via Rube MCP (Composio). Always search tools first for current schemas.

Install

Hot:17

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-cults-automation&locale=en&source=copy

Cults Automation - Automate Cults Tasks via Rube MCP

Skill Overview


Cults Automation integrates Composio’s Cults toolkit with Rube MCP to help users automatically perform various operations on the Cults platform, without writing complex API-calling code.

Suitable Use Cases

  • Batch Management of 3D Printing Models

  • Automate the downloading, organizing, and managing of 3D model files from the Cults platform. Ideal for content creators and collectors who need to acquire resources in bulk.

  • Creator Dashboard Automation on Cults

  • Streamline everyday creator tasks on the Cults platform, such as publishing works, viewing statistics, and managing comments, to improve operational efficiency.

  • MCP App Integration Development

  • Add Cults functionality support to MCP-based applications. Developers don’t need to handle API authentication or Schema changes—simply call through Rube MCP.

    Core Features

  • Smart Tool Discovery

  • Use RUBE_SEARCH_TOOLS to dynamically fetch the currently available list of Cults tools and their input schemas, avoiding compatibility issues caused by hard-coding.

  • Connection Status Management

  • Use RUBE_MANAGE_CONNECTIONS to check and manage the Cults connection status in real time, ensuring that the connection is activated before executing the workflow.

  • Batch Execution of Multiple Tools

  • Chain multiple Cults operations within a single session using RUBE_MULTI_EXECUTE_TOOL, supporting complex automation workflows.

    Frequently Asked Questions

    Does Rube MCP require an API key?


    No. Rube MCP uses a no-auth architecture. You only need to add https://rube.app/mcp as the MCP server endpoint in the client configuration.

    Why must I call RUBE_SEARCH_TOOLS first?


    Composio’s tool schemas are updated periodically. Hard-coding tool names and parameters can lead to call failures. Running tool discovery first ensures you use the latest schemas and improves the stability of automation scripts.

    How should I handle tool schema changes?


    Before each workflow run, call RUBE_SEARCH_TOOLS to fetch the latest tool definitions. If the returned tool parameters differ from before, adjust the parameter structure of RUBE_MULTI_EXECUTE_TOOL according to the new schema.

    What if the Cults connection is not activated?


    Call RUBE_MANAGE_CONNECTIONS to check the connection status. If the status is not ACTIVE, complete Cults account authorization using the authentication link returned. After activation, normal usage will work.

    Which tool should I use for batch operations?


    For scenarios where you need to execute multiple different tools in batch, use RUBE_MULTI_EXECUTE_TOOL. For complex tasks that require running the full Composio toolchain, consider using RUBE_REMOTE_WORKBENCH together with run_composio_tool().

    Can a session ID be reused?


    Yes. Reuse the session ID within the same workflow to maintain contextual continuity. For new independent workflows, it’s recommended to generate a new session ID.