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

agent tool_use skill risk: medium

Rube MCP Autom Task Automation

The prompt instructs the model to automate Autom operations via Composio's toolkit through Rube MCP by always calling RUBE_SEARCH_TOOLS first, verifying ACTIVE connections with RUB…

  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["autom"]
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 Autom-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `autom` |
| 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
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

OPTIONAL CONTEXT

  • session_id
  • use_case description

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

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 autom
  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. Always discover available tools before executing workflows
  8. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  9. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  10. Use exact field names and types from the search results
  11. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  12. Reuse session IDs within a workflow
  13. Generate new session IDs for new workflows
  14. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • follow core workflow pattern
  • check connection status

FAILURE MODES

  • Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Fail to verify connection status before executing tools
  • Omit memory parameter from RUBE_MULTI_EXECUTE_TOOL calls
  • Fail to reuse session IDs within a workflow
  • Ignore pagination tokens in responses

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Autom connection via RUBE_MANAGE_CONNECTIONS with toolkit autom

QUALITY

OVERALL
0.85
CLARITY
0.90
SPECIFICITY
0.85
REUSABILITY
0.80
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder "your specific Autom task" with an explicit instruction to insert the concrete task description.
  • Add an example of a complete end-to-end tool call sequence for one common Autom operation.

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