$ ~/registry/skill/composiohq-composio-skills-2chat-automation

SKILL

-2chat-automation

Name: -2chat-automation
Author: Composio

Automate 2chat workflows via Rube MCP after checking 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

The skill material itself is an open-source prompt-style README with no declared local secrets or local code execution, so overall risk is low. However, it is intended to connect to remote Rube MCP and then operate 2chat, which introduces third-party connectivity and account authorization considerations during actual use.

CredentialsCaution

The material states there are 'no API keys', but it requires establishing an ACTIVE `_2chat` connection via `RUBE_MANAGE_CONNECTIONS` and completing setup through a returned auth link. This implies third-party account authorization/tokens in practice, even if no environment variables are exposed in the skill itself.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute 2chat operations. Therefore, user inputs, session identifiers, and task arguments may be sent to that declared third-party service, with no additional unknown exfiltration endpoint shown in the material.

Code executionLow risk

Per the provided checks, this skill is prompt-only. The material only describes an MCP tool-calling workflow and does not declare any need to start local processes, install scripts, or execute local code.

Data accessCaution

The skill text does not declare local file read/write access, but its purpose is to perform 2chat operations through Rube/Composio. The effective data scope depends on the connected 2chat account and the discovered tool schemas, creating a normal permission surface over third-party business data for reading/modifying.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk. The current material is also just README/prompt content. Still, the license is unspecified and maintenance status is unknown, so ongoing verification of upstream activity is advisable.

Recommendations

Use it only if you are comfortable sending task parameters to `https://rube.app/mcp` and related 2chat/Composio services.
Review the authorization scope when connecting `_2chat`, and prefer least-privilege or test accounts.
Avoid placing unnecessary sensitive data in tool arguments, and log which tool slugs and targets were actually used.
Periodically verify that the upstream repository, Rube MCP endpoint, and Composio documentation remain active and consistent.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

2chat Automation via Rube MCP

Automate 2chat operations through Composio's 2chat toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/_2chat

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["_2chat"]
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 2chat-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `_2chat`
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 Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_