Do I need API keys to use this skill?

No keys are required. Just add the MCP endpoint and ensure the Givebutter toolkit is connected.

How do I keep tool schemas current?

Always call RUBE_SEARCH_TOOLS before executing any tool and use the exact field names and types from the search results; do not hardcode slugs.

Can I reuse sessions across multiple tool executions?

Yes. Reuse session IDs within a workflow and generate new ones for new workflows; memory must be included in each multi-tool call.

givebutter-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Givebutter Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/givebutter

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Givebutter operations via Composio's Givebutter toolkit through Rube MCP. It keeps workflows aligned with current tool schemas by always running RUBE_SEARCH_TOOLS before execution.

How This Skill Works

The workflow starts by querying RUBE_SEARCH_TOOLS to fetch available Givebutter tool schemas. It then validates the connection with RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL using exact field names from the search results, including memory.

When to Use It

When you need the latest Givebutter tools and schemas before running an automation
When you must verify the Givebutter connection is ACTIVE before workflows
When you want to execute a discovered tool slug with the correct, schema-compliant arguments
When performing bulk or multi-tool execution via RUBE_MULTI_EXECUTE_TOOL
When handling changes in tool schemas or pagination in responses

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS is available
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["givebutter"] and confirm the connection is ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and exact arguments, including memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty {})
Reuse session IDs within a workflow and handle pagination tokens

Example Use Cases

Automate a basic donation flow by discovering tools with RUBE_SEARCH_TOOLS and executing a slug with correct arguments
Set up a Givebutter connection via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status before running a workflow
Execute multiple Givebutter actions in one workflow using RUBE_MULTI_EXECUTE_TOOL and memory payloads
Fetch updated tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt to API changes
Handle paginated tool lists by iterating RUBE_SEARCH_TOOLS until all results are fetched

Frequently Asked Questions

Add this skill to your agents