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

agent tool_use skill risk: medium

Echtpost Automation via Rube MCP

Provides instructions for automating Echtpost operations through Composio's Echtpost toolkit using Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_T…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["echtpost"]
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 Echtpost-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `echtpost` |
| 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)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • echtpost toolkit connection status

OPTIONAL CONTEXT

  • existing session_id
  • specific Echtpost use_case

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. Always discover available tools before executing workflows.
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds.
  5. If connection is not ACTIVE, follow the returned auth link to complete setup.
  6. Confirm connection status shows ACTIVE before running any workflows.
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS.
  8. Check connection: 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. Generate new ones for new workflows.
  12. Check responses for pagination tokens and continue fetching until complete.

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Always search first
  • Verify ACTIVE connection before execution
  • Use schema-compliant arguments from search results
  • Reuse session IDs within workflows

FAILURE MODES

  • Hardcoding tool slugs or arguments without search
  • Executing before confirming ACTIVE connection
  • Omitting memory parameter in execute calls
  • Ignoring pagination tokens

EXAMPLES

Includes multiple example RUBE tool calls (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) with parameters and a quick-reference table.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Echtpost connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target output format or response style expected from the agent using this prompt
  • Error handling or fallback steps when tools return errors
Ambiguities
  • Session parameter shown as 'session' in one example and 'session_id' in others without explicit mapping between them.

QUALITY

OVERALL
0.80
CLARITY
0.88
SPECIFICITY
0.78
REUSABILITY
0.82
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace generic placeholders like 'your specific Echtpost task' with 2-3 concrete example use cases.
  • Add a minimal end-to-end example showing a complete successful workflow with sample tool responses.

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