Why must I search tools first?

Tool schemas change; always fetch current tool slugs and schemas via RUBE_SEARCH_TOOLS.

What indicates a healthy connection?

RUBE_MANAGE_CONNECTIONS status ACTIVE.

Yes, always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.

memberspot-automation

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

Files (1)

SKILL.md

2.9 KB

Memberspot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/memberspot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Memberspot operations through Composio's Memberspot toolkit via Rube MCP. It emphasizes discovering tool schemas first to stay current and avoid hardcoding tool slugs.

How This Skill Works

Leveraging RUBE_SEARCH_TOOLS, the skill discovers available Memberspot tools and their input schemas. It then validates the active connection with RUBE_MANAGE_CONNECTIONS before executing tools using RUBE_MULTI_EXECUTE_TOOL. Always include memory in tool calls and rely on current schemas rather than fixed slugs to ensure compatibility.

When to Use It

You need to perform a Memberspot operation and want to fetch current tool schemas first.
You must verify the Memberspot connection is ACTIVE before starting a workflow.
You want to run a sequence of tool executions in a single session, reusing session IDs.
You need to handle dynamic tool schemas or paginate tool lists.
You plan a bulk or multi-tool workflow for a Memberspot campaign.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Memberspot tool schemas.
Step 3: Use RUBE_MANAGE_CONNECTIONS to connect to Memberspot and then RUBE_MULTI_EXECUTE_TOOL to run a tool with memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the tool schemas; avoid hardcoding.
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

Create a new Memberspot event with attendee invites using the discovered tool.
Sync attendees from an external CRM to a Memberspot event.
Update event details (date/time) using the appropriate tool slug from the current schema.
List all available Memberspot tools to audit tool coverage via RUBE_SEARCH_TOOLS.
Run a mini-workflow that searches tools, connects, and executes a create-event tool in one session.

Frequently Asked Questions

Add this skill to your agents