What prerequisites do I need to use goody-automation?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Goody connection via RUBE_MANAGE_CONNECTIONS with toolkit goody; always search for tools first.

How do I select the correct tool slug and inputs?

Run RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas; use the exact field names and include the memory field in RUBE_MULTI_EXECUTE_TOOL; never hardcode slugs.

What if tool schemas change?

Re-run RUBE_SEARCH_TOOLS to fetch updated schemas and adjust your arguments accordingly; ensure you have an ACTIVE connection before executing.

goody-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Goody Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/goody

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Goody operations through Composio's Goody toolkit using Rube MCP. It emphasizes discovering current tool schemas before each run and maintaining an active Goody connection for repeatable, schema-compliant automation.

How This Skill Works

Begin by verifying RUBE_SEARCH_TOOLS is available, then connect to the Goody toolkit with RUBE_MANAGE_CONNECTIONS and check for ACTIVE status. Finally, discover tools, select a tool_slug, and execute it via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the active session_id.

When to Use It

You need up-to-date Goody tool schemas before running a workflow.
You want to validate the Goody connection is ACTIVE before execution.
You are automating a Goody task that requires a discovered tool slug and schema.
You need to run multiple Goody tools in a single session with memory state.
You must handle updated tool schemas or pagination in tool results.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: "Goody operations", known_fields: ""}], session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["goody"], session_id: "<from step 1>"
Step 3: RUBE_MULTI_EXECUTE_TOOL with tools: [{tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: { /* schema-compliant args from search results */ }}], memory: {}, session_id: "<from step 2>"

Best Practices

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use the exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even when empty.
Reuse session IDs within a workflow and regenerate for new workflows.

Example Use Cases

Automate a Goody status check by discovering the latest tool set, connecting, and running a status tool.
Generate a Goody activity report by executing a discovered reporting tool with structured inputs.
Sync Goody tasks to an external calendar by chaining a discovery step with a calendar update tool.
Run a batch of Goody operations in a single session to improve throughput.
Retry a failed Goody step by reusing the session and re-running the corresponding tool with updated inputs.

Frequently Asked Questions

Add this skill to your agents