How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before execution to fetch the latest tool slugs and input schemas.

What if the connection is not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with toolkit 'chmeetings', follow the returned auth link, then retry until ACTIVE.

Is memory required in execute calls?

Yes. Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

chmeetings-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Chmeetings Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/chmeetings

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["chmeetings"]
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 Chmeetings-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `chmeetings`
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/chmeetings-automation/SKILL.mdView on GitHub

Overview

Automate Chmeetings operations through Composio's Chmeetings toolkit via Rube MCP. It requires an active Rube MCP connection and an established Chmeetings link, and you must call RUBE_SEARCH_TOOLS first to fetch current tool schemas. This approach speeds routine tasks and minimizes manual errors by ensuring you always use up-to-date tool slugs and arguments.

How This Skill Works

First, fetch available Chmeetings tools and their input schemas by calling RUBE_SEARCH_TOOLS. Then verify the connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE before execution. Finally, run the selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying exact field names and a memory object, and reuse session_id across steps if needed.

When to Use It

Automate scheduling, updating, or canceling Chmeetings events by discovering the right tool first.
Verify the Chmeetings connection is ACTIVE before running workflows.
Re-fetch tool schemas with RUBE_SEARCH_TOOLS when tool slugs or arguments change.
Reuse a session_id across multiple steps in a single Chmeetings workflow.
Run multi-tool sequences and manage memory state while handling pagination.

Quick Start

Step 1: Ensure RUBE MCP is connected and run RUBE_SEARCH_TOOLS for Chmeetings tasks.
Step 2: Run RUBE_MANAGE_CONNECTIONS to confirm the toolkit is ACTIVE.
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing memory and the current session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing tools.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs.

Example Use Cases

Discover and execute a schedule_meeting tool to auto-create a weekly standup.
Connect to Chmeetings and update attendees via the appropriate tool after confirming ACTIVE.
Run a sequence across tools to adjust a meeting time, reusing the same session_id.
When tool schemas change, re-run RUBE_SEARCH_TOOLS and execute the updated tool without hardcoding slugs.
Process a multi-page attendee list by fetching pages and preserving results in memory across steps.

Frequently Asked Questions

Add this skill to your agents