Do I need API keys to use Enigma automation?

No. Add the MCP endpoint (https://rube.app/mcp) and follow the authentication flow only if prompted.

How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing and do not hardcode slugs or arguments; schemas can change.

What if the Enigma connection isn't ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to activate the enigma toolkit and follow the provided auth link; only run workflows when the status is ACTIVE.

enigma-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Enigma Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/enigma

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Enigma operations by leveraging Composio's Enigma toolkit through Rube MCP. It enforces always querying current tool schemas before execution to prevent stale tool slugs and arguments.

How This Skill Works

Connect to Rube MCP and confirm an ACTIVE Enigma toolkit connection. Start with RUBE_SEARCH_TOOLS to pull current tool slugs and input schemas, then verify the connection with RUBE_MANAGE_CONNECTIONS. Finally, execute discovered tools using RUBE_MULTI_EXECUTE_TOOL with the required memory and session_id, ensuring schema compliance.

When to Use It

When you need up-to-date Enigma tool schemas before running any workflow
When you must establish and verify an active Enigma connection prior to automation
When discovering, selecting, and executing a specific Enigma tool slug
When orchestrating multi-tool Enigma workflows in a single session with memory
When troubleshooting tool lists for pagination and avoiding hardcoded slugs

Quick Start

Step 1: Add RUBE MCP server at https://rube.app/mcp to your client configuration
Step 2: Run RUBE_SEARCH_TOOLS with use_case like 'Enigma operations' to discover current tools
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["enigma"] and then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a valid session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before starting a workflow to fetch current schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution
Use exact field names and types from the search results; avoid hardcoding
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

Automate an Enigma data pull by discovering the tool slug with RUBE_SEARCH_TOOLS and executing it via RUBE_MULTI_EXECUTE_TOOL in a single session
Reconnect to Enigma after a disconnect, then resume a queued workflow using the existing session_id
Chain multiple Enigma tools in one session, reusing memory and validating schemas at each step
List Enigma tools when results paginate, then select and execute the appropriate slug without hardcoding
Bulk-run several Enigma tasks across tools in a single job using RUBE_MULTI_EXECUTE_TOOL with memory and session management

Frequently Asked Questions

Add this skill to your agents