Do I need API keys for Bannerbear when using this skill?

No. Rube MCP handles connections via the bannerbear toolkit; add the MCP endpoint and use RUBE_MANAGE_CONNECTIONS to authorize the Bannerbear connection.

What if tool schemas change after I’ve started building a workflow?

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas; do not hardcode slugs or argument names.

How can I ensure a successful execution?

Ensure the connection status is ACTIVE before executing tools, include memory in RUBE_MULTI_EXECUTE_TOOL, and reuse an existing session ID or generate a new one for a fresh workflow.

bannerbear-automation

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

Files (1)

SKILL.md

2.9 KB

Bannerbear Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bannerbear

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Bannerbear operations through Composio's Bannerbear toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflows to stay in sync with updates and avoid hardcoding slugs.

How This Skill Works

The workflow discovers available Bannerbear tools using RUBE_SEARCH_TOOLS, then establishes and verifies a Bannerbear connection with RUBE_MANAGE_CONNECTIONS. Once the connection is ACTIVE, you execute discovered tools via RUBE_MULTI_EXECUTE_TOOL using the tool_slug and schema-compliant arguments, always including a memory payload.

When to Use It

When you need to automate Bannerbear tasks without manual setup each time
When tool schemas change, requiring the latest slugs and arguments
When performing bulk operations across multiple Bannerbear tools
When reusing a workflow session to maintain continuity
When validating connectivity before executing any tool

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server; no API keys needed
Step 2: Run RUBE_SEARCH_TOOLS with use_case: Bannerbear operations to get current slugs and schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["bannerbear"] and then RUBE_MULTI_EXECUTE_TOOL with the chosen slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
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 or generate new ones for new runs

Example Use Cases

Discover a set of Bannerbear tools for a campaign and run a template update automatically
Update multiple banners in a single workflow using the discovered tool slugs
Validate the Bannerbear connection and then execute a tool to generate a new banner
Fetch updated tool schemas and adapt a running automation without hardcoding slugs
Bulk-create banners across several templates using run_composio_tool via RUBE_MULTI_EXECUTE_TOOL

Frequently Asked Questions

Add this skill to your agents