What is gagelist-automation?

A framework to automate gagelist operations through Composio's gagelist toolkit using Rube MCP, with a focus on discovering current tool schemas before execution.

Why must tools be discovered first?

Tool schemas change over time. Running RUBE_SEARCH_TOOLS returns available tool slugs, input schemas, and recommended execution plans, preventing hard-coded errors.

What must be included in RUBE_MULTI_EXECUTE_TOOL calls?

Include a memory object (even if empty) and use exact schema-compliant arguments from the search results; avoid hardcoding tool slugs or arguments.

gagelist-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Gagelist Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gagelist

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Gagelist operations through Composio's Gagelist toolkit using Rube MCP. Always search for current tool schemas first to ensure compatibility and avoid hard-coded slugs.

How This Skill Works

The workflow is: discover available gagelist tools with RUBE_SEARCH_TOOLS, verify the active connection via RUBE_MANAGE_CONNECTIONS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments. Always include a memory object and reuse session IDs to maintain state across steps.

When to Use It

When setting up a new gagelist automation workflow and you need current tool schemas.
During routine gagelist batch operations that require multiple tool calls in a single session.
When tool schemas change and you must refresh slugs and argument names before execution.
Before running any gagelist workflow to confirm the connection is ACTIVE.
When integrating gagelist tasks into an automated pipeline and avoiding hard-coded tool references.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config.
Step 2: Verify RUBE_SEARCH_TOOLS responds and ensure the gagelist connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute with RUBE_MULTI_EXECUTE_TOOL using the returned slug and arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS before selecting tools to use current schemas.
Check RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status prior to execution.
Use exact field names and types from the tool schemas; do not hardcode slugs or args.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow to maintain continuity and avoid resets.

Example Use Cases

Automate nightly gagelist updates by discovering tools, validating the ACTIVE connection, and executing the relevant tool with a memory payload.
Orchestrate a batch operation: discover multiple gagelist tools, verify connection, and run them in sequence within a single session.
Onboard a new gagelist workflow by querying current tool schemas, updating your automation script, and performing a test run.
Integrate gagelist tasks into an ETL-like pipeline: discover tools, manage connections, and execute with schema-compliant arguments.
Run a fault-tolerant gagelist routine that handles pagination tokens from RUBE_SEARCH_TOOLS and continues until complete.

Frequently Asked Questions

Add this skill to your agents