home / skills / composiohq / awesome-claude-skills / aryn-automation
/aryn-automation
This skill automates Aryn tasks via Composio's Rube MCP, always discovering current tool schemas before execution.
npx playbooks add skill composiohq/awesome-claude-skills --skill aryn-automationReview the files below or copy the command above to add this skill to your agents.
---
name: aryn-automation
description: "Automate Aryn tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
---
# Aryn Automation via Rube MCP
Automate Aryn operations through Composio's Aryn toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/aryn](https://composio.dev/toolkits/aryn)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Aryn connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aryn`
- 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 `aryn`
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: "Aryn 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 Aryn task"}]
session: {id: "existing_session_id"}
```
### Step 2: Check Connection
```
RUBE_MANAGE_CONNECTIONS
toolkits: ["aryn"]
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 Aryn-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `aryn` |
| 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)*
This skill automates Aryn tasks through Composio’s Rube MCP integration. It guides discovery of available tools, manages Aryn connections, and executes toolkit operations while enforcing schema compliance and session management. Use it to reliably run single or bulk Aryn workflows from an automated agent.
The skill first calls RUBE_SEARCH_TOOLS to discover current tool slugs, input schemas, and recommended execution plans. It then verifies or establishes an Aryn connection via RUBE_MANAGE_CONNECTIONS and runs one or more operations with RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs), always passing a memory object and a session ID. It emphasizes searching tools first because schemas and slugs can change frequently.
Do I need API keys to use Rube MCP?
No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration and use the provided Rube MCP actions.
What if a tool slug or schema changes during a workflow?
Always call RUBE_SEARCH_TOOLS before executing. If schemas change mid-workflow, rediscover tools and adjust arguments to match the returned schema. Use new session IDs for distinct workflows.