Skip to main content

2chat-automation

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

Zur Installation springen

Quellinformationen

Repository
onfire7777/universal-ai-skills-library
Letzte Quellaktivität
10. Mai 2026 um 01:21
Erkannte Sprache von SKILL.md
Englisch
Sterne
16
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
2chat-automation
description
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
requires
{"mcp":["rube"]}
# 2chat Automation via Rube MCP Automate 2chat operations through Composio's 2chat toolkit via Rube MCP. **Toolkit docs**: [composio.dev/toolkits/_2chat](https://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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `_2chat` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. 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](https://composio.dev)*
Auf GitHub ansehen