What is eventee-automation?

Eventee-automation is a skill to automate Eventee tasks using Composio's Rube MCP toolkit, with a focus on always discovering current tool schemas before execution.

How does it handle updated tool schemas?

ItAlways searches for tools first (RUBE_SEARCH_TOOLS) to fetch current slugs and input schemas, avoiding hardcoded values and ensuring schema compliance during execution.

eventee-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Eventee Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/eventee

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Eventee operations through Composio's Eventee toolkit via Rube MCP. It emphasizes discovering current tool schemas first to adapt to changes, then managing the Eventee connection and executing tools in a controlled sequence for reliable workflows.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to fetch available Eventee tool slugs and input schemas, then checks the connection with RUBE_MANAGE_CONNECTIONS and ensures the status is ACTIVE. Once ready, it executes a chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and a memory object, reusing sessions as needed.

When to Use It

Automating a recurring Eventee workflow (e.g., scheduling or updating events) where tool schemas may change
Need to discover current Eventee tool slugs and input schemas before running tasks
Verify and maintain an ACTIVE Eventee connection through Rube MCP prior to execution
Execute multiple tools in a single workflow using RUBE_MULTI_EXECUTE_TOOL with session reuse
Handle evolving tool schemas and pagination by re-discovering tools instead of hardcoding slugs

Quick Start

Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Eventee operations", known_fields: ""}] session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["eventee"] session_id: "your_session_id"
Step 3: RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */} }] memory: {} session_id: "your_session_id"

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results; avoid hardcoding slugs
Include memory parameter in RUBE_MULTI_EXECUTE_TOOL (even if empty)
Reuse session IDs within a workflow; check pagination tokens and continue

Example Use Cases

Example 1: Discover tools with RUBE_SEARCH_TOOLS for Eventee operations and run a selected tool with RUBE_MULTI_EXECUTE_TOOL
Example 2: Establish and verify an ACTIVE Eventee connection using RUBE_MANAGE_CONNECTIONS before a workflow
Example 3: Run a multi-step Eventee task by iterating over discovered tool slugs and supplying memory
Example 4: Re-discover schemas after an Eventee tool update to avoid hardcoding slugs
Example 5: Perform a bulk Eventee operation using RUBE_REMOTE_WORKBENCH with run_composio_tool

Frequently Asked Questions

Add this skill to your agents