Do I need API keys to use this skill?

No. Add the MCP server endpoint and rely on RUBE_SEARCH_TOOLS to fetch current tool schemas; no keys are required for basic usage.

How do I find current tool schemas?

Run RUBE_SEARCH_TOOLS with use_case set to 'Evenium operations' to retrieve tool slugs, input schemas, recommended execution plans, and known pitfalls.

What if tool slugs change?

Always search for tools first (RUBE_SEARCH_TOOLS) and avoid hardcoding slugs or arguments; adapt your workflow to the latest schemas.

evenium-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Evenium Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/evenium

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Evenium operations through Composio's Evenium toolkit via Rube MCP. It guides you to discover current tool schemas, securely connect to Evenium, and execute the appropriate tools with schema-compliant arguments.

How This Skill Works

Start by discovering available tools with RUBE_SEARCH_TOOLS using the use_case 'Evenium operations'. Then establish an ACTIVE connection to Evenium via RUBE_MANAGE_CONNECTIONS with the toolkit 'evenium'. Finally, execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required memory payload and a valid session_id.

When to Use It

Automating recurring Evenium workflows (e.g., event updates or attendee actions) that require current tool schemas.
Onboarding a new Evenium integration where you must fetch and validate tool schemas before use.
Building multi-step workflows that should reuse a single session for efficiency.
Performing bulk operations via RUBE_REMOTE_WORKBENCH with run_composio_tool to speed up batch tasks.
Integrating Evenium tasks within larger Composio workflows while ensuring the connection is ACTIVE first.

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) to your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["evenium"] and ensure the connection is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools for your Evenium task, then execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results to maintain schema compliance.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty ({}).
Reuse session IDs within a workflow and generate new ones only for new workflows.

Example Use Cases

Automatically sync attendee status by discovering the appropriate Evenium tool and executing it after a registration event.
Discover scheduling tools and update an event in Evenium using the correct input schemas.
Run a post-event cleanup task by exporting reports through a discovered Evenium tool.
Execute bulk attendee communications by leveraging RUBE_REMOTE_WORKBENCH with run_composio_tool().
Perform a daily health check: discover tools, ensure ACTIVE connection, and run a status-check tool.

Frequently Asked Questions

Add this skill to your agents