remove-bg-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/remove-bg-automation --openclawRemove 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
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Remove Bg connection via
RUBE_MANAGE_CONNECTIONSwith toolkitremove_bg - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitremove_bg - 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: "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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/remove-bg-automation/SKILL.mdView on GitHub Overview
This skill automates background-removal tasks using Composio's Remove Bg toolkit through Rube MCP. It emphasizes discovering current tool schemas before each run, verifying an ACTIVE connection, and executing tools via the standard RUBE_MULTI_EXECUTE_TOOL flow.
How This Skill Works
Technically, you first query RUBE_SEARCH_TOOLS to fetch available Remove Bg tools and their input schemas. Next, you establish an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the remove_bg toolkit, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the provided memory payload and session_id.
When to Use It
- Automate batch Remove Bg tasks across catalogs or campaigns.
- When tool schemas change often and you must fetch current schemas before running.
- To validate that the Rube MCP connection for remove_bg is ACTIVE before execution.
- Integrate Remove Bg into a larger automation pipeline using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH.
- Reuse session IDs within a workflow to improve consistency and tracking.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with use_case: "Remove Bg operations" to discover available tools and schemas.
- Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ["remove_bg"] and check session_id results until status is ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {}, and the active session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to retrieve current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from search results for tool arguments.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens when present.
Example Use Cases
- Batch remove backgrounds for an e-commerce product catalog using discovered Remove Bg tools.
- Integrate Remove Bg into a marketing asset pipeline by validating the ACTIVE connection first.
- Perform bulk background removals for gallery thumbnails via RUBE_REMOTE_WORKBENCH run_composio_tool.
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and then execute a selected tool.
- Troubleshoot updates by re-discovering tools after schema changes and re-running the workflow.
