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

amara-automation skill

safe

/amara-automation

This skill automates Amara operations via Rube MCP, ensuring up-to-date tool schemas by always searching tool definitions first.

npx playbooks add skill composiohq/awesome-claude-skills --skill amara-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: amara-automation
description: "Automate Amara tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Amara Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/amara](https://composio.dev/toolkits/amara)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["amara"]
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 Amara-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `amara` |
| 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 Amara operations through Composio's Amara toolkit using Rube MCP. It provides a repeatable pattern to discover tools, verify connections, and execute Amara tasks reliably. The skill emphasizes dynamic tool discovery to avoid schema drift and enforces session and memory best practices.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, and recommended execution plans. It then verifies an active Amara connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes one or more tools with RUBE_MULTI_EXECUTE_TOOL (including memory and session_id) or runs bulk flows via RUBE_REMOTE_WORKBENCH.

When to use it

Automating uploads, captions, or metadata updates in Amara via Composio
Building repeatable workflows that must adapt to changing tool schemas
Orchestrating multi-step Amara operations across sessions and memory
Executing bulk operations or workbench scripts against the Amara toolkit
Integrating Amara tasks into larger Claude-driven automation pipelines

Best practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas and slugs
Confirm RUBE_MANAGE_CONNECTIONS reports an ACTIVE Amara connection before executing tools
Include a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id within a workflow; generate new session_ids for separate workflows
Follow exact field names and types returned by tool discovery—do not hardcode arguments

Example use cases

Discover the latest Amara upload tool and post a batch of subtitle files using RUBE_MULTI_EXECUTE_TOOL
Verify and reauthorize an Amara connection when a user link flow returns an inactive status
Run a bulk metadata update across many videos using RUBE_REMOTE_WORKBENCH run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before constructing complex payloads
Implement paginated fetches when search results include pagination tokens

FAQ

Do I need API keys to use Rube MCP?

No API keys are required—add the MCP endpoint (https://rube.app/mcp) to your client configuration and use the Rube MCP endpoints.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before each run or step that depends on the tool. If schemas change, adapt arguments to the returned schema and restart the step with the same or a new session_id as appropriate.