home / skills / composiohq / awesome-claude-skills / ably-automation

ably-automation skill

safe

/ably-automation

This skill automates Ably tasks via Rube MCP, guiding tool discovery, connection management, and compliant execution for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill ably-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: ably-automation
description: "Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Ably Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/ably](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `ably`
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: "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](https://composio.dev)*

Overview

This skill automates Ably operations through Composio's Ably toolkit using Rube MCP. It guides tool discovery, connection management, and safe execution patterns so agents can run real-time messaging tasks reliably. The focus is on always discovering current schemas and verifying connections before executing workflows.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Ably tool slugs and their input schemas. It then verifies or establishes an Ably connection via RUBE_MANAGE_CONNECTIONS. Finally it runs actions using RUBE_MULTI_EXECUTE_TOOL (or bulk runs via RUBE_REMOTE_WORKBENCH), always supplying schema-compliant arguments, a session_id, and a memory object.

When to use it

Automate channel, message, or presence operations in Ably
Run multi-step workflows that require current tool schemas
Perform bulk or remote workbench operations with Ably toolkit
Integrate Ably tasks into larger agent workflows that rely on Rube MCP
When you need an agent to discover and adapt to changing tool inputs

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or argument shapes
Verify toolkit connection status with RUBE_MANAGE_CONNECTIONS and complete any auth flow until ACTIVE
Use exact field names and types returned by search; follow schemaRef if provided
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (use {} if empty) and reuse session_id for a workflow
Handle pagination tokens in responses and continue fetching until complete

Example use cases

Send or schedule messages across Ably channels after discovering the correct publish tool schema
Query channel history or presence using discovered tools and schema-compliant arguments
Run bulk channel updates or migrations via RUBE_REMOTE_WORKBENCH with run_composio_tool()
Embed Ably event publishing into a larger automation that requires session reuse and connection checking
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS when you need exact validation rules

FAQ

What is the first call an agent should make?

Always call RUBE_SEARCH_TOOLS to get current tool slugs and input schemas before any other action.

How do I confirm the Ably connection is usable?

Call RUBE_MANAGE_CONNECTIONS with toolkit 'ably' and ensure the returned connection status is ACTIVE; follow any returned auth links if not ACTIVE.

Can I reuse session IDs across multiple steps?

Yes. Reuse the same session_id within a workflow; generate new session IDs for separate workflows to keep context isolated.