Rube MCP is Composio's MCP server (e.g., https://rube.app/mcp) used to discover tool schemas, manage connections, and execute tools without API keys.

How do I ensure tools use current schemas?

Always call RUBE_SEARCH_TOOLS before executing; tool slugs and required fields come from the latest schemas returned by the search.

What if the connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to activate the castingwords toolkit and follow the provided auth flow until the status is ACTIVE before running workflows.

castingwords-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Castingwords Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/castingwords

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["castingwords"]
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 Castingwords-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `castingwords`
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/castingwords-automation/SKILL.md

View on GitHub

Overview

Automate Castingwords operations through Composio's Castingwords toolkit via Rube MCP. This approach ensures you fetch current tool schemas first and establish a Castingwords connection before executing workflows.

How This Skill Works

Discover available Castingwords tools with RUBE_SEARCH_TOOLS to pull the latest input schemas and execution plans. Then verify or establish a connection with RUBE_MANAGE_CONNECTIONS, ensure ACTIVE, and execute the tool via RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

When to Use It

You need to automate a Castingwords operation within a Composio workflow.
You want to adapt to changing tool schemas by always querying RUBE_SEARCH_TOOLS before running a task.
You are integrating Castingwords tasks into larger automation pipelines and need secure connections.
You plan to batch multiple Castingwords tasks in a single session with shared memory.
You need to confirm the Castingwords connection is ACTIVE before executing any tools.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with a Castingwords use_case to fetch current tool slugs and input schemas.
Step 2: RUBE_MANAGE_CONNECTIONS for the castingwords toolkit and confirm the session is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL using a discovered tool_slug, proper arguments from the schema, memory: {} and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas.
Check RUBE_MANAGE_CONNECTIONS and ensure ACTIVE status before executing tools.
Use exact field names and types from the search results; do not hardcode slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones only for new workflows.

Example Use Cases

Discover a Castingwords transcription tool and run it on a provided audio URL, then return the transcript.
Batch-submit multiple audio files in a single session using the same Castingwords tool and memory.
Validate the Castingwords connection in a recurring job to ensure it remains ACTIVE before execution.
Review full tool schemas with RUBE_GET_TOOL_SCHEMAS before building custom arguments.
Reuse a session_id across steps to maintain context during a multi-tool Castingwords workflow.

Frequently Asked Questions

Add this skill to your agents