How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing any Short Menu tool to fetch the latest slugs and input schemas.

What if the Short Menu connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and recheck until status shows ACTIVE.

Do I need API keys for the MCP server?

No API keys are needed for the MCP server; you only add the endpoint (e.g., https://rube.app/mcp) in your client configuration.

short-menu-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Short Menu Automation via Rube MCP

Automate Short Menu operations through Composio's Short Menu toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/short_menu

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Short Menu operations using Composio's Short Menu toolkit through Rube MCP. Always search tools first to fetch current tool schemas, ensuring up-to-date integration.

How This Skill Works

The workflow: discover available Short Menu tools with RUBE_SEARCH_TOOLS, verify the connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and runtime arguments. Include memory in executions and reuse sessions for seamless workflows.

When to Use It

You need to run a Short Menu task and want to dynamically select the tool based on current schemas.
You must verify your Rube MCP connection is ACTIVE before executing Short Menu tools.
You want to automate a sequence of Short Menu operations with a single workflow.
You are integrating Short Menu tasks into a larger automation pipeline with session management.
You need to bulk-run or reuse discovered tool configurations while handling pagination and updates.

Quick Start

Step 1: Ensure Rube MCP is configured as an MCP server and that RUBE_SEARCH_TOOLS is available.
Step 2: Discover tools with RUBE_SEARCH_TOOLS for your Short Menu use case and note the tool slug and input schema.
Step 3: Check connectivity with RUBE_MANAGE_CONNECTIONS, then execute a tool using RUBE_MULTI_EXECUTE_TOOL with memory and the discovered slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and avoid hardcoding slugs.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before tool execution.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when it’s empty.
Reuse session IDs within a workflow to maintain context; generate new IDs for new workflows.

Example Use Cases

Discover available Short Menu tools for a specific use case, then execute the best-matching tool slug with proper arguments.
Establish an ACTIVE Short Menu connection, then run a sequence of tools in a single session for a batch operation.
Handle tool schema changes by re-running RUBE_SEARCH_TOOLS before each execution to adapt slugs and args.
Resolve an INACTIVE connection by following the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup and retry.
Use RUBE_REMOTE_WORKBENCH to run multiple composio_tool calls in bulk, validating schemas with RUBE_GET_TOOL_SCHEMAS.

Frequently Asked Questions

Add this skill to your agents