Do I need an API key to use Shotstack automation with Rube MCP?

No API keys are required. You configure the MCP server endpoint and establish a connection to Shotstack through the toolkit; authentication is handled via the Rube MCP workflow.

How do I ensure tool schemas are up to date before running a workflow?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas; do not hardcode slugs or arguments.

What if the connection shows not ACTIVE?

Call the auth flow from the returned link to complete setup, then re-check with RUBE_MANAGE_CONNECTIONS until the status is ACTIVE before executing tools.

shotstack-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Shotstack Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/shotstack

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Shotstack operations via Composio's Shotstack toolkit using Rube MCP. The workflow relies on discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE connection, and executing discovered tools to ensure resilient automation.

How This Skill Works

You start by discovering available Shotstack tools with RUBE_SEARCH_TOOLS, then verify or establish a connection via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the exact slugs and schema-compliant arguments. Always include memory in execution calls and reuse session IDs to maintain workflow continuity.

When to Use It

You need to automate Shotstack tasks and keep tool schemas up to date by always querying current tool schemas first.
You must verify that RUBE_SEARCH_TOOLS returns valid tool slugs and input schemas before running any workflow.
You want to connect to Shotstack via Rube MCP and ensure the connection status is ACTIVE prior to execution.
You're performing bulk or multi-tool operations using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH workflows.
You need to adapt to schema changes without hardcoding tool slugs or arguments.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed).
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are current.
Step 3: Use RUBE_MANAGE_CONNECTIONS to connect the 'shotstack' toolkit, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and schema-compliant arguments in a single session.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and handle pagination tokens when fetching tool lists.

Example Use Cases

Discover a Shotstack render tool with RUBE_SEARCH_TOOLS, connect with RUBE_MANAGE_CONNECTIONS, then execute the tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments.
Run a batch of render tasks by discovering multiple tool slugs, validating ACTIVE connections, and issuing multiple tool executions in a single session.
Regularly refresh tool schemas by re-running RUBE_SEARCH_TOOLS before updating any automation workflow that uses Shotstack tools.
Bulk process a queue of clips by using RUBE_REMOTE_WORKBENCH with run_composio_tool() after tool discovery.
If a workflow fails due to schema changes, re-discover tools, update arguments accordingly, and retry with the same session.

Frequently Asked Questions

Add this skill to your agents