What if tool schemas change?

Always fetch current schemas with RUBE_SEARCH_TOOLS and do not hardcode tool slugs or arguments.

Do I need an active Coassemble connection before executing tools?

Yes, ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE for the coassemble toolkit.

What is memory used for in RUBE_MULTI_EXECUTE_TOOL?

Memory carries workflow state and arguments; include it even if empty ({}).

coassemble-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/coassemble-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Coassemble Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/coassemble

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["coassemble"]
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 Coassemble-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `coassemble`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/coassemble-automation/SKILL.mdView on GitHub

Overview

Coassemble Automation via Rube MCP enables programmatic control of Coassemble operations through Composio's toolkit. It emphasizes discovering up-to-date tool schemas with RUBE_SEARCH_TOOLS and validating an ACTIVE connection before execution, ensuring resilient automation.

How This Skill Works

Connect to Rube MCP and verify connectivity with RUBE_SEARCH_TOOLS. Discover available Coassemble tools, then check the active connection with RUBE_MANAGE_CONNECTIONS before executing any tool with RUBE_MULTI_EXECUTE_TOOL. Use session IDs and memory payloads as shown in the Core Workflow Pattern.

When to Use It

Automating repetitive Coassemble admin tasks (e.g., creating tasks or pipelines) to save time.
When tool schemas change and you must fetch the latest inputs and arguments before running.
To bulk run multiple Coassemble operations in a single automation workflow.
When ensuring a known-good connection status before tool execution in scheduled or triggered jobs.
To integrate Coassemble automation with other MCP workflows using shared session management.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS is available.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["coassemble"] and complete auth if the connection is not ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; do not hardcode slugs or args.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and create new ones for distinct workflows.

Example Use Cases

Automate a Coassemble task creation by discovering the appropriate TOOL_SLUG and supplying required arguments.
Execute a batch of Coassemble workflows in one run using RUBE_MULTI_EXECUTE_TOOL with multiple tool_slugs.
Validate the Coassemble connection is ACTIVE before starting a scheduled automation job.
Fetch the latest tool schemas via RUBE_SEARCH_TOOLS and adapt automation scripts accordingly.
Integrate Coassemble automation into a larger Composio workflow by reusing a session across steps.

Frequently Asked Questions

Add this skill to your agents