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

agent tool_use skill risk: medium

Demio Automation via Rube MCP

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

  • Human review
  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["demio"]
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 Demio-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `demio` |
| 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
  • active Demio connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id
  • specific Demio 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. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit demio
  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. 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 ones for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • reuse session ids within workflow

SUCCESS CRITERIA

  • Verify connection is ACTIVE
  • Use schema-compliant arguments from search results
  • Follow core workflow pattern in order

FAILURE MODES

  • Hardcoding tool slugs or arguments
  • Skipping connection status check
  • Omitting memory parameter
  • Not reusing session IDs

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Demio connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Example of a complete end-to-end tool call sequence with realistic slugs and arguments
  • Error handling or retry strategy when connection status is not ACTIVE
Ambiguities
  • Placeholder text 'your specific Demio task' is not replaced with guidance on how to phrase queries.
  • 'generate_id: true' syntax is shown but not explained how the ID is produced or returned.

QUALITY

OVERALL
0.79
CLARITY
0.78
SPECIFICITY
0.72
REUSABILITY
0.81
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Replace the generic placeholder with 2-3 concrete Demio use-case query examples.
  • Add a short 'Success criteria' section stating what a completed workflow should return.

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