Do I need an API key to use this skill?

No. Setup uses the Rube MCP endpoint; no API keys are required—just add the MCP server and follow the connection steps.

Why is RUBE_SEARCH_TOOLS required before every tool execution?

Tool schemas change frequently; calling RUBE_SEARCH_TOOLS fetches current tool slugs, input schemas, and execution plans to prevent hardcoding.

What are the prerequisites to run Moonclerk workflows?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond, and an ACTIVE Moonclerk connection via RUBE_MANAGE_CONNECTIONS is required before executing tools. Include a memory object in multi-tool calls and reuse session IDs where appropriate.

moonclerk-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Moonclerk Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moonclerk

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["moonclerk"]
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 Moonclerk-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `moonclerk`
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/moonclerk-automation/SKILL.mdView on GitHub

Overview

Automate Moonclerk operations using Composio's Moonclerk toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution, verifying an ACTIVE Moonclerk connection, and executing tools with schema-compliant arguments. This saves time and reduces errors when integrating Moonclerk tasks into workflows.

How This Skill Works

The skill fetches live tool schemas with RUBE_SEARCH_TOOLS, ensures a Moonclerk connection via RUBE_MANAGE_CONNECTIONS, then runs the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory context.

When to Use It

When you need to perform a Moonclerk operation that exists as a tool slug discovered via RUBE_SEARCH_TOOLS.
When you must verify an ACTIVE Moonclerk connection before running workflows.
When tool schemas may change and you must fetch the latest slugs and arg schemas.
When executing a sequence of Moonclerk tools in a single session with memory data.
When performing bulk or batch Moonclerk tasks via a workflow and handling pagination in tool results.

Quick Start

Step 1: Add the MCP server at https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["moonclerk"] and complete auth if required.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas.
Verify the Moonclerk connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the discovered tool schemas; avoid hardcoding.
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when fetching results.

Example Use Cases

Create a new Moonclerk payment using a tool slug discovered by RUBE_SEARCH_TOOLS, with schema-compliant arguments.
Update an existing Moonclerk customer or subscription record based on a form submission, using the corresponding discovered tool.
Fetch latest invoices or subscribers and trigger downstream actions in another system using the Moonclerk tools.
Execute multiple Moonclerk tools in a single session to reconcile payments and update statuses.
Paginate through tool results to fetch all Moonclerk subscribers using RUBE_SEARCH_TOOLS and subsequent execution steps.

Frequently Asked Questions

Add this skill to your agents