home / skills / composiohq / awesome-claude-skills / clearout-automation

clearout-automation skill

safe

/clearout-automation

This skill automates Clearout tasks via Rube MCP, ensuring up-to-date tool schemas are discovered before execution for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill clearout-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: clearout-automation
description: "Automate Clearout tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Clearout Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/clearout](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clearout`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Clearout tasks through Composio’s Clearout toolkit using Rube MCP. It provides a reliable workflow for discovering current tool schemas, managing toolkit connections, and executing Clearout operations programmatically. The skill emphasizes safety checks and schema compliance to avoid runtime errors.

How this skill works

Before any action it always calls RUBE_SEARCH_TOOLS to discover available Clearout tools and their exact input schemas. It verifies an active Clearout connection via RUBE_MANAGE_CONNECTIONS, then runs operations with RUBE_MULTI_EXECUTE_TOOL (including an explicit memory object and a session_id). The pattern supports pagination, session reuse, and bulk runs via RUBE_REMOTE_WORKBENCH when needed.

When to use it

Automate email or data validation jobs that Clearout supports
Run large batches of Clearout checks with consistent, repeatable tooling
Integrate Clearout tasks into Claude-based or automated agent workflows
Ensure tool schema discovery before invoking remote operations
Orchestrate multi-step Clearout pipelines across sessions

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas change frequently
Confirm toolkit connection status with RUBE_MANAGE_CONNECTIONS and only proceed if ACTIVE
Pass the exact fields and types returned by the search result; do not hardcode inputs
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id within a workflow; generate new session_ids for new workflows
Handle pagination tokens when fetching lists or results

Example use cases

Discover current Clearout tool slugs and input schemas, then run single-item validation
Connect or reauthorize the Clearout toolkit when RUBE_MANAGE_CONNECTIONS reports non-ACTIVE
Execute bulk email validation by combining RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL, and RUBE_REMOTE_WORKBENCH
Build a multi-step agent that fetches data, validates with Clearout, then stores results in a downstream system
Automate nightly batches: generate a session_id, paginate through inputs, and run composio tools with consistent memory objects

FAQ

What should I always call before executing a tool?

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and exact input schemas.

What if the connection is not active?

Use RUBE_MANAGE_CONNECTIONS to get the auth link and complete setup; only run workflows after status is ACTIVE.