Do I need API keys to use Rube MCP for Sidetracker automation?

No. Get Rube MCP set up by adding https://rube.app/mcp as an MCP server; no API keys are required.

What happens if tool schemas change between runs?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode tool slugs or arguments, and adapt to the returned input schemas.

Why is the memory parameter required in RUBE_MULTI_EXECUTE_TOOL?

Memory preserves state between tool calls within a session. Include memory in every execute call, even if empty ({}) to ensure proper continuity.

sidetracker-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sidetracker Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sidetracker

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["sidetracker"]
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 Sidetracker-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `sidetracker`
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/sidetracker-automation/SKILL.md

View on GitHub

Overview

This skill automates Sidetracker operations through Composio's Sidetracker toolkit using Rube MCP. It emphasizes always querying RUBE_SEARCH_TOOLS first to fetch current tool schemas and uses RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE Sidetracker connection before execution.

How This Skill Works

You connect Rube MCP to Sidetracker, then discover available tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas. Next, verify or establish an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, and finally run tools with RUBE_MULTI_EXECUTE_TOOL using the discovered schema fields, including a memory object, within a session_id.

When to Use It

When starting a Sidetracker workflow and you need the latest tool schemas
When reusing a session_id across multiple Sidetracker steps to maintain context
When verifying that the Sidetracker connection is ACTIVE before tool execution
When you need to inspect tool input schemas and recommended execution plans before running
When performing bulk Sidetracker operations via RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Ensure RUBE_SEARCH_TOOLS responds and fetch current Sidetracker tool schemas
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'sidetracker' and verify ACTIVE
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {}, and an active session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to fetch current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools
Use exact field names and types from the discovered schemas
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow where appropriate and generate new ones for new workflows

Example Use Cases

Discover the Sidetracker tools with RUBE_SEARCH_TOOLS, select a task like 'log_task', and execute it via RUBE_MULTI_EXECUTE_TOOL using the returned schema
If RUBE_MANAGE_CONNECTIONS shows INACTIVE, follow the auth link to reconnect, then continue with the workflow
Run a sequence of tools within the same session_id to complete a multi-step Sidetracker operation
Perform bulk updates on multiple Sidetracker items using RUBE_REMOTE_WORKBENCH and run_composio_tool
Fetch the latest tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt automation when tools change

Frequently Asked Questions

Add this skill to your agents