How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch up-to-date tool slugs and input schemas.

How can I verify the Goodbits connection is ready?

Query RUBE_MANAGE_CONNECTIONS with the goodbits toolkit and confirm the status is ACTIVE before running tools.

Is memory required for tool execution?

Yes. Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if it’s empty.

goodbits-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Goodbits Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/goodbits

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Goodbits operations through Composio's Goodbits toolkit using Rube MCP. This skill emphasizes always fetching current tool schemas before executing workflows to avoid stale slugs or fields.

How This Skill Works

Discover available Goodbits tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Check the connection status with RUBE_MANAGE_CONNECTIONS for the goodbits toolkit and ensure it is ACTIVE. Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, a memory payload, and the session_id from the discovery step.

When to Use It

You need to start a Goodbits workflow and want to ensure you’re using the latest tool schemas.
You must confirm the Goodbits connection is ACTIVE before running any workflows.
You want to execute a specific Goodbits operation discovered from tool discovery.
Performing bulk operations or multi-tool executions via RUBE_MULTI_EXECUTE_TOOL.
Troubleshooting tool changes or pagination by re-fetching tool schemas and reinitializing sessions.

Quick Start

Step 1: Add Rube MCP endpoint and verify RUBE_SEARCH_TOOLS responds.
Step 2: Use RUBE_SEARCH_TOOLS to discover tool_slugs and schemas for Goodbits tasks.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Do not hardcode tool slugs or argument names; use values from search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and refresh when starting new workflows.

Example Use Cases

Discover tools for a new Goodbits task, confirm the connection is ACTIVE, then run the create_campaign tool with appropriate arguments.
Update a subscriber list by executing the update_subscribers tool after validating the Goodbits connection is ACTIVE.
Run a bulk export of campaigns using a bulk_export tool, ensuring memory is provided.
Inspect available tools and input schemas via RUBE_GET_TOOL_SCHEMAS to validate required fields.
When tool schemas change, re-run RUBE_SEARCH_TOOLS and refresh session IDs to continue automation.

Frequently Asked Questions

Add this skill to your agents