How do I start using dreamstudio-automation?

Add the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS responds, manage the dreamstudio connection with RUBE_MANAGE_CONNECTIONS, and ensure ACTIVE before executing tools.

Why must I search tools first every time?

Tool schemas change regularly; hardcoding slugs or arguments can break workflows. Always fetch current schemas with RUBE_SEARCH_TOOLS.

How are tools executed once connected?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, supply exact schema-compliant arguments, include memory, and reference a session_id from discovery or a prior step.

dreamstudio-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dreamstudio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dreamstudio

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["dreamstudio"]
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 Dreamstudio-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `dreamstudio`
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/dreamstudio-automation/SKILL.md

View on GitHub

Overview

Automate Dreamstudio operations using Composio's Dreamstudio toolkit through Rube MCP. It emphasizes discovering current tool schemas first, managing connections, and executing tools with proper memory and session handling.

How This Skill Works

First, call RUBE_SEARCH_TOOLS to fetch up-to-date Dreamstudio tool schemas. Then use RUBE_MANAGE_CONNECTIONS to activate the dreamstudio toolkit. Finally, run tools via RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug, proper arguments, memory, and a session_id reference.

When to Use It

You need to orchestrate Dreamstudio tasks while ensuring you have the latest tool schemas
You must establish and verify an ACTIVE Dreamstudio connection before workflows
You want to reuse a session_id across related Dreamstudio workflows
You want to avoid hardcoding tool slugs by always discovering tools first
You plan to perform bulk operations or advanced workflows with RUBE_REMOTE_WORKBENCH

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 available
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["dreamstudio"] and ensure the session becomes ACTIVE before running workflows

Best Practices

Always call RUBE_SEARCH_TOOLS before any execution to get current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to running tools
Use exact field names and types from the search results; do not hardcode
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs for related workflows and handle pagination tokens when present

Example Use Cases

Discover Dreamstudio tools for a task, then execute the returned tool_slug with the required arguments
Establish a dreamstudio connection, confirm ACTIVE, then run a tool within a specific session
Fetch all available Dreamstudio tool schemas with RUBE_GET_TOOL_SCHEMAS and plan execution
Bulk run multiple Dreamstudio tools using RUBE_REMOTE_WORKBENCH and run_composio_tool()
Iterate tool discovery, execution, and memory sharing across chained Dreamstudio workflows

Frequently Asked Questions

Add this skill to your agents