home / skills / composiohq / awesome-claude-skills / maintainx-automation

maintainx-automation skill

safe

/maintainx-automation

This skill automates Maintainx tasks using Rube MCP and Composio, always discovering current tool schemas before execution for reliable workflows.

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

# Maintainx Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["maintainx"]
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 Maintainx-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `maintainx` |
| 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 Maintainx tasks by orchestrating Composio’s Maintainx toolkit through Rube MCP. It focuses on safe, schema-driven execution: always discover tools, verify connections, and call multi-execute with proper memory and session handling. The skill is designed for reliable, repeatable workflows that integrate Maintainx operations into automated pipelines.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. It then validates the Maintainx connection with RUBE_MANAGE_CONNECTIONS and uses RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk runs) to perform actions with schema-compliant arguments. Sessions and memory objects are included in every execute call to preserve state and support pagination and retries.

When to use it

Automating routine Maintainx tasks like work order creation, updates, and status checks
Building a workflow that integrates Maintainx into broader automation or ticketing systems
Running bulk or scheduled maintenance operations across assets
Prototyping agent-driven maintenance assistants that must respect live tool schemas
When you need reliable session and state handling for multi-step Maintainx operations

Best practices

Always call RUBE_SEARCH_TOOLS first—do not hardcode tool slugs or argument shapes
Verify toolkit connection status via RUBE_MANAGE_CONNECTIONS and complete any auth flow until status is ACTIVE
Use exact field names and types returned by tool discovery; schema compliance prevents runtime errors
Include a memory object (even an empty {}) in RUBE_MULTI_EXECUTE_TOOL calls to ensure correct execution semantics
Reuse session IDs across a workflow; generate a fresh session for new, unrelated workflows
Handle pagination tokens returned by search or execute responses and iterate until complete

Example use cases

Create and assign a batch of preventative work orders using discovered Maintainx tool schemas
Query asset histories and generate summarized reports by combining multiple Composio tools
Automate status updates and notifications when maintenance tasks transition states
Build an agent that inspects available Maintainx operations then runs chosen tools with validated arguments
Run a remote workbench job to perform bulk edits across many assets or tasks

FAQ

Do I need API keys to use Rube MCP?

No API keys are required—add https://rube.app/mcp as an MCP server in your client configuration to connect.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS before executing new steps. If schemas change mid-run, adjust arguments to match the latest schema and restart affected steps.