What is RUBE MCP in this context?

RUBE MCP is the central management plane used to discover tools, manage connections, and execute Abuselpdb workflows through the Composio toolkit.

What happens if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch current slugs and input schemas; do not hardcode tool slugs or arguments.

How do I ensure the Abuselpdb connection is ready?

Check the ACTIVE status via RUBE_MANAGE_CONNECTIONS before execution and follow any required auth steps if not active.

abuselpdb-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Abuselpdb Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/abuselpdb

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Abuselpdb operations through Composio's Abuselpdb toolkit via Rube MCP. It emphasizes discovering up-to-date tool schemas before each workflow and ensuring an active Abuselpdb connection.

How This Skill Works

The workflow starts by connecting to Rube MCP and confirming RUBE_SEARCH_TOOLS is available. It then manages an active Abuselpdb connection via RUBE_MANAGE_CONNECTIONS, discovers tools with RUBE_SEARCH_TOOLS, and finally executes the selected tool using RUBE_MULTI_EXECUTE_TOOL with memory and session IDs.

When to Use It

Starting a new Abuselpdb workflow requires current tool schemas via tool discovery.
When tool schemas or slugs may have changed and you must avoid hardcoding.
Before executing tools, verify the Abuselpdb connection is ACTIVE.
Running a multi-tool workflow that requires session reuse and memory payloads.
Handling paginated tool discovery results to fetch all available tools.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and connect via RUBE_MANAGE_CONNECTIONS with toolkits: [abuselpdb].
Step 3: Use RUBE_SEARCH_TOOLS to fetch tool schemas, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first for current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
Use exact field names and types from search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new ones only for new workflows.

Example Use Cases

Automate a data-sync tool by discovering the tool slug, connecting to abuselpdb, and executing with required args.
Run a nightly data cleanup by fetching the latest schema, ensuring connectivity, and performing the cleanup tool.
Fetch available tools for an Abuselpdb use case and execute a specific operation with user-provided parameters.
Perform a bulk operation using RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory payload.
Execute a full workflow from discovery to execution with session reuse in a single automation run.

Frequently Asked Questions

Add this skill to your agents