How do I discover available Logo Dev tools?

Use RUBE_SEARCH_TOOLS with a use_case like "Logo Dev operations" to retrieve tool slugs, input schemas, and execution plans.

How do I ensure my connection is ready?

Call RUBE_MANAGE_CONNECTIONS with the logo_dev toolkit and confirm the session shows ACTIVE before any execution.

What common pitfalls should I avoid?

Do not hardcode slugs or arguments; always search first, ensure exact schema fields, include memory in calls, and consider pagination for large results.

logo-dev-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Logo Dev Automation via Rube MCP

Automate Logo Dev operations through Composio's Logo Dev toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/logo_dev

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Logo Dev operations through Composio's Logo Dev toolkit via Rube MCP. This workflow requires an active Rube MCP connection and a Logo Dev connection, and always starts by calling RUBE_SEARCH_TOOLS to fetch current tool schemas.

How This Skill Works

Discover available tools using RUBE_SEARCH_TOOLS to obtain slugs and schemas. Verify your connection status with RUBE_MANAGE_CONNECTIONS for the logo_dev toolkit. Finally, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper arguments, including a memory payload and a session_id for continuity.

When to Use It

When starting a new Logo Dev automation project and wiring up Rube MCP
When you need the latest tool schemas before running any workflow
When verifying that the Logo Dev connection is ACTIVE prior to execution
When executing a discovered tool with exact schema fields
When performing bulk operations or reusing sessions across steps

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["logo_dev"] and confirm ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL

Best Practices

Always run RUBE_SEARCH_TOOLS before any execution to fetch current tool schemas
Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the discovered tool schemas
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination if present

Example Use Cases

Discover Logo Dev tasks, connect to logo_dev, and execute a tool with proper arguments in a single workflow
Establish MCP connection, fetch current tool schemas, then run a Logo Dev operation using the latest slug
Validate ACTIVE status before execution and pass the correct memory payload for stateful tasks
Use RUBE_REMOTE_WORKBENCH for bulk operations with run_composio_tool across multiple tools
Query full schemas with RUBE_GET_TOOL_SCHEMAS to validate inputs before automation

Frequently Asked Questions

Add this skill to your agents