What is hyperise-automation?

A skill to automate Hyperise tasks via Rube MCP (Composio), with schema-first tool discovery to adapt to changing tool definitions.

What are the prerequisites?

Rube MCP connected (RUBE_SEARCH_TOOLS available); Active Hyperise connection via RUBE_MANAGE_CONNECTIONS with toolkit hyperise; Always search tools first to get current schemas.

How do I run a workflow end-to-end?

Connect MCP, discover tools with RUBE_SEARCH_TOOLS, verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS, then execute tools with RUBE_MULTI_EXECUTE_TOOL using the correct memory and session_id.

hyperise-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Hyperise Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hyperise

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Hyperise operations through Composio's Rube MCP toolkit. It prioritizes discovering current tool schemas with RUBE_SEARCH_TOOLS and validating an ACTIVE Hyperise connection before running workflows. This enables repeatable, schema-compliant Hyperise tasks.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas for Hyperise tasks, then uses RUBE_MANAGE_CONNECTIONS to ensure the hyperise toolkit is connected. Once a connection is ACTIVE, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with the needed arguments and a memory object, enabling session-aware automation.

When to Use It

Automating repetitive Hyperise tasks across campaigns by discovering tooling dynamically with RUBE_SEARCH_TOOLS.
When tool schemas change, fetch the latest slugs and inputs before execution.
Before batch-running workflows, verify an ACTIVE Hyperise connection via RUBE_MANAGE_CONNECTIONS.
Executing multiple Hyperise operations in a single session using RUBE_MULTI_EXECUTE_TOOL with memory parameter.
Integrating Hyperise tasks into larger Composio workflows while reusing session IDs for efficiency.

Quick Start

Step 1: Get Rube MCP working by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
Step 2: Establish a Hyperise connection with RUBE_MANAGE_CONNECTIONS (toolkit: hyperise) and confirm ACTIVE status.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, select a tool_slug, then execute via RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Follow the exact field names and types from the search results for schema compliance.
Include memory 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 Hyperise image personalization sequence across multiple campaigns by discovering tools with RUBE_SEARCH_TOOLS and executing them via RUBE_MULTI_EXECUTE_TOOL per session.
Sync updated Hyperise templates across several campaigns after refreshing tool schemas with RUBE_SEARCH_TOOLS.
Set up and verify an ACTIVE Hyperise connection before batch-running a weekly Hyperise workload using RUBE_MANAGE_CONNECTIONS.
Run a batch of Hyperise tasks in a single session, reusing the session_id for efficiency and consistency.
Perform bulk Hyperise operations on a large dataset through RUBE_REMOTE_WORKBENCH using run_composio_tool.

Frequently Asked Questions

Add this skill to your agents