repairshopr-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/repairshopr-automation --openclawRepairshopr Automation via Rube MCP
Automate Repairshopr operations through Composio's Repairshopr toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/repairshopr
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Repairshopr connection via
RUBE_MANAGE_CONNECTIONSwith toolkitrepairshopr - 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 toolkitrepairshopr - 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: "Repairshopr 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 Repairshopr task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["repairshopr"]
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 Repairshopr-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit repairshopr |
| 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/repairshopr-automation/SKILL.mdView on GitHub Overview
Repairshopr-automation lets you run Repairshopr operations through Composio's Rube MCP toolkit. It relies on discovering current tool schemas before execution, so workflows stay resilient to changes. This minimizes manual steps and keeps automation aligned with the latest Repairshopr capabilities.
How This Skill Works
It discovers available tools with RUBE_SEARCH_TOOLS to fetch the latest Repairshopr tool schemas. It then ensures an ACTIVE connection via RUBE_MANAGE_CONNECTIONS to the repairshopr toolkit, and executes a chosen tool using RUBE_MULTI_EXECUTE_TOOL with exact arguments and a memory payload, tracked by a session_id. Always verify the connection is ACTIVE and supply memory in each call.
When to Use It
- You need to automate a Repairshopr operation and want the latest tool schemas fetched automatically.
- You must establish or verify an ACTIVE Repairshopr toolkit connection before running workflows.
- You have discovered a specific Repairshopr tool slug and want to execute it with exact, schema-compliant arguments.
- You’re building a multi-step workflow and want to reuse a session_id across steps for consistency.
- You want to review or refresh the entire tool set by fetching full schemas with RUBE_GET_TOOL_SCHEMAS to adapt scripts.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Run RUBE_SEARCH_TOOLS for Repairshopr to discover available tools and input schemas (use_case: 'Repairshopr operations').
- Step 3: Run RUBE_MANAGE_CONNECTIONS to connect to toolkit 'repairshopr', then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a memory payload and a session_id.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas before execution.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any tools.
- Use exact field names and types from the search results; do not hardcode slugs or args.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty ({})
- Reuse session IDs within a workflow and fetch new ones only for separate workflows; watch for pagination tokens.
Example Use Cases
- Discover tools for a Repairshopr task and execute a discovered tool with schema-compliant arguments.
- Connect to Repairshopr via RUBE_MANAGE_CONNECTIONS and run a multi-step workflow using a shared session.
- Batch multiple Repairshopr operations using RUBE_MULTI_EXECUTE_TOOL and memory payloads.
- Bulk operations across records using RUBE_REMOTE_WORKBENCH with run_composio_tool().
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS and adjust your automation to updated schemas.
