amara-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/amara-automation --openclawAmara Automation via Rube MCP
Automate Amara operations through Composio's Amara toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amara
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Amara connection via
RUBE_MANAGE_CONNECTIONSwith toolkitamara - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitamara - 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: "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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/amara-automation/SKILL.mdView on GitHub Overview
This skill automates Amara operations using Composio's Amara toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before workflows and ensuring an ACTIVE connection via RUBE_MANAGE_CONNECTIONS.
How This Skill Works
The workflow starts by querying RUBE_SEARCH_TOOLS to fetch available Amara tool slugs and schemas. It then uses RUBE_MANAGE_CONNECTIONS to ensure the Amara toolkit is connected and ACTIVE. Finally, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing the required arguments, memory, and a session_id.
When to Use It
- When you need end-to-end automation of Amara operations from discovery to execution
- When tool schemas change frequently and you must fetch the latest slugs and fields
- When you want to ensure the Amara connection is ACTIVE before running tools
- When running multiple Amara tasks in a single workflow
- When you must preserve and reuse session context across steps
Quick Start
- Step 1: Configure MCP by adding https://rube.app/mcp as an MCP server in your client
- Step 2: Discover available Amara tools with RUBE_SEARCH_TOOLS using the Amara use_case
- Step 3: Connect and execute: run RUBE_MANAGE_CONNECTIONS for amara, then RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory
Best Practices
- Always call RUBE_SEARCH_TOOLS before any workflow to get current tool schemas
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
- Use exact field names and types from the search results (no hardcoding)
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
- Reuse session IDs within a workflow; generate new ones for new runs
Example Use Cases
- Automate a batch of Amara subtitling tasks by discovering tools, connecting, and executing multiple tools in sequence
- Fetch the latest Amara operation schemas and run a single tool with proper arguments
- Connect to Amara, verify status, then execute a bulk set of tasks using discovered tool slugs
- Orchestrate a workflow that searches for tools, checks connection, and runs several tools with shared session_id
- Handle evolving tool schemas by re-querying tools before each Amara workflow
