Do I always need to call RUBE_SEARCH_TOOLS first?

Yes. It fetches current tool schemas so you have up to date slugs and arguments.

How do I ensure the Hyperbrowser connection is ready?

Use RUBE_MANAGE_CONNECTIONS with the hyperbrowser toolkit and confirm the status is ACTIVE before executing tools.

What about memory and session handling?

Always include memory in RUBE_MULTI_EXECUTE_TOOL calls and reuse a session ID within a workflow, generating a new one for new workflows.

hyperbrowser-automation

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

Files (1)

SKILL.md

2.9 KB

Hyperbrowser Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hyperbrowser

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["hyperbrowser"]
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 Hyperbrowser-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `hyperbrowser`
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/hyperbrowser-automation/SKILL.md

View on GitHub

Overview

Automate Hyperbrowser operations through Composio's Hyperbrowser toolkit via Rube MCP. It emphasizes discovering current tool schemas before execution to stay in sync with updates.

How This Skill Works

Use RUBE_SEARCH_TOOLS to discover available tools for Hyperbrowser use cases, then verify the Hyperbrowser connection with RUBE_MANAGE_CONNECTIONS. When ready, run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and properly formatted arguments, including memory, and pairing with a session_id.

When to Use It

When you must use up to date Hyperbrowser tool schemas obtained via RUBE_SEARCH_TOOLS
When automating a workflow that uses multiple Hyperbrowser tools in sequence
When establishing a new Hyperbrowser connection via Rube MCP and validating ACTIVE status
When handling large results or paginated responses from tools
When reusing a session ID within a single automation workflow for statefulness

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS responds
Step 2: Run RUBE_SEARCH_TOOLS with a Hyperbrowser use case to discover tools and schemas
Step 3: Run RUBE_MANAGE_CONNECTIONS with the hyperbrowser toolkit and then execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any tool execution
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Discover available tools with the Hyperbrowser use case and execute a discovered tool slug
Set up the Hyperbrowser connection and validate ACTIVE before starting automation
Execute a sequence of tools to fetch and process Hyperbrowser data while reusing a session ID
Handle pagination by continuing to fetch results until completion
Run bulk operations via the remote bench for multiple Hyperbrowser tasks

Frequently Asked Questions

Add this skill to your agents