What is seat-geek-automation?

A skill to automate Seat Geek tasks using Composio's Rube MCP toolkit.

What prerequisites are required?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Seat Geek connection via RUBE_MANAGE_CONNECTIONS with toolkit seat_geek. Always search tools first.

What is the recommended workflow?

Discover tools with RUBE_SEARCH_TOOLS, verify via RUBE_MANAGE_CONNECTIONS, then execute with RUBE_MULTI_EXECUTE_TOOL, including memory, and reuse sessions as appropriate.

seat-geek-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Seat Geek Automation via Rube MCP

Automate Seat Geek operations through Composio's Seat Geek toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/seat_geek

Prerequisites

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

Step 2: Check Connection

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

Overview

Leverages Composio's Seat Geek toolkit via Rube MCP to automate Seat Geek operations. It emphasizes discovering current tool schemas first, establishing an active connection, and executing workflows in a repeatable, session-based pattern.

How This Skill Works

Start by calling RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas for seat_geek. Then establish a connection with RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE. Finally, execute the discovered tool(s) using RUBE_MULTI_EXECUTE_TOOL, supplying a memory object and a session_id.

When to Use It

You need to perform a specific Seat Geek operation without manual UI intervention.
Tool schemas may change; you must fetch current schemas before running any tool.
You want to confirm an ACTIVE Seat Geek connection before executing tools.
You want to batch multiple Seat Geek actions in a single workflow using memory and session management.
You automate recurring Seat Geek tasks and reuse session IDs where appropriate.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: 'Seat Geek operations'}].
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['seat_geek'] and check for ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug, with memory: {} and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Do not hardcode tool slugs or argument fields; rely on the latest schemas.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse a session_id for related steps and paginate responses as needed.

Example Use Cases

Discover tools for Seat Geek operations with RUBE_SEARCH_TOOLS, then execute a tool to fetch events for a venue on a given date.
Connect to Seat Geek via RUBE_MANAGE_CONNECTIONS and run a tool to list upcoming concerts, ensuring ACTIVE status.
Run a complete workflow: discover tools, verify connection, then execute a tool with a valid session_id and memory.
If tool schemas change, re-run RUBE_SEARCH_TOOLS to update slugs and arguments before execution.
Use RUBE_MULTI_EXECUTE_TOOL to perform multiple operations in one session, reusing session_id and memory across calls.

Frequently Asked Questions

Add this skill to your agents