Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Claid AI Rube MCP Automation Guide

agent tool_use skill risk: medium

Claid AI Rube MCP Automation Guide

The prompt provides instructions for automating Claid AI operations through Composio's Claid AI toolkit via Rube MCP, including prerequisites, setup, tool discovery with RUBE_SEARC…

  • External action: high

SKILL 1 file

SKILL.md
---
name: claid-ai-automation
description: "Automate Claid AI tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Claid AI Automation via Rube MCP

Automate Claid AI operations through Composio's Claid AI toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["claid_ai"]
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 Claid AI-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `claid_ai` |
| 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)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active claid_ai connection via RUBE_MANAGE_CONNECTIONS

OPTIONAL CONTEXT

  • existing session_id

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • include memory parameter
  • reuse session ids

FAILURE MODES

  • Hardcoding tool slugs or arguments without first calling RUBE_SEARCH_TOOLS
  • Executing tools before confirming ACTIVE connection status
  • Using incorrect field names or types from search results
  • Omitting the memory parameter from RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse session IDs within a workflow
  • Ignoring pagination tokens in responses

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Claid AI connection via RUBE_MANAGE_CONNECTIONS with toolkit claid_ai
  • Current tool schemas from RUBE_SEARCH_TOOLS
Missing context
  • Specific Claid AI task description to insert into use_case
  • Existing session_id value when reusing sessions

QUALITY

OVERALL
0.80
CLARITY
0.88
SPECIFICITY
0.82
REUSABILITY
0.72
COMPLETENESS
0.78

IMPROVEMENT SUGGESTIONS

  • Replace inline code blocks with explicit {{placeholder}} tokens for task description, session_id, and tool arguments to improve templating.
  • Add a minimal end-to-end example showing one complete successful run with sample values.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT