Do I need API keys to use Rube MCP for Ably automation?

No API keys are required—add the MCP endpoint and your toolkit config; authentication is handled via the Rube workflow.

Why must I always search tools before running a workflow?

Tool schemas change over time. Re-fetching with RUBE_SEARCH_TOOLS ensures you use current slugs and field names.

Which commands are used to discover, connect, and execute Ably tools?

Use RUBE_SEARCH_TOOLS to discover tools, RUBE_MANAGE_CONNECTIONS to connect, and RUBE_MULTI_EXECUTE_TOOL to run the selected tool.

ably-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Ably Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ably

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ably"]
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 Ably-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ably`
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/ably-automation/SKILL.mdView on GitHub

Overview

Automate Ably operations through Composio's Ably toolkit via Rube MCP. It emphasizes discovering current tool schemas before running workflows to adapt to schema changes.

How This Skill Works

Connect to Ably via the Rube MCP and fetch current tool schemas with RUBE_SEARCH_TOOLS. Choose a tool slug, then verify the Ably connection with RUBE_MANAGE_CONNECTIONS and run the tool with RUBE_MULTI_EXECUTE_TOOL. Always include a memory payload and reuse session IDs to keep workflows consistent.

When to Use It

Automate routine Ably operations (e.g., message routing, presence checks) using the Ably toolkit.
When tool schemas change, fetch current schemas with RUBE_SEARCH_TOOLS before proceeding.
Set up and validate the Ably connection via RUBE_MANAGE_CONNECTIONS before running workflows.
Execute multiple tools in a single session using RUBE_MULTI_EXECUTE_TOOL with a shared session_id.
Handle long-running or error-prone workflows by reusing memory and session information to retry cleanly.

Quick Start

Step 1: Add the MCP endpoint at https://rube.app/mcp to your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to verify availability and fetch Ably tool schemas.
Step 3: Connect and execute a tool using RUBE_MANAGE_CONNECTIONS followed by RUBE_MULTI_EXECUTE_TOOL with a memory payload and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing tools to get current slugs and schemas.
Verify the connection status shows ACTIVE with RUBE_MANAGE_CONNECTIONS before any tool execution.
Use exact field names and types from the search results to avoid schema errors.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {}).
Reuse session IDs within a workflow and only generate new ones for new workflows.

Example Use Cases

Discover available Ably tools with RUBE_SEARCH_TOOLS and execute a specific operation.
Connect to Ably toolkit using RUBE_MANAGE_CONNECTIONS and verify ACTIVE before tasks.
Run a multi-step workflow using RUBE_MULTI_EXECUTE_TOOL with a discovered slug.
Handle changing tool schemas by re-searching tools before execution.
Perform bulk or remote bench tasks with RUBE_REMOTE_WORKBENCH and run_composio_tool().

Frequently Asked Questions

Add this skill to your agents