What is moxie-automation?

It automates Moxie operations through the Composio Moxie toolkit using Rube MCP mechanisms.

Do I need API keys to use Rube MCP for Moxie?

No API keys are needed. Add the Rube MCP endpoint such as https://rube.app/mcp and it works.

How do I handle changing tool schemas?

Always call RUBE_SEARCH_TOOLS to fetch current tool schemas before selecting slugs or arguments; do not hardcode values; ensure memory is included in executions and verify ACTIVE connection

moxie-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Moxie Automation via Rube MCP

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Moxie-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `moxie`
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/moxie-automation/SKILL.mdView on GitHub

Overview

Automate Moxie operations through Composio's Moxie toolkit via Rube MCP. Always search for current tool schemas using RUBE_SEARCH_TOOLS and avoid hardcoding tool slugs.

How This Skill Works

The workflow starts by discovering available Moxie tools with RUBE_SEARCH_TOOLS, then ensures an active connection to the moxie toolkit via RUBE_MANAGE_CONNECTIONS. Tools are executed with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and schema compliant arguments, including memory and session data.

When to Use It

Initialize a new Moxie automation pipeline with Rube MCP
Automate a task where tool schemas change frequently and must be fetched first
Validate and establish an ACTIVE Moxie connection before running workflows
Execute a sequence of tools in a single session using RUBE_MULTI_EXECUTE_TOOL
Troubleshoot flaky workflows by refreshing tool schemas and connection status

Quick Start

Step 1: Ensure RUBE MCP is available by adding the MCP server and running RUBE_SEARCH_TOOLS
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits moxie and confirm ACTIVE
Step 3: Discover tools and execute using RUBE_MULTI_EXECUTE_TOOL with the slug and memory

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting tool slugs
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the tool schemas
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs when appropriate and avoid creating new sessions for related tasks

Example Use Cases

Automate monthly Moxie data export by discovering tools, connecting to moxie, then executing the chosen tool slug with proper arguments
Orchestrate a multi step Moxie cleanup task in a single session using memory in each tool call
Diagnose a failed workflow by re searching for tools to refresh slugs and re running with an ACTIVE connection
Bulk operate multiple Moxie tasks via RUBE_REMOTE_WORKBENCH run_composio_tool after tool discovery
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS and craft a compliant execution plan

Frequently Asked Questions

Add this skill to your agents