What is required to start?

You need a connected Rube MCP (RUBE_SEARCH_TOOLS endpoint reachable) and an active Appdrag connection via the appdrag toolkit. Then call RUBE_SEARCH_TOOLS to fetch current tool schemas.

Do I always have to search for tools before running a task?

Yes. Tool schemas can change; always call RUBE_SEARCH_TOOLS to get valid slugs and input schemas before RUBE_MANAGE_CONNECTIONS or RUBE_MULTI_EXECUTE_TOOL.

What data should I pass in memory when executing a tool?

Pass a memory object in RUBE_MULTI_EXECUTE_TOOL even if empty ({}); include relevant state only if your workflow requires it. Ensure the memory structure matches the tool's expectations.

appdrag-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Appdrag Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/appdrag

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Appdrag operations through Composio's Rube MCP toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas before executing workflows. Prerequisites include an active Rube MCP connection and an Appdrag toolkit connection.

How This Skill Works

You first discover available Appdrag tools using RUBE_SEARCH_TOOLS, then validate the connection via RUBE_MANAGE_CONNECTIONS, and finally run tools with RUBE_MULTI_EXECUTE_TOOL while passing a memory object and a session_id. Reuse session IDs within a workflow and ensure the connection remains ACTIVE before execution.

When to Use It

Automating routine Appdrag tasks such as batch updates, imports, or exports.
Before executing any Appdrag tool, to refresh and fetch current tool schemas.
When you need to confirm an active connection prior to tool execution.
Executing multiple Appdrag tools in a single workflow (bulk operations).
Troubleshooting: validate schema compliance and session management in automations.

Quick Start

Step 1: Add the Rube MCP endpoint https://rube.app/mcp to your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_SEARCH_TOOLS with your Appdrag use case to discover available tool slugs and input schemas.
Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, include memory: {} and session_id: "your_session_id"; ensure the session is ACTIVE.

Best Practices

Always call RUBE_SEARCH_TOOLS first to refresh tool schemas.
Verify the RUBE_MANAGE_CONNECTIONS status shows ACTIVE before running tools.
Use exact field names and types from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Automate a monthly Appdrag product sync by discovering the relevant tool and executing with a scripted workflow.
Bulk update Appdrag records based on external data sources using discovered tool slugs.
Run a deployment task across multiple Appdrag tools within a single session.
Validate tool schemas before performing a complex Appdrag operation to prevent errors.
Paginate tool discovery results and continue executing workflows until all tasks are covered.

Frequently Asked Questions

Add this skill to your agents