Cults Automation
This skill automates Cults operations through Composio's Cults toolkit via Rube MCP.
Install
npx promptshop add cults-automationDetails
What This Skill Does
- This skill automates Cults operations through Composio's Cults toolkit via Rube MCP.
- It is designed for users who need to manage and automate tasks related to Cults, a platform for 3D printing models.
- The skill enables programmatic interaction with Cults for managing designs and sales.
When to Use
- Upload new 3D models.
- Update model descriptions.
- Manage pricing and availability.
- Track sales performance.
- Automate promotional campaigns.
- Respond to user inquiries.
Key Features
- Automates Cults tasks via Rube MCP.
- Uses RUBE_SEARCH_TOOLS for tool discovery.
- Requires active Cults connection.
- Employs RUBE_MULTI_EXECUTE_TOOL for execution.
- Provides connection status checks.
- Ensures schema compliance.
Manual Installation
- Manual installation
- View Full Skill Content
- The complete markdown content that gets installed
- 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
- Cults Automation via Rube MCP
Automate Cults operations through Composio's Cults toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cults
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
- 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
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.
RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Cults task"}] session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS toolkits: ["cults"] session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"
- 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
| 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