Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Cults Automation via Rube MCP

agent tool_use skill risk: low

Cults Automation via Rube MCP

Provides instructions for automating Cults operations through Composio's Cults toolkit via Rube MCP, covering prerequisites, setup, tool discovery with RUBE_SEARCH_TOOLS, connectio…

  • External action: high

SKILL 1 file

SKILL.md
---
name: cults-automation
description: "Automate Cults tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Cults Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/cults](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `cults`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active Cults toolkit connection

OPTIONAL CONTEXT

  • session_id
  • specific use_case for tool search

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas.
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds.
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit cults.
  5. Confirm connection status shows ACTIVE before running any workflows.
  6. Always discover available tools before executing workflows.
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
  8. Reuse session IDs within a workflow. Generate new ones for new workflows.
  9. Check responses for pagination tokens and continue fetching until complete.
  10. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.
  11. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
  12. Use exact field names and types from the search results.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Prerequisites, Setup, Tool Discovery, Core Workflow Pattern, Known Pitfalls, Quick Reference
Constraints
  • include prerequisites and setup steps
  • always start with RUBE_SEARCH_TOOLS
  • use exact schemas from tool discovery

SUCCESS CRITERIA

  • Follow the core workflow pattern in order
  • Search tools before any execution
  • Maintain active Cults connection

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Skipping connection status verification
  • Ignoring schema compliance from search results
  • Omitting the memory parameter in execute calls

EXAMPLES

Includes example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with parameters.

CAVEATS

Dependencies
  • Rube MCP connection
  • Active Cults connection via RUBE_MANAGE_CONNECTIONS
  • RUBE_SEARCH_TOOLS availability
Missing context
  • Example values for session_id and use_case
  • Error handling or fallback steps

QUALITY

OVERALL
0.80
CLARITY
0.85
SPECIFICITY
0.75
REUSABILITY
0.80
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace inline code blocks with explicit {{placeholder}} variables for session_id, use_case, and tool_slug to improve templating.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT