What is etermin-automation?

A workflow that automates Etermin tasks through Composio's Etermin toolkit using Rube MCP, prioritizing current tool schemas and validated connections.

Do I need API keys for Rube MCP?

No API keys are required. Add the MCP endpoint (for example, https://rube.app/mcp) in your client configuration.

What if tool schemas change?

RUBE_SEARCH_TOOLS must be re-run to fetch the latest tool slugs and input schemas before execution.

etermin-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Etermin Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/etermin

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Etermin operations through Composio's Etermin toolkit via Rube MCP. Always fetch current tool schemas before running workflows to adapt to updates and ensure correct tool usage.

How This Skill Works

First, connect to Rube MCP and verify RUBE_SEARCH_TOOLS responds. Next, discover available Etermin tools with the returned schemas and confirm the toolkit is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute the selected tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and a memory payload.

When to Use It

When you need to automate recurring Etermin tasks through Composio.
When tool schemas may change and you must fetch the latest tool slugs and arguments.
When establishing or validating an ACTIVE Rube MCP connection for etermin.
When reusing session IDs within a long-running or multi-step workflow.
When executing multiple Etermin tools in a single workflow or bulk operation.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config; no API keys needed.
Step 2: Ensure RUBE_SEARCH_TOOLS responds and fetch Etermin tool schemas.
Step 3: Manage the etermin connection to ACTIVE and execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas.
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new IDs for new runs.

Example Use Cases

Automate a weekly Etermin report by discovering the latest tooling slugs and chaining RUBE_MULTI_EXECUTE_TOOL calls.
Update a workflow when tool schemas change by re-running RUBE_SEARCH_TOOLS and adjusting arguments.
Establish a new etermin connection, verify it is ACTIVE, then execute a sequence of tools in a single run.
Reuse a session ID to maintain context while performing related Etermin tasks in one workflow.
Coordinate bulk Etermin operations via RUBE_REMOTE_WORKBENCH, using run_composio_tool for efficiency.

Frequently Asked Questions

Add this skill to your agents