What are the prerequisites?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available), an ACTIVE Thanks IO connection via RUBE_MANAGE_CONNECTIONS with toolkit thanks_io, and you should always search tools first to get current schemas.

Why must I always call RUBE_SEARCH_TOOLS?

Tool schemas can change frequently; fetching them ensures you have the latest tool slugs and argument schemas and prevents hardcoding.

What should I include in memory for RUBE_MULTI_EXECUTE_TOOL?

Always include a memory parameter, even if empty (memory: {}), to conform with the expected payload structure.

thanks-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Thanks IO Automation via Rube MCP

Automate Thanks IO operations through Composio's Thanks IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/thanks_io

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Thanks IO operations through Composio's Thanks IO toolkit via Rube MCP. It emphasizes discovering current tool schemas, verifying an ACTIVE connection, and executing tools in a memory-aware workflow. Keeping tool schemas fresh by always using RUBE_SEARCH_TOOLS helps avoid hardcoding slugs.

How This Skill Works

Technically, the workflow starts with RUBE_SEARCH_TOOLS to fetch available Thanks IO tool schemas, then uses RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE connection to the thanks_io toolkit. Finally, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with the proper slug and arguments, always including a memory object and a valid session_id.

When to Use It

Automating routine Thanks IO tasks by discovering and executing tools programmatically
When tool schemas may change and you must fetch current slugs first
When you need to confirm an ACTIVE connection before running workflows
When performing batch or bulk tool operations via RUBE_REMOTE_WORKBENCH
When reusing a session_id across related workflows to preserve state

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit "thanks_io", then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory object

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to get current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to running tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs where appropriate and handle pagination tokens in tool searches

Example Use Cases

Discover Thanks IO tools for a specific use case, then execute a discovered tool slug with the correct arguments
Establish a new Thanks IO connection, validate it is ACTIVE, and run a workflow
Run multiple Thanks IO tasks in bulk using RUBE_MULTI_EXECUTE_TOOL in succession with a shared session
Before each run, re-run RUBE_SEARCH_TOOLS to pick up any schema changes and adjust tool slugs
Retain a single session_id across related tasks to maintain context and state

Frequently Asked Questions

Add this skill to your agents