Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Abuselpdb Automation via Rube MCP

agent tool_use skill risk: high

Abuselpdb Automation via Rube MCP

Instructs on automating Abuselpdb operations through Composio's Abuselpdb toolkit via Rube MCP, requiring RUBE_SEARCH_TOOLS calls first for schemas followed by connection managemen…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: abuselpdb-automation
description: "Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Abuselpdb Automation via Rube MCP

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

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

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `abuselpdb`
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: "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](https://composio.dev)*

INPUTS

use_case REQUIRED

Abuselpdb task description for tool discovery

e.g. Abuselpdb operations

session_id

existing workflow session identifier

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • Abuselpdb connection status via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • session_id
  • specific use_case for tool search

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit abuselpdb
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Prerequisites, Setup, Tool Discovery, Core Workflow Pattern, Known Pitfalls, Quick Reference
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from RUBE_SEARCH_TOOLS

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments
  • Include memory parameter
  • Reuse sessions appropriately

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing before connection is ACTIVE
  • Using incorrect field names from outdated schemas
  • Omitting the memory parameter in execute calls
  • Not handling pagination

EXAMPLES

Includes multiple example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Abuselpdb connection via RUBE_MANAGE_CONNECTIONS

QUALITY

OVERALL
0.82
CLARITY
0.85
SPECIFICITY
0.90
REUSABILITY
0.75
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace the inline example `queries: [{use_case: "your specific Abuselpdb task"}]` with an explicit placeholder token such as `{{USE_CASE}}` for easier templating.
  • Add a one-line success criterion at the end of the Core Workflow Pattern section (e.g., "Workflow succeeds when all tool responses contain `status: success` and no pagination tokens remain").

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT