home / skills / composiohq / awesome-claude-skills / brandfetch-automation

brandfetch-automation skill

safe

/brandfetch-automation

This skill automates Brandfetch tasks via Composio's MCP, always discovering current tool schemas before execution to ensure up-to-date workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill brandfetch-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: brandfetch-automation
description: "Automate Brandfetch tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Brandfetch Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/brandfetch](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `brandfetch`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Brandfetch tasks by orchestrating Composio's Brandfetch toolkit through Rube MCP. It guides tool discovery, connection checks, and schema-compliant execution so workflows run reliably and repeatably. The workflow enforces searching tools first and reusing session context to avoid schema drift and auth issues.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It verifies an active Brandfetch connection via RUBE_MANAGE_CONNECTIONS and then runs operations using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH with schema-aligned arguments. Responses are polled for pagination and memory is preserved or passed as an empty object when required.

When to use it

When you need to fetch or manage brand data (logos, colors, metadata) via Brandfetch programmatically.
When integrating Brandfetch actions into automated Claude or agent workflows that use Rube MCP.
Before running any Brandfetch operation to avoid failures due to schema changes or stale connections.
When performing bulk operations or remote workbench runs across many brands or accounts.
When you need repeatable, audit-friendly automation with session reuse and pagination handling.

Best practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and exact input schemas; never hardcode fields.
Confirm RUBE_MANAGE_CONNECTIONS shows toolkit 'brandfetch' as ACTIVE before executing tools.
Include a memory parameter (even if {}) in RUBE_MULTI_EXECUTE_TOOL calls to satisfy execution requirements.
Reuse the same session_id within a workflow; generate new session_ids for distinct workflows.
Handle pagination tokens in responses and iterate until results are complete.

Example use cases

Look up brand assets for a list of companies, handling pagination and batching via RUBE_MULTI_EXECUTE_TOOL.
Automate a sync pipeline that updates a CMS with brand logos and color palettes using the remote workbench.
Validate connection health and auto-initiate an auth flow if Brandfetch connection is not ACTIVE.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to build a dynamic UI that maps to the latest inputs.
Perform bulk enrichment of company records by running composio Brandfetch tools in parallel sessions.

FAQ

Do I need API keys to use Rube MCP with this skill?

No API keys are required for the MCP endpoint; add https://rube.app/mcp to your client configuration and use the provided Rube MCP actions.

What if a tool schema changes mid-workflow?

Always run RUBE_SEARCH_TOOLS at the start of each workflow and validate schema fields before executing; regenerate or adjust arguments if schemas differ.