What is hotspotsystem-automation used for?

It automates Hotspotsystem tasks using the Composio Hotspotsystem toolkit via Rube MCP, ensuring tool schemas are current before each workflow.

What prerequisites do I need?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, and an active Hotspotsystem connection via RUBE_MANAGE_CONNECTIONS using the hotspotsystem toolkit.

How do I ensure tools won’t break when schemas change?

Always perform RUBE_SEARCH_TOOLS first to obtain up-to-date tool slugs and input schemas, and avoid hardcoding slugs or field names; verify ACTIVE connections before execution.

hotspotsystem-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Hotspotsystem Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hotspotsystem

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automates Hotspotsystem operations through Composio's Hotspotsystem toolkit via Rube MCP. Always search for current tool schemas before running workflows to adapt to changes.

How This Skill Works

Connect to Rube MCP and fetch the latest tool slugs and input schemas with RUBE_SEARCH_TOOLS. Then establish an active Hotspotsystem connection via RUBE_MANAGE_CONNECTIONS with the hotspotsystem toolkit and execute discovered tools using RUBE_MULTI_EXECUTE_TOOL, providing exact schema fields and a memory object. This workflow relies on current schemas and ACTIVE connections before execution.

When to Use It

Setting up a new automated Hotspotsystem workflow end-to-end (including discovery, connection, and first execution).
Running recurring hotspot maintenance tasks (e.g., periodic updates or status checks).
Executing a specific hotspot operation after verifying updated tool schemas via RUBE_SEARCH_TOOLS.
Performing bulk operations (enable/disable) on multiple hotspots using bulk tools.
Validating tool schemas and connection status before critical workflows to prevent failures.

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Hotspotsystem tool slugs and input schemas.
Step 3: Manage the connection with RUBE_MANAGE_CONNECTIONS (toolkit: hotspotsystem) and execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools.
Do not hardcode tool slugs or arguments; derive them from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs for related workflows and fetch new ones only for separate tasks.

Example Use Cases

Create a new hotspot using a discovered tool slug and required arguments, then verify the hotspot exists and is active.
Update hotspot metadata (name, location) by selecting the appropriate tool slug from the latest search results and supplying exact field values.
Bulk disable a subset of hotspots by running a bulk operation tool with a list of hotspot IDs and an empty memory payload.
Query current hotspot status and usage statistics using a read-only tool to monitor performance.
Before a major deployment, re-run RUBE_SEARCH_TOOLS to confirm tool schemas have not changed and refresh the available tool slugs.

Frequently Asked Questions

Add this skill to your agents