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

agent tool_use skill risk: medium

Abstract Toolkit Automation via Rube MCP

Instructs on automating Abstract operations through Composio's Abstract toolkit via Rube MCP, covering prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, connection…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

**Toolkit docs**: [composio.dev/toolkits/abstract](https://composio.dev/toolkits/abstract)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["abstract"]
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 Abstract-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `abstract` |
| 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

Description of the Abstract operation to perform

e.g. Abstract operations

session_id

Session identifier for tool calls

tool_slug REQUIRED

Tool identifier returned by search

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • Abstract connection status via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • specific use_case for Abstract task
  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. Call RUBE_MANAGE_CONNECTIONS with toolkit abstract
  6. Confirm connection status shows ACTIVE before running any 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
Constraints
  • follow exact Rube tool call patterns
  • always search tools first
  • reuse session IDs

SUCCESS CRITERIA

  • Verify Rube MCP is available
  • Establish ACTIVE Abstract connection
  • Discover tools via RUBE_SEARCH_TOOLS before execution
  • Execute tools using discovered schemas and session IDs

FAILURE MODES

  • Hardcoding tool slugs or arguments without searching first
  • Executing tools before confirming ACTIVE connection
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse or correctly manage session IDs

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Abstract connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target user or agent environment (e.g., specific MCP client)
  • Concrete examples of Abstract tasks or use cases
  • Error handling or fallback behavior when tools fail
Ambiguities
  • The exact format and parameters for tool calls (e.g., 'generate_id: true', 'queries' structure) are shown inconsistently between code blocks and prose.
  • Does not specify desired output length or response format from the agent executing the workflow.

QUALITY

OVERALL
0.76
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.75
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Add a short 'Example Task' section showing a complete end-to-end call sequence with realistic values.
  • Replace pseudo-code blocks with a single consistent JSON or YAML call template.
  • Explicitly state whether the prompt is intended for an LLM agent or a human developer.

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