What is hypeauditor-automation?

A workflow pattern to automate hypeauditor tasks using Rube MCP, always discovering current tool schemas first.

No API keys are required; connect via the Rube MCP endpoint and use the hypeauditor toolkit.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing tools to fetch the latest slugs and input fields.

hypeauditor-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Hypeauditor Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hypeauditor

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Hypeauditor operations through Composio's Hypeauditor toolkit via Rube MCP. This skill emphasizes discovering current tool schemas before execution and requires a connected Rube MCP, an active hypeauditor connection, and following the setup steps for reliable automation. It helps teams reduce manual steps and stay aligned with changing tool schemas.

How This Skill Works

Begin by discovering available Hypeauditor tools with RUBE_SEARCH_TOOLS to fetch slugs and input schemas. Next, verify the hypeauditor connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, including a memory object. Workflows reuse an existing session_id when possible and must use exact field names and types from the discovered schema.

When to Use It

Setting up a new hypeauditor workflow by discovering tools, connecting, and running a task end-to-end.
When tool schemas may have changed, so you fetch current slugs and fields with RUBE_SEARCH_TOOLS first.
Before executing any tool, ensure the hypeauditor connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
Running a sequence of tools in one session with RUBE_MULTI_EXECUTE_TOOL and memory parameter.
Performing bulk or remote tasks with RUBE_REMOTE_WORKBENCH to orchestrate multiple tools.

Quick Start

Step 1: Add the Rube MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Connect to hypeauditor with RUBE_MANAGE_CONNECTIONS toolkits: ["hypeauditor"] and ensure ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and run a tool with RUBE_MULTI_EXECUTE_TOOL using memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first; tool schemas can change.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution.
Use exact field names and types from the discovered schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new tasks.

Example Use Cases

Automate a daily hypeauditor domain report by discovering tools, establishing a connection, and running a single tool.
Bundle multiple hypeauditor tasks into a single workflow to compare campaigns and consolidate results.
Re-authenticate hypeauditor connection after credential rotation and resume automated tasks.
Execute bulk reports using RUBE_REMOTE_WORKBENCH to run multiple tools in a batch.
Iterate on tool discovery while handling pagination to fetch all tool schemas.

Frequently Asked Questions

Add this skill to your agents