How do I ensure tool schemas stay up to date?

Always run RUBE_SEARCH_TOOLS before executing tools; tool schemas can change and must be referenced exactly.

What if the Waiverfile connection is not ACTIVE?

Follow the auth flow returned by RUBE_MANAGE_CONNECTIONS and re-check status until it shows ACTIVE.

Is the memory parameter required?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is an empty object {}.

waiverfile-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Waiverfile Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/waiverfile

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Waiverfile operations through Composio's Waiverfile toolkit via Rube MCP. This enables end-to-end tasks like discovery, connection management, and tool execution with up-to-date schemas.

How This Skill Works

First, use RUBE_SEARCH_TOOLS to discover current Waiverfile tools and their schemas. Then verify the Waiverfile connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing memory and a session_id to maintain context.

When to Use It

You need to automate a Waiverfile operation via MCP using the Waiverfile toolkit.
You must ensure tool schemas are current before running any workflow.
You want to connect Waiverfile to Rube MCP and manage its connection status.
You perform batch or automated Waiverfile tasks using RUBE_MULTI_EXECUTE_TOOL.
You are handling long-running or paginated Waiverfile data fetches and need consistent context.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["waiverfile"] and ensure ACTIVE status.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the received slug and memory ({}), along with a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens when listing results.

Example Use Cases

On a new form submission, discover the Waiverfile create tool and auto-create a waiver entry.
After an approval step, update the waiver status using the Waiverfile update tool with the correct arguments.
Bulk import dozens of waivers by using a bulk Waiverfile operation via RUBE_REMOTE_WORKBENCH run_composio_tool.
Schedule a nightly audit that lists waivers and exports results after discovering latest schemas.
Maintain context in a long waiver processing job by reusing the same session_id across steps.

Frequently Asked Questions

Add this skill to your agents