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

agent tool_use skill risk: medium

Apilio Automation via Rube MCP

The prompt provides instructions for automating Apilio operations through Composio's Apilio toolkit via Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEA…

  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["apilio"]
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 Apilio-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `apilio` |
| 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 Apilio task for tool search

e.g. your specific Apilio task

session_id

session identifier for tool calls and connections

e.g. existing_session_id

tool_slug REQUIRED

discovered tool identifier from search results

e.g. TOOL_SLUG_FROM_SEARCH

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active Apilio connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id
  • specific Apilio use case

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. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. 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 call RUBE_SEARCH_TOOLS first
  • include memory parameter even if empty
  • reuse session IDs within workflow

SUCCESS CRITERIA

  • Follow core workflow pattern using RUBE_SEARCH_TOOLS first
  • Confirm ACTIVE Apilio connection before execution
  • Use schema-compliant arguments from search results
  • Include memory and reuse session IDs

FAILURE MODES

  • Hardcoding tool slugs without prior search
  • Executing before verifying ACTIVE connection status
  • Omitting memory parameter in execute calls
  • Ignoring pagination tokens

EXAMPLES

Includes multiple example RUBE_* tool calls showing discovery, connection check, and execution patterns with sample arguments.

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Apilio connection via RUBE_MANAGE_CONNECTIONS
  • Rube MCP server configured at https://rube.app/mcp
Missing context
  • Target client or environment where Rube MCP is used
  • Example of a complete end-to-end task execution
Ambiguities
  • Placeholder text 'your specific Apilio task' left unresolved
  • Exact format of RUBE_* function calls (JSON vs. plain text) not specified
  • Meaning of 'memory: {}' parameter not explained

QUALITY

OVERALL
0.74
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.68
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace inline placeholders with explicit variables such as {{task_description}}
  • Add a minimal working example showing one full tool discovery + execution cycle

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