$ ~/registry/skill/composiohq-composio-skills-listclean-automation

SKILL

listclean-automation

Discover and automate Listclean workflows through Rube MCP and Composio.

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 "listclean-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/listclean-automation/SKILL.md
2. Save it as ~/.claude/skills/listclean-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Integrate Listclean into an AI workflow

After connecting Rube in an MCP client, a developer can search for available Listclean tools first, then run automation with the latest schema to avoid broken hardcoded calls.

Connection troubleshooting before execution

Before running any Listclean workflow, the user can verify that the listclean connection is ACTIVE to reduce failures caused by missing authorization or inactive connections.

Run discovered tools in bulk

For bulk processing, users can build execution flows from the discovered tools and schemas while reusing the session, including memory, and handling paginated results.

// docs

AI summary

This README explains how to automate the Composio Listclean toolkit through Rube MCP. It covers prerequisites, connection setup, and the recommended workflow: search for tools first, verify the Listclean connection is active, and then execute with the discovered schema. It also highlights key pitfalls such as avoiding hardcoded arguments, reusing session IDs, always including the memory parameter, and handling pagination or full schema lookups when needed.

Show full docs ▾

Listclean Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/listclean

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["listclean"]
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 Listclean-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `listclean`
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 does this skill do?

It lets you automate Listclean-related operations through Rube MCP using Composio’s Listclean toolkit. The docs emphasize searching for tools first, then executing with the latest returned schema.

What are the prerequisites for setup?

You need to add the Rube MCP server at `https://rube.app/mcp` in your client and confirm `RUBE_SEARCH_TOOLS` is available. You also need to configure and activate the `listclean` connection through `RUBE_MANAGE_CONNECTIONS`; the docs say no separate API key is required.

Why must I search tools first instead of hardcoding arguments?

Because tool schemas can change, the docs explicitly require calling `RUBE_SEARCH_TOOLS` first to get the current tool slug and argument structure. Execution also requires exact field names and types, and `memory` must always be included in `RUBE_MULTI_EXECUTE_TOOL`.

Automate Langbase workflows through Rube MCP using current tool schemas.

ComposioGet→

$ loading_