What is brandfetch-automation?

It automates Brandfetch tasks using Composio's Brandfetch toolkit via the Rube MCP, enabling tool discovery, connection management, and automated execution.

What are the prerequisites?

Rube MCP must be connected, RUBE_SEARCH_TOOLS must respond to fetch current schemas, and the Brandfetch connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS.

How do you handle tool schema changes?

Always call RUBE_SEARCH_TOOLS before execution to obtain the latest tool slugs and input schemas; avoid hardcoding; include memory and manage pagination as needed.

brandfetch-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Brandfetch Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/brandfetch

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Brandfetch operations through Composio's Brandfetch toolkit via Rube MCP. Always start by searching tools to get current schemas and available tool slugs, ensuring you work with up-to-date definitions.

How This Skill Works

Use RUBE_SEARCH_TOOLS to discover available Brandfetch tools and their input schemas. Then verify an ACTIVE Brandfetch connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id, while respecting any pagination in responses.

When to Use It

Automate retrieval of brand assets (colors, logos) for a product page or marketing asset library.
Batch-run multiple Brandfetch tasks in a single workflow and reuse a session across steps.
Preflight automation by ensuring current tool schemas before executing Brandfetch tasks.
Validate and maintain an ACTIVE Brandfetch connection before running workflows.
Batch process Brandfetch lookups across several domains with pagination handling.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify it’s reachable.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Brandfetch tool schemas and slugs.
Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkit 'brandfetch', then execute a tool with RUBE_MULTI_EXECUTE_TOOL using a valid session_id and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and slugs.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results; do not hardcode slugs.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and properly handle pagination tokens.

Example Use Cases

Auto-fetch color palettes and logos for a product page by orchestrating Brandfetch lookups discovered via RUBE_SEARCH_TOOLS.
Sync brand assets across a marketing campaign by batching multiple Brandfetch tool executions in one session.
Preflight automation: check ACTIVE Brandfetch connection before executing any lookups.
Retrieve complete brand asset lists by following pagination tokens across multiple domain lookups.
Bulk update asset metadata across domains using RUBE_MULTI_EXECUTE_TOOL with memory and session management.

Frequently Asked Questions

Add this skill to your agents