What is abyssale-automation?

Aabyssale-automation automates Abyssale tasks using Composio's Abyssale toolkit via Rube MCP.

Do I need API keys to use it?

No API keys are needed. Just configure the MCP server at https://rube.app/mcp and follow the discovery and connection steps.

What should I check before running workflows?

Ensure RUBE_SEARCH_TOOLS returns current tool schemas, confirm the Abyssale connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS, and include memory in RUBE_MULTI_EXECUTE_TOOL calls with the correct session_id.

abyssale-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Abyssale Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/abyssale

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Abyssale operations through Composio's Abyssale toolkit via Rube MCP. The process relies on discovering current tool schemas, establishing an ACTIVE Abyssale connection, and executing tools with the proper arguments and memory. This approach keeps workflows resilient to schema changes and streamlines repetitive tasks.

How This Skill Works

First, discover available Abyssale tools and their input schemas with RUBE_SEARCH_TOOLS. Then verify the Abyssale connection is ACTIVE using RUBE_MANAGE_CONNECTIONS with the abyssale toolkit. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug, exact arguments, memory, and the session_id from the discovery step.

When to Use It

Automating repetitive Abyssale tasks across multiple assets or campaigns
Tool schemas change and you need up-to-date slugs and fields without hardcoding
Batching multiple Abyssale actions in a single workflow using a shared session
Performing pre-flight checks to ensure the connection is ACTIVE before running tools
Handling pagination or large result sets by sequentially discovering and executing tools

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed)
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Abyssale tool schemas and review inputs
Step 3: Ensure the Abyssale connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory

Best Practices

Always search first: tool schemas change; fetch current schemas before execution
Check connection: ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results to avoid errors
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate exporting a batch of new assets to Abyssale by discovering the correct tool, validating the ACTIVE connection, and executing with a single session
Update multiple product images by sequencing several Abyssale tool executions in one workflow using a shared session
Adapt to tool schema changes by re-running RUBE_SEARCH_TOOLS before executing any tool
Reconnect after an intermittent loss by ensuring RUBE_MANAGE_CONNECTIONS reports ACTIVE before continuing
Fetch all tool schemas with RUBE_GET_TOOL_SCHEMAS and perform bulk operations across tools

Frequently Asked Questions

Add this skill to your agents