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

SKILL

supportbee-automation

Name: supportbee-automation
Author: Composio

Automate Supportbee tickets and support workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt/instruction wrapper with no clear red flags such as local code execution, file access, or embedded secrets. The main security consideration is the normal external data transfer and account-authorization exposure introduced by connecting Rube MCP and a Supportbee account.

CredentialsCaution

The material says there are 'no API keys', but it requires creating a `supportbee` connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which implies third-party account authorization/OAuth credentials. No hardcoded secrets are shown in the skill itself; exposure mainly depends on the scope granted to the connected Supportbee account.

Network egressCaution

The README explicitly requires adding `https://rube.app/mcp` as an MCP server and performing Supportbee actions through Composio/Rube. Therefore, user requests, tool arguments, and some ticket/support data are likely transmitted via Rube/Composio to Supportbee, which is normal egress consistent with the stated function.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no executable scripts, install commands, or requirement to launch extra local processes. Its behavior depends on external MCP tool calls rather than arbitrary local code execution.

Data accessCaution

There is no indication of local file or system access, but once the Supportbee connection is active, the skill can query or perform bulk actions on Supportbee business data through discovered tools. The effective data scope depends on the privileges of the connected account, so high-privilege accounts should be avoided.

Supply chainLow risk

The source is an open-source GitHub repository with high community adoption (~64.7k stars), which materially lowers supply-chain risk. However, the license is not stated, maintenance status is unknown, and actual execution depends on third-party Rube/Composio services, so their upstream changes and terms should still be reviewed.

Recommendations

Authorize using a least-privilege Supportbee account and avoid admin-level access where possible.
Before connecting, verify whether `rube.app`/Composio data handling, logging retention, and privacy terms meet your compliance needs.
Apply a whitelist to the Supportbee tools that may be executed, especially bulk modify, delete, or export actions.
Periodically review changes in the skill documentation and upstream MCP tool schemas to prevent unexpected expansion of data access.

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 "supportbee-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/supportbee-automation/SKILL.md
2. Save it as ~/.claude/skills/supportbee-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Supportbee Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/supportbee

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["supportbee"]
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 Supportbee-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `supportbee`
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 EspoCRM tasks and streamline customer workflows through Rube MCP.

ComposioGet→

$ loading_