$ ~/registry/skill/composiohq-composio-skills-ambee-automation

SKILL

ambee-automation

Name: ambee-automation
Author: Composio

Automate Ambee workflows via Rube MCP using current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is essentially an open-source prompt/instruction wrapper with relatively strong source credibility, and no clear red flags for local execution or local file access. The main consideration is that it directs users to connect to a remote Rube MCP endpoint and authorize external Ambee/Composio integrations.

CredentialsCaution

The material says no API keys are needed, but it requires establishing an ACTIVE `ambee` connection via `RUBE_MANAGE_CONNECTIONS` and following an authorization link. This suggests credentials are handled as external OAuth/connection tokens rather than local environment variables. There is no explicit evidence of credential abuse, but the authorization scope and token custody with third parties should be reviewed.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and operate through Composio's Ambee toolkit. User inputs, queries, session IDs, tool arguments, and possibly Ambee-related business data may be transmitted through that remote service. This is typical network egress for this class of MCP/integration tool, and the material does not show unrelated or hidden exfiltration endpoints.

Code executionLow risk

The system flags this as `prompt-only`, and the provided content is limited to workflow guidance and tool invocation patterns. It does not describe starting local processes, running scripts, installing binaries, or requesting system-level execution privileges.

Data accessCaution

There is no indication of local filesystem or host-resource access. However, it invokes authorized Ambee tools via a remote MCP and uses session, memory, and pagination mechanisms to process workflow data, so it should be assumed to access whatever Ambee account/API data the user grants through that external connection. No signs of excessive local authorization beyond the stated use case are shown.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars). The material itself is mainly auditable text instructions rather than a closed-source executable component. Although the license is unspecified and maintenance status is unknown, these do not amount to high-risk red flags here, so overall supply-chain risk appears low.

Recommendations

Before connecting to `https://rube.app/mcp`, verify its privacy policy, data handling practices, and relationship to Composio/Ambee.
When authorizing the `ambee` connection, use the minimum scope possible and confirm what data categories the third party can access.
Avoid sending unnecessary sensitive information in queries, memory, or tool arguments.
Validate the skill in a controlled test account before using it in production.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "ambee-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/ambee-automation/SKILL.md
2. Save it as ~/.claude/skills/ambee-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Re:amaze support tasks via Rube MCP using current tool schemas.

ComposioGet→

$ loading_