How do I start automating Ambee tasks?

Add the MCP server, verify RUBE_SEARCH_TOOLS, manage an active Ambee connection, and execute tools with RUBE_MULTI_EXECUTE_TOOL using discovered slugs.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change frequently; fetching current slugs and argument schemas prevents hardcoding and errors.

Is an active Ambee connection required?

Yes. Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running any workflows.

ambee-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Ambee Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ambee

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Ambee operations through Composio's Ambee toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any tasks, ensuring compatibility with updated tool slugs and arguments. A connected Rube MCP and an active Ambee connection are required to execute workflows.

How This Skill Works

Start by discovering available Ambee tools using RUBE_SEARCH_TOOLS, then confirm an ACTIVE Ambee connection via RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool through RUBE_MULTI_EXECUTE_TOOL, passing the discovered schema-compliant arguments and a memory object, reusing a session across the workflow.

When to Use It

When automating routine Ambee operations via Composio.
When tool schemas change and you must fetch latest slugs.
When validating and reusing a session across multiple Ambee tasks.
When ensuring an ACTIVE Ambee connection before execution.
When integrating Ambee tasks into larger automated workflows that rely on RUBE MCP.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Ambee tool schemas and confirm availability.
Step 3: Use RUBE_MANAGE_CONNECTIONS (toolkit: ambee) to activate the connection, then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types from search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and manage new ones for new tasks.

Example Use Cases

Automate hourly Ambee weather data retrieval for multiple locations.
Run a batch of Ambee analysis tasks using discovered tools in a single session.
Onboard a new Ambee integration by verifying active connection and executing a test tool.
Audit and update an automation pipeline when tool schemas change.
Migrate routine Ambee checks into a scheduled Composio workflow.

Frequently Asked Questions

Add this skill to your agents