What is Winston AI Automation via Rube MCP?

A structured workflow to automate Winston AI tasks using Rube MCP and Composio toolkit, requiring tool discovery first.

Do I always need to search tools first?

Yes, to obtain current tool schemas and avoid hardcoding slugs or arguments.

What if the connection is not ACTIVE?

Follow the returned auth link to complete setup, then recheck until ACTIVE before running tools.

winston-ai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Winston AI Automation via Rube MCP

Automate Winston AI operations through Composio's Winston AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/winston_ai

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Winston AI operations through Composio's Winston AI toolkit via Rube MCP. This approach emphasizes always searching for current tool schemas before execution to keep integrations up-to-date. It requires a connected Rube MCP and an active Winston AI session.

How This Skill Works

Discover available Winston AI tools with RUBE_SEARCH_TOOLS, verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute tools using RUBE_MULTI_EXECUTE_TOOL with a memory payload. The process enforces using live schemas and avoids hardcoding tool slugs or arguments to prevent breakages.

When to Use It

When you want to automate a Winston AI task from discovery to execution in a single workflow.
When tool schemas change and you must fetch the latest tool slugs and input schemas via RUBE_SEARCH_TOOLS.
When you need to confirm the Winston AI connection is ACTIVE before executing tools.
When performing multiple tool executions in a single session (batch workflows) using RUBE_MULTI_EXECUTE_TOOL.
When reusing a session ID and handling pagination tokens to fetch all available tools.

Quick Start

Step 1: Ensure Rube MCP is configured (add https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'winston_ai' and complete the auth flow if required.
Step 3: Run RUBE_SEARCH_TOOLS for discovery, then execute a tool via RUBE_MULTI_EXECUTE_TOOL with memory payload and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE prior to executing tools.
Use exact field names and types from the search results to ensure schema compliance.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({ }).
Reuse session IDs within a workflow and handle pagination tokens to fetch all tools.

Example Use Cases

Discover a Winston AI tool with use_case: 'Winston AI operations' and execute its slug with required arguments in a single session.
Run a batch of Winston AI tasks across multiple tools in one session using RUBE_MULTI_EXECUTE_TOOL.
If RUBE_MANAGE_CONNECTIONS returns a non-ACTIVE status, follow the auth flow and recheck until ACTIVE.
Bulk operations can be performed via RUBE_REMOTE_WORKBENCH using run_composio_tool().
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS before integrating into a workflow.

Frequently Asked Questions

Add this skill to your agents