home / skills / composiohq / awesome-claude-skills / turbot-pipes-automation

turbot-pipes-automation skill

safe

/turbot-pipes-automation

This skill automates Turbot Pipes tasks via Rube MCP, first discovering current tool schemas to ensure accurate, up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill turbot-pipes-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: turbot-pipes-automation
description: "Automate Turbot Pipes tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Turbot Pipes Automation via Rube MCP

Automate Turbot Pipes operations through Composio's Turbot Pipes toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/turbot_pipes](https://composio.dev/toolkits/turbot_pipes)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["turbot_pipes"]
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 Turbot Pipes-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `turbot_pipes` |
| 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 Turbot Pipes tasks through Composio's Rube MCP interface, providing a repeatable pattern to discover tools, validate connections, and execute operations. It enforces dynamic tool discovery so your workflows remain schema-compliant and resilient to toolkit changes. The skill is implemented in Python and designed for safe, paginated, and session-aware automation.

How this skill works

The skill always calls RUBE_SEARCH_TOOLS first to retrieve current tool slugs, input schemas, and execution plans. It checks and manages toolkit connections via RUBE_MANAGE_CONNECTIONS, ensuring the Turbot Pipes connection is ACTIVE before any actions. Execution uses RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs) with schema-compliant arguments, an explicit memory object, and controlled session reuse.

When to use it

Automate repetitive Turbot Pipes operations across environments
Integrate Turbot Pipes actions into CI/CD pipelines or agent workflows
Run bulk or parallel Turbot Pipes tasks with schema-driven inputs
Ensure workflows remain stable when toolkit schemas change
Orchestrate multi-step workflows that require session state and pagination handling

Best practices

Always run RUBE_SEARCH_TOOLS at the start of each workflow to fetch current tool schemas and recommended args
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE for the turbot_pipes toolkit before execution
Use exact field names and types returned by the search; do not hardcode slugs or payload shapes
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}), to avoid execution errors
Reuse session IDs within a workflow and generate new ones for separate workflows; handle pagination tokens until completion

Example use cases

Discover available Turbot Pipes tool operations then execute a configuration change across accounts
Authenticate and validate a turbot_pipes connection, then run a batch provisioning workflow via RUBE_REMOTE_WORKBENCH
Integrate into an agent that dynamically queries available Turbot Pipes schemas and builds compliant payloads before execution
Drive a scheduled bulk cleanup or reporting job that handles pagination and session state

FAQ

Do I need API keys to use Rube MCP with this skill?

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

What if RUBE_SEARCH_TOOLS returns a different schema than I expect?

Stop and rebuild payloads using the returned schema. Never hardcode arguments. Use the provided schemaRef or call RUBE_GET_TOOL_SCHEMAS for full definitions to ensure compliance.