What is Rube MCP's role in this skill?

Rube MCP serves as the central controller to discover, connect, and execute Passslot tools via the passslot toolkit.

Why must I always search tools first?

Tool schemas and slugs change; you should fetch current schemas to avoid failures from stale information.

What must be included in each RUBE_MULTI_EXECUTE_TOOL call?

You must provide the tool_slug, the exact argument structure from the schema, a memory object (even if {}), and a valid session_id.

passslot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Passslot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/passslot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Passslot operations through Composio's Passslot toolkit using Rube MCP. Always fetch current tool schemas first to ensure correct slugs and arguments, and maintain an active Passslot connection for safe workflow execution.

How This Skill Works

You first query RUBE_SEARCH_TOOLS to obtain available Passslot tool slugs and their input schemas. Then verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and finally execute the desired tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, the required arguments, a memory object, and a session_id. This flow ensures adapters remain in sync with live schemas and supports session reuse.

When to Use It

When automating a Passslot workflow in a larger pipeline to ensure repeatable runs
When tool schemas change and you need to fetch current slugs and arguments before execution
When establishing or validating an ACTIVE Passslot connection prior to workflow execution
When performing batch or multi-tool Passslot operations in sequence or parallel (using memory and session)
When you need to reuse a session across steps to maintain continuity in a Passslot workflow

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to Passslot with RUBE_MANAGE_CONNECTIONS using toolkits: ['passslot'] and complete auth if needed; ensure ACTIVE
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, a session_id, and memory

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to get up-to-date slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the tool schemas returned by search
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and avoid hardcoding tool slugs

Example Use Cases

Discover tools for a Passslot task and execute the chosen tool slug with the required arguments
Set up and validate an ACTIVE Passslot connection before running workflows
Execute a batch of Passslot operations in a single session using RUBE_MULTI_EXECUTE_TOOL
Handle schema changes by always fetching current tool slugs via RUBE_SEARCH_TOOLS before execution
Complete a Passslot workflow by reusing a session_id across steps and including memory in calls

Frequently Asked Questions

Add this skill to your agents