$ ~/registry/skill/composiohq-composio-skills-thanks-io-automation

SKILL

thanks-io-automation

Automate Thanks IO tasks through Rube MCP with tool discovery first.

Stars

★ 73,665

Source

GitHub

Updated

2026-08-28

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.7k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "thanks-io-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/thanks-io-automation/SKILL.md
2. Save it as ~/.claude/skills/thanks-io-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Integrate Thanks IO into an automated workflow

Developers can connect Thanks IO operations to existing AI or automation workflows through Rube MCP. The key pattern is to discover tools first, verify the connection, and then execute against the live schema.

Verify tools and authorization before execution

Before running Thanks IO operations, users can verify the available tools, parameter requirements, and connection status. This helps reduce failures caused by missing authorization or schema changes.

Run bulk or multi-step Thanks IO operations

When a task requires multiple steps, users can reuse the same session and complete the flow with multi-tool execution. The docs also highlight details like pagination and the required memory parameter.

// docs

AI summary

The README explains how to automate Thanks IO operations through Rube MCP using Composio’s Thanks IO toolkit. It covers prerequisites, connection and authorization steps, and the standard workflow: search for tools first, verify the thanks_io connection, then execute with the discovered tool slug and schema-compliant arguments. It also highlights pitfalls such as session reuse, required memory fields, and pagination handling.

Show full docs ▾

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

// FAQ

What prerequisites are required before using this skill?

You need Rube MCP to be connected and RUBE_SEARCH_TOOLS to be available. You also need to configure and activate a thanks_io connection through RUBE_MANAGE_CONNECTIONS.

Why must I search for tools first?

The docs explicitly say tool schemas can change, so you should not hardcode tool slugs or arguments. Call RUBE_SEARCH_TOOLS first to get the current tools and exact field definitions.

Do I need an API key for setup or connection?

The excerpt says you only need to add the Rube MCP endpoint and no API key is required. Thanks IO connection and authorization are handled through RUBE_MANAGE_CONNECTIONS.

Automate Esignatures IO signing and document workflows through Rube MCP.

ComposioGet→

$ loading_