PromptShop

Moxie Automation

This skill automates Moxie operations using the Composio Moxie toolkit via Rube MCP.

Install

npx promptshop add moxie-automation

Details

What This Skill Does

This skill automates Moxie operations using the Composio Moxie toolkit via Rube MCP. It's designed for users who want to streamline their customer service and engagement workflows. The skill provides guidance on setup, tool discovery, and execution, while also addressing common pitfalls.

When to Use

  • Discover available Moxie tools.
  • Check the status of the Moxie connection.
  • Execute specific Moxie tools.
  • Automate customer service tasks.
  • Manage customer interactions automatically.
  • Personalize customer engagement.

Key Features

  • Uses Rube MCP to automate Moxie tasks.
  • Requires an active Moxie connection.
  • Employs RUBE_SEARCH_TOOLS for tool discovery.
  • Checks connection status via RUBE_MANAGE_CONNECTIONS.
  • Executes tools using RUBE_MULTI_EXECUTE_TOOL.
  • Provides guidance on avoiding common pitfalls.

Manual Installation

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

Toolkit docs: composio.dev/toolkits/moxie

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["moxie"] 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Moxie-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit moxie
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

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

Toolkit docs: composio.dev/toolkits/moxie

Quick Reference

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Moxie-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit moxie
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef