What is godial-automation?

It's a method to automate Godial operations through Composio's toolkit using Rube MCP as the orchestration layer.

What prerequisites are required?

Rube MCP must be connected, a Godial connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS, and you must always run RUBE_SEARCH_TOOLS first to get current tool schemas.

How do I discover tools and execute a Godial task?

First run RUBE_SEARCH_TOOLS to discover tool slugs and schemas, then verify the connection with RUBE_MANAGE_CONNECTIONS, and finally execute the tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload.

godial-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Godial Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/godial

Prerequisites

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

Step 2: Check Connection

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

Overview

Godial Automation via Rube MCP lets you orchestrate Godial operations through Composio's toolkit. It relies on up-to-date tool schemas obtained by RUBE_SEARCH_TOOLS and requires an active Godial connection established with RUBE_MANAGE_CONNECTIONS. This approach minimizes drift by always discovering tools before execution.

How This Skill Works

The workflow begins by discovering available Godial tools with RUBE_SEARCH_TOOLS, then checks that a live connection exists via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovery-provided slug and a memory payload. Always ensure the session is ACTIVE and pass an explicit memory object, even if empty.

When to Use It

Starting a Godial workflow and fetching current tool schemas
Establishing or validating an ACTIVE Godial connection before use
Discovering tools for a specific Godial task and planning execution
Executing a multi-tool workflow with a session and memory payload
Troubleshooting by re-searching tools when schemas change or connections fluctuate

Quick Start

Step 1: Add MCP server https://rube.app/mcp to your client configuration
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Godial tool schemas
Step 3: Use RUBE_MANAGE_CONNECTIONS for toolkit godial; if ACTIVE, execute with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and a memory payload

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas; do not hardcode tool slugs or arguments
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate a weekly Godial data pull by discovering tools with RUBE_SEARCH_TOOLS and executing a chosen slug using RUBE_MULTI_EXECUTE_TOOL in a single session
Update a Godial script by re-fetching the latest tool schemas and executing with the new slug imported from the search results
Run a bulk set of Godial operations in a multi-step workflow using a shared session and memory payload
Recover from an inactive connection by re-authenticating via RUBE_MANAGE_CONNECTIONS before retrying
Handle large tool catalogs by paging through RUBE_SEARCH_TOOLS results until all relevant tools are loaded

Frequently Asked Questions

Add this skill to your agents