$ ~/registry/skill/composiohq-composio-skills-ably-automation

SKILL

ably-automation

Name: ably-automation
Author: Composio

Automate Ably workflows through Rube MCP using the latest tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/template with no declared local execution, file access, or built-in secret requirement, so its baseline risk is low. However, it is explicitly designed to drive remote Rube MCP/Composio workflows and connect an Ably account, so credential delegation, data egress, and external-service dependency still warrant attention.

CredentialsCaution

The material says no API key is needed, but it requires an ACTIVE `ably` connection via `RUBE_MANAGE_CONNECTIONS` and completion of a returned auth link. This suggests credentials are likely delegated or managed through Rube/Composio rather than absent, creating the usual third-party account authorization considerations.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and executing actions through Composio's Ably toolkit. Therefore, task inputs, session data, and Ably-related information are likely transmitted through external services. This egress path matches the stated function, but it is still a standard remote-service dependency that should be reviewed for data minimization and trust boundaries.

Code executionLow risk

The objective checks mark it as `prompt-only`, and the material does not claim to start local processes, run scripts, or request system-level privileges. It mainly describes invocation order and tool-discovery/execution patterns, without showing additional code-execution capability by itself.

Data accessCaution

The material does not show local filesystem access or host data access, but its stated purpose is to automate Ably operations through `RUBE_MULTI_EXECUTE_TOOL`/`RUBE_REMOTE_WORKBENCH`. Once the account connection is established, the skill may indirectly access Ably resources and related business data, with scope determined by the granted connection permissions and selected tools.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), both of which are meaningful risk-reducing signals. The visible content is mainly README/prompt-template material rather than an executable binary. Note that the license is undeclared, maintenance is unknown, and actual operation depends on external Rube/Composio services, but the available material does not show concrete red flags sufficient for a high-risk rating.

Recommendations

Only connect Rube/Composio when Ably automation is actually needed, and prefer the minimum Ably authorization scope.
Before production use, verify the privacy policy, log retention, and data-handling boundaries of `rube.app` and Composio, and avoid sending unnecessary sensitive content.
Manually review the actual tool schemas and executable actions returned by `RUBE_SEARCH_TOOLS` to avoid dynamic tool discovery invoking operations beyond expectation.
If your organization has compliance requirements, verify repository maintenance status, license details, and the security/audit documentation for the external services.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "ably-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/ably-automation/SKILL.md
2. Save it as ~/.claude/skills/ably-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate V0 workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_