Do I need API keys for Demio with this skill?

No API keys are required. You add the Rube MCP endpoint and authenticate through the toolkit connection; Demio access is managed by the Demio toolkit via Rube MCP.

How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS before running workflows. Use the returned tool_slug and field names exactly as provided.

What if tool schemas change after I’ve started a workflow?

Re-run RUBE_SEARCH_TOOLS to refresh slugs and arguments, then restart or adapt the workflow to the new schemas.

demio-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/demio-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Demio Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit demio
If connection is not ACTIVE, follow the returned auth link to complete setup
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/demio-automation/SKILL.mdView on GitHub

Overview

Automates Demio operations using Composio's toolkit via Rube MCP. It prioritizes discovering current tool schemas with RUBE_SEARCH_TOOLS to adapt to updates, ensuring you never hardcode tool slugs or args. Requires an active Rube MCP connection and a working Demio connection to execute discovered tools in sequence.

How This Skill Works

The workflow starts by querying available Demio tools with RUBE_SEARCH_TOOLS to get tool slugs and schemas. It then validates the Demio connection with RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and schema-aligned arguments, including a memory object and a session_id for continuity.

When to Use It

Setting up a new Demio automation workflow and verifying tool schemas before use
Automating a sequence of Demio tasks (e.g., event creation, attendee updates) in a single session
Validating and establishing the Demio connection prior to execution
Working with changing tool schemas so you always fetch current slugs and fields
Bulk executions or batch operations using RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and confirm RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit demio and complete auth if needed; verify ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL using the provided memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to fetch current tool schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the tool schemas; avoid hardcoding slugs or args
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even when empty
Reuse session IDs within a workflow and fetch new ones for new workflows; monitor pagination

Example Use Cases

Create a Demio webinar and automatically update attendee lists across stages
Verify and connect the Demio toolkit, then perform a sequence of tool executions
Execute multiple Demio tasks in a single session using discovered tool slugs
Bulk run Demio actions via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Manage tool schemas dynamically by re-searching tools before each batch

Frequently Asked Questions

Add this skill to your agents