What is required to start?

Add https://rube.app/mcp as an MCP server; no API keys are needed.

Why should I search tools first?

Tool schemas change over time; never hardcode slugs or arguments—always call RUBE_SEARCH_TOOLS to get current schemas.

What about memory and sessions?

Include the memory parameter in every RUBE_MULTI_EXECUTE_TOOL call (even if empty) and reuse session IDs within a workflow; generate new IDs for new tasks.

chaser-automation

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

Files (1)

SKILL.md

2.8 KB

Chaser Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/chaser

Prerequisites

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

Step 2: Check Connection

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

Overview

Chaser Automation via Rube MCP lets you orchestrate Chaser operations through Composio’s Chaser toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active connection to the Chaser toolkit. This ensures you always run up-to-date tools without hardcoding slugs.

How This Skill Works

First, discover available tools with RUBE_SEARCH_TOOLS. Then verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for toolkit 'chaser'. Finally, execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL, passing the tool_slug and memory payload, within a session.

When to Use It

Discover and select a Chaser tool with RUBE_SEARCH_TOOLS before starting a task
Establish or verify an active Rube MCP connection for the chaser toolkit
Execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with the appropriate arguments
Reuse a session ID across multiple tool executions within a single workflow
Handle tool/schema changes by re-searching tools before every run

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds and list available Chaser tools.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'chaser' and ensure ACTIVE.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow; generate new IDs for new tasks

Example Use Cases

Automate a routine Chaser health-check by discovering tools, connecting, and executing a chosen slug.
Update and adapt a workflow after a tool schema change by re-searching tools first.
Reuse a session ID across multiple tool executions in a single Chaser task.
Batch multiple Chaser tools in one run using RUBE_MULTI_EXECUTE_TOOL with a shared memory payload.
Perform bulk Chaser operations via RUBE_REMOTE_WORKBENCH and run_composio_tool.

Frequently Asked Questions

Add this skill to your agents