home / skills / composiohq / awesome-claude-skills / winston-ai-automation

winston-ai-automation skill

/winston-ai-automation

This skill automates Winston AI workflows via Rube MCP, always discovering current tool schemas first to ensure accurate tool execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill winston-ai-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.9 KB
---
name: winston-ai-automation
description: "Automate Winston AI tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `winston_ai`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Winston AI tasks through Rube MCP (Composio) and provides a repeatable pattern for discovering, connecting, and executing Composio tools. It enforces a strict discovery-first approach so tool slugs and input schemas stay current. The workflow focuses on safe execution: search tools, confirm connections, then run tools with schema-compliant arguments.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, and recommended execution plans. It then verifies an active Winston AI connection via RUBE_MANAGE_CONNECTIONS. Finally it runs tools using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk ops), always including a memory object and correct session handling.

When to use it

  • Automate Winston AI operations that require Composio tool calls
  • Run multi-step workflows relying on current tool schemas
  • Perform bulk or remote operations with Rube MCP orchestration
  • Integrate Winston AI tasks into larger agent workflows
  • When you need robust session and connection checks before execution

Best practices

  • Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas
  • Verify toolkit connection status with RUBE_MANAGE_CONNECTIONS and complete auth links if not ACTIVE
  • Pass schema-compliant arguments exactly as returned by the search results
  • Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
  • Reuse session IDs within a workflow; generate new sessions for new workflows
  • Handle pagination tokens in search responses and iterate until complete

Example use cases

  • Discover and run Winston AI text or classification tools discovered via RUBE_SEARCH_TOOLS
  • Automate bulk processing using RUBE_REMOTE_WORKBENCH with run_composio_tool() batching
  • Set up a workflow template: search tools, validate connection, execute tool chain with RUBE_MULTI_EXECUTE_TOOL
  • Build an agent that adapts to changing tool schemas by always fetching schemas before each run
  • Orchestrate a multi-step Winston AI pipeline while managing session state and memory between calls

FAQ

What is the first call I should make when using this skill?

Always start with RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas.

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and use the provided Rube MCP endpoints.