What setup is required to use ragic-automation?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Ragic connection via RUBE_MANAGE_CONNECTIONS with the ragic toolkit; always search tools first.

Do I need to hardcode tool slugs?

No. Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before execution.

How do I run a tool and what data do I pass?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and arguments from the tool's input schema, include memory, and pass a session_id.

ragic-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Ragic Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ragic

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Ragic operations through Composio's Ragic toolkit using Rube MCP. It emphasizes discovering current tool schemas before execution to adapt to changes and requires an active Ragic connection and RUBE_SEARCH_TOOLS prior to running workflows.

How This Skill Works

You first discover available tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Next, you verify that RUGE_MANAGE_CONNECTIONS shows an ACTIVE Ragic connection for the ragic toolkit. Finally, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, providing the discovered arguments and a memory payload within a session.

When to Use It

When you need a Ragic operation using the latest tool schemas.
When automating repetitive Ragic tasks across multiple forms.
When establishing or validating a Ragic connection via Rube MCP before running a workflow.
When executing discovered tool slugs with a controlled session and proper memory payload.
When performing bulk or chained Ragic actions and handling pagination tokens.

Quick Start

Step 1: Verify Rube MCP is connected and call RUBE_SEARCH_TOOLS to fetch current Ragic tool schemas.
Step 2: Check/Set up the connection to the ragic toolkit via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE.
Step 3: Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs within a workflow and fetch pagination tokens until complete.

Example Use Cases

Discover a tool for creating a new Ragic record, then run it with the required fields.
Run a bulk update across several Ragic forms by iterating tool slugs in a single session.
Validate connectivity first, then enumerate available tools before execution.
Use RUBE_MULTI_EXECUTE_TOOL with a discovered slug to execute a specific operation.
Fetch full tool schemas via RUBE_GET_TOOL_SCHEMAS and adapt your automation.

Frequently Asked Questions

Add this skill to your agents