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

SKILL

breeze-automation

Name: breeze-automation
Author: Composio

Automate Breeze tasks via Rube MCP with schema-aware tool discovery first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be primarily a prompt/instruction layer for using Rube MCP and Composio Breeze tools, with no direct key requirement or explicit local code execution in the material. The main concern is reliance on a remote MCP service and external Breeze connection, which may route user data externally, so the overall posture is caution rather than high risk.

CredentialsCaution

The material says 'No API keys needed', but it also requires establishing an ACTIVE Breeze connection via `RUBE_MANAGE_CONNECTIONS` and following an external auth link. This suggests the skill does not directly collect secrets, yet third-party account access is still managed through Rube/external authorization, which carries normal account-linking and mis-authorization risk.

Network egressCaution

The README explicitly instructs users to add the remote MCP endpoint `https://rube.app/mcp` and perform remote operations through Composio/Breeze tools. User prompts, queries, tool arguments, and session information may be sent through that service chain. The endpoint is declared and related to the stated purpose, but this is still a standard external data egress scenario.

Code executionLow risk

Based on the provided material, this is prompt-only and does not include install scripts, shell commands, or instructions to start local processes. Its core behavior is invoking existing MCP tool interfaces rather than directly requesting host-side code execution. No local execution red flags are evident from the material.

Data accessCaution

The skill is intended to 'Automate Breeze operations' and supports execution modes such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`. The exact data scope depends on Breeze tool schemas and the connected account permissions, and the material does not define a least-privilege boundary, so it should be treated as potentially accessing data and actions associated with the Breeze account.

Supply chainLow risk

The source is a GitHub open-source repository, system-marked as open-source, with high community adoption (about 64.9k stars), all of which are strong risk-reducing signals. Although the license is undeclared and maintenance status is unknown, and the entry depends on the trustworthiness of external Rube/Composio services, the current material does not show closed-source exfiltration, untrusted provenance, or obvious prompt-injection style red flags.

Recommendations

Enable it only after you trust the `rube.app/mcp`, Composio, and Breeze authorization chain, and review their privacy/data-handling terms.
Apply least privilege when connecting a Breeze account; prefer a restricted test account and avoid granting unnecessary data or write permissions.
Inspect the schemas and parameters returned by `RUBE_SEARCH_TOOLS` before using `RUBE_MULTI_EXECUTE_TOOL`, to avoid sending sensitive content to remote tools.
Log and periodically review established external connections, and revoke Breeze/Rube authorizations that are no longer needed.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Breeze Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/breeze

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["breeze"]
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 Breeze-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `breeze`
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 browser tool tasks via Rube MCP with schema lookup first.

ComposioGet→

$ loading_