How do I start using fixer-automation?

Add the MCP endpoint, verify RUBE_SEARCH_TOOLS responds, then manage the Fixer connection and verify it is ACTIVE before running tools.

What if the connection is not ACTIVE?

Follow the returned authentication link to complete setup, then re-check the status until ACTIVE.

Can I hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas to avoid failures.

fixer-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Fixer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fixer

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Fixer operations via Composio's Fixer toolkit through Rube MCP. It emphasizes discovering current tool schemas before running workflows, ensuring an ACTIVE Fixer connection, and executing tools with schema-compliant arguments.

How This Skill Works

Begin with RUBE_SEARCH_TOOLS to fetch available Fixer tools and their input schemas. Then verify the connection via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally execute tools using RUBE_MULTI_EXECUTE_TOOL, including a memory payload, to run the chosen fixer workflow with up-to-date schemas.

When to Use It

When you need to automate repetitive Fixer tasks and reduce manual steps
When tool schemas have changed and you must fetch current slugs and arguments
When verifying that the Fixer connection is ACTIVE before running workflows
When executing multiple tools in a single workflow using a shared session
When performing bulk or remote operations with run_composio_tool() or RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'fixer' and ensure the connection is ACTIVE
Step 3: Run a discovered tool using RUBE_MULTI_EXECUTE_TOOL with memory: {} and the correct tool slug

Best Practices

Always call RUBE_SEARCH_TOOLS before executing workflows to obtain current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool execution
Use exact field names and types from the search results; do not hardcode slugs or args
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow where appropriate; generate new IDs for new workflows

Example Use Cases

Automate a Fixer data cleanup by discovering the relevant tool, confirming ACTIVE connection, and executing with the required arguments
After a toolkit update, re-discover tools with RUBE_SEARCH_TOOLS and then run the updated fixer task using the new slug and schema
Orchestrate a multi-tool workflow: search tools, verify connection, then execute TOOL_SLUG_FROM_SEARCH with memory
Perform bulk changes via RUBE_REMOTE_WORKBENCH using run_composio_tool() to apply fixes across many records
Fetch the latest tool schemas with RUBE_GET_TOOL_SCHEMAS and then execute compatible tools

Frequently Asked Questions

Add this skill to your agents