How do I start using honeyhive-automation?

Add the Rube MCP endpoint, verify tool availability with RUBE_SEARCH_TOOLS, then manage the Honeyhive connection with RUBE_MANAGE_CONNECTIONS.

Is an ACTIVE connection required to run tools?

Yes. Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.

How do I keep tool schemas up to date?

Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas before running workflows.

honeyhive-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Honeyhive Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/honeyhive

Prerequisites

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

Step 2: Check Connection

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

Overview

Honeyhive automation via Rube MCP connects Honeyhive toolkit through Composio to perform operations. It requires RUBE_SEARCH_TOOLS and an active Honeyhive connection; always fetch tool schemas first.

How This Skill Works

Set up Rube MCP via the endpoint, verify tool availability with RUBE_SEARCH_TOOLS, then establish a Honeyhive connection using RUBE_MANAGE_CONNECTIONS. Discover tools, ensure the connection is ACTIVE, and execute tool slugs with RUBE_MULTI_EXECUTE_TOOL, including memory and the session id for workflow continuity.

When to Use It

When you need to automate a specific Honeyhive task after discovering the relevant tool slug and input schema.
When preparing to verify and establish an ACTIVE Honeyhive connection before running workflows.
When you want to fetch current tool schemas to avoid hardcoding slugs or arguments.
When reusing a session ID to improve workflow efficiency across steps.
When performing bulk tool executions or chained operations via RUBE_REMOTE_WORKBENCH or multiple multi-tool runs.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS returns results.
Step 2: Use RUBE_MANAGE_CONNECTIONS to connect to the honeyhive toolkit; complete auth if prompted.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the provided schema and session.

Best Practices

Always call RUBE_SEARCH_TOOLS before execution to get up-to-date tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from search results for arguments.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and avoid creating new ones mid-run.

Example Use Cases

Discover a Honeyhive tool slug for inventory sync and execute it with the returned input schema.
Establish a Honeyhive connection, then run a scheduled data sync tool across a daily workflow.
Batch run multiple Honeyhive operations by querying tools with RUBE_SEARCH_TOOLS and executing them via RUBE_MULTI_EXECUTE_TOOL.
Validate tool schemas on the fly by fetching current schemas before running any workflow.
Recover from a failed run by reusing the existing session and reissuing the tool calls.

Frequently Asked Questions

Add this skill to your agents