home / skills / composiohq / awesome-claude-skills / bart-automation

bart-automation skill

safe

/bart-automation

This skill automates Bart operations via Rube MCP, ensuring tools are discovered first and connections verified before executing workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill bart-automation

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

Files (1)

SKILL.md

2.8 KB

---
name: bart-automation
description: "Automate Bart tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bart Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["bart"]
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 Bart-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `bart` |
| 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 Bart tasks through Rube MCP using Composio's Bart toolkit. It provides a repeatable pattern to discover tools, validate connections, and execute toolkit operations reliably. The workflow emphasizes live tool discovery and strict schema compliance to avoid runtime failures.

How this skill works

The skill always begins by calling RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and execution guidance. It then verifies or establishes an active Bart connection via RUBE_MANAGE_CONNECTIONS. Actions are executed with RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs), supplying schema-compliant arguments, a session_id, and a memory object.

When to use it

Automating Bart workflows that require live tool schemas and connection state
Running multi-step Bart operations where session reuse is important
Performing bulk or remote Bart jobs using Composio tooling
Integrating Bart actions into larger Claude or agent-driven pipelines
When you need resilient automation that adapts to evolving tool schemas

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or input fields
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use exact field names and types returned by the search response to ensure schema compliance
Always include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id during a single workflow; generate new session_ids for new workflows
Handle pagination tokens from search responses and fetch until complete

Example use cases

Discover available Bart operations for a given use case, then execute the matching tool with schema-validated inputs
Automate a sequence of Bart tasks across a persistent session_id, reusing memory between steps
Run large-scale Bart bulk operations via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Validate and activate a Bart connection programmatically before executing downstream automation
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS for complex input construction

FAQ

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 Rube MCP endpoints.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS before each run or new workflow to get the latest schemas. If a schema changed mid-workflow, regenerate inputs using the updated schema and restart or continue with a new session_id.