What is required to start using clearout-automation?

You need a connected Rube MCP, an active Clearout toolkit connection, and you must call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

Should I rerun RUBE_SEARCH_TOOLS before every execution?

Yes, to ensure you have the latest tool slugs and input schemas and to avoid hardcoding.

How should memory be used in tool execution?

Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) to preserve state and context.

clearout-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Clearout Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/clearout

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Clearout operations through Composio's Clearout toolkit using Rube MCP. It requires an active Rube MCP connection and a Clearout toolkit, and it mandates calling RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How This Skill Works

Connect to Rube MCP, verify availability with RUBE_SEARCH_TOOLS, and discover available Clearout tools. Confirm the toolkit connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the proper tool_slug and arguments, always including memory. Use the latest schemas to ensure correct field names and types.

When to Use It

You need to automate a Clearout operation end-to-end without manually selecting tools.
Tool schemas may have changed; you must fetch current slugs and arguments before running.
You want to validate that the Clearout connection is ACTIVE before executing workflows.
Perform bulk Clearout actions and prefer reusing an existing session across steps.
You’re implementing a multi-step Clearout workflow: discover tools, verify connection, then execute.

Quick Start

Step 1: Add the MCP endpoint (https://rube.app/mcp) as an MCP server and confirm RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS with use_case: 'Clearout operations' to discover tool slugs and schemas; pick the desired tool.
Step 3: Connect to the toolkit with RUBE_MANAGE_CONNECTIONS (toolkit: 'clearout'), then execute the tool with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover a Clearout operation tool (e.g., delete_inactive_contacts) and execute with appropriate arguments such as {days_inactive: 365}.
Batch-clean multiple datasets by iterating discovery and execution steps using the latest tool slugs from RUBE_SEARCH_TOOLS.
Validate the Clearout connection is ACTIVE, then run a scheduled cleanup workflow within a single session.
Perform bulk operations via RUBE_REMOTE_WORKBENCH using run_composio_tool for speed and scalability.
After a tool update, re-run RUBE_SEARCH_TOOLS to obtain new schemas and adapt your arguments accordingly.

Frequently Asked Questions

Add this skill to your agents