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

abyssale-automation skill

safe

/abyssale-automation

This skill automates Abyssale tasks via Rube MCP, prioritizing tool discovery before execution to ensure up-to-date schemas.

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

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

Files (1)

SKILL.md

2.9 KB

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

# Abyssale Automation via Rube MCP

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

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

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

Overview

This skill automates Abyssale tasks by driving Composio's Abyssale toolkit through Rube MCP. It provides a repeatable pattern for discovering tools, validating connections, and executing operations while enforcing schema compliance and session management. Use it to run image generation, templates, and bulk operations from an automated agent workflow.

How this skill works

The skill always begins by calling RUBE_SEARCH_TOOLS to retrieve current tool slugs, schemas, and recommended execution plans. Next it verifies or creates an active Abyssale connection via RUBE_MANAGE_CONNECTIONS. Finally it executes one or more toolkit actions with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, passing schema-compliant arguments and a memory object.

When to use it

Automating Abyssale image generation or template processes from an agent
Running bulk image or asset operations via Composio in CI/CD or backend jobs
Orchestrating multi-step workflows that require discovering changing tool schemas
Embedding Abyssale actions inside larger Claude or agent-driven pipelines
When you need reliable session and connection management for Abyssale tasks

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument shapes
Check RUBE_MANAGE_CONNECTIONS and confirm connection status is ACTIVE before execution
Pass the exact field names and types returned in tool schemas; mismatches cause failures
Include a memory object (can be {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow; generate new sessions for independent workflows
Handle pagination in search results and follow returned pagination tokens

Example use cases

Discover current Abyssale image-generation tools and run a single-generation job using returned schema fields
Validate and complete an Abyssale connection flow for a new account, following the auth link returned by RUBE_MANAGE_CONNECTIONS
Execute bulk asset transformations with RUBE_REMOTE_WORKBENCH and run_composio_tool() for batch operations
Integrate Abyssale template rendering into a downstream publishing pipeline with session reuse
Automate nightly content refreshes by paginating tool lists, selecting compatible tools, and running scheduled RUBE_MULTI_EXECUTE_TOOL calls

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; the endpoint works without additional API keys.

What if tool schemas change between runs?

Always call RUBE_SEARCH_TOOLS at the start of each workflow to fetch current schemas and recommended execution plans; never assume schemas are stable.