fixer-io-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/fixer-io-automation --openclawFixer IO Automation via Rube MCP
Automate Fixer IO operations through Composio's Fixer IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/fixer_io
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Fixer IO connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfixer_io - 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 toolkitfixer_io - 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 IO 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 IO task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["fixer_io"]
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 Fixer IO-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit fixer_io |
| 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-io-automation/SKILL.mdView on GitHub Overview
This skill automates Fixer IO operations through Composio's Fixer IO toolkit via Rube MCP. It requires an active Rube MCP connection and a Fixer IO connection, and it mandates always searching for current tool schemas to ensure accurate inputs and slugs. By combining discovery, connection validation, and execution, you can streamline repetitive Fixer IO workflows with up-to-date schemas.
How This Skill Works
First, discover available Fixer IO tools and their input schemas using RUBE_SEARCH_TOOLS. Then verify the Fixer IO connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and memory, and reuse a session ID where appropriate.
When to Use It
- Automate repetitive Fixer IO tasks and always use the latest tool schemas.
- Integrate Fixer IO operations into a larger workflow while reusing an existing session.
- Set up a new Fixer IO task by discovering current tools and schemas before execution.
- Perform bulk Fixer IO operations using RUBE_REMOTE_WORKBENCH and run_composio_tool.
- When tool schemas change or new tools appear, re-discover tools before running.
Quick Start
- Step 1: Run RUBE_SEARCH_TOOLS to discover available Fixer IO tools and their input schemas.
- Step 2: Verify the Fixer IO connection is ACTIVE via RUBE_MANAGE_CONNECTIONS for toolkit fixer_io.
- Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the discovered session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Do not hardcode tool slugs; rely on the discovered tool slugs and input schemas.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
- Reuse session IDs within a workflow and generate new ones for new runs.
Example Use Cases
- Daily Fixer IO sync: discover tools, verify connection, and execute the appropriate tool with the latest schema.
- Onboarding a new Fixer IO task: discover tools, connect, then execute using the discovered slug and args.
- Bulk updates: use RUBE_REMOTE_WORKBENCH to run several Fixer IO tools in one session with memory blocks.
- Workflow consolidation: reuse an existing session ID when chaining multiple Fixer IO steps.
- Schema changes: re-run RUBE_SEARCH_TOOLS to pull updated schemas before executing any tool.
