home / skills / composiohq / awesome-claude-skills / remove-bg-automation

remove-bg-automation skill

safe

/remove-bg-automation

This skill automates Remove Bg tasks via Composio's toolkit using Rube MCP, always discovering current tool schemas first.

npx playbooks add skill composiohq/awesome-claude-skills --skill remove-bg-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: remove-bg-automation
description: "Automate Remove Bg tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Remove Bg Automation via Rube MCP

Automate Remove Bg operations through Composio's Remove Bg toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/remove_bg](https://composio.dev/toolkits/remove_bg)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["remove_bg"]
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 Remove Bg-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `remove_bg` |
| 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 Remove Bg tasks through Composio's Remove Bg toolkit using Rube MCP. It orchestrates discovery, connection checks, and tool execution so you can remove backgrounds at scale while staying resilient to changing tool schemas. The skill enforces search-first and schema-compliant execution patterns to avoid runtime errors.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It then verifies or establishes an active connection via RUBE_MANAGE_CONNECTIONS for the remove_bg toolkit. Finally it runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always passing schema-compliant arguments, session IDs, and a memory object.

When to use it

Removing backgrounds from single or batches of images via Composio Remove Bg toolkit
Automating background removal within larger image-processing pipelines
Running bulk or remote workbench jobs that call composio remove_bg tools
When you need robust tool discovery to handle dynamic tool schemas
When building Claude-based agents that call external image toolkits

Best practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas
Verify connection status with RUBE_MANAGE_CONNECTIONS and complete any returned auth flow until ACTIVE
Use exact field names and data types from the tool schema; do not hardcode arguments
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs for a workflow and generate new ones for separate workflows
Handle pagination in search responses and follow schemaRef with RUBE_GET_TOOL_SCHEMAS when needed

Example use cases

Batch remove backgrounds from product photos for ecommerce, using discovered bulk tools and RUBE_REMOTE_WORKBENCH
Interactive agent flow that prompts a user for images, verifies remove_bg connection, and calls RUBE_MULTI_EXECUTE_TOOL
Scheduled pipeline that re-checks tool schemas before each run to avoid field mismatch errors
Developer tool that lists available remove_bg tool capabilities for QA and integration testing

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required for basic MCP connectivity.

What if a tool schema changed since my last run?

Always call RUBE_SEARCH_TOOLS at the start of the workflow. If schemas changed, adapt arguments to the returned schema fields or fetch full schemas via RUBE_GET_TOOL_SCHEMAS.