adobe-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/adobe-automation --openclawAdobe Automation via Rube MCP
Automate Adobe operations through Composio's Adobe toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/adobe
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Adobe connection via
RUBE_MANAGE_CONNECTIONSwith toolkitadobe - 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 toolkitadobe - 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: "Adobe 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 Adobe task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["adobe"]
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 Adobe-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit adobe |
| 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/adobe-automation/SKILL.mdView on GitHub Overview
Automate Adobe operations through Composio's Adobe toolkit via Rube MCP. The setup prioritizes discovering current tool schemas before workflows to keep integrations up to date and avoid hard-coded slugs. It provides a repeatable pattern for connecting, validating, and executing Adobe tasks.
How This Skill Works
Set up Rube MCP by adding the rube.app/mcp endpoint and verify availability with RUBE_SEARCH_TOOLS. Connect the Adobe toolkit using RUBE_MANAGE_CONNECTIONS and ensure the connection status is ACTIVE before any workflow. Discover available tools with RUBE_SEARCH_TOOLS to get tool slugs, input schemas, and execution plans, then execute using RUBE_MULTI_EXECUTE_TOOL with the required memory payload and a valid session_id.
When to Use It
- You need to automate recurring Adobe tasks and want to pull current tool schemas before running.
- Batch multiple Adobe operations in a single workflow using discovered tool slugs.
- Validate and establish an ACTIVE Adobe connection prior to execution.
- Reuse a session ID within a workflow and manage new workflows with fresh sessions.
- Handle schema changes and pagination by re-discovering tools instead of hardcoding values.
Quick Start
- Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client.
- Step 2: Verify availability with RUBE_SEARCH_TOOLS and connect the Adobe toolkit via RUBE_MANAGE_CONNECTIONS; ensure ACTIVE status.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using a valid session_id and memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results for schema compliance.
- Include the memory parameter 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
- Discover tools for Adobe operations, then run TOOL_SLUG_FROM_SEARCH with arguments matching the discovered input schema to batch-export PDFs.
- Automate a sequence of Adobe tasks by first validating the ACTIVE connection, then executing multiple tools in one session using RUBE_MULTI_EXECUTE_TOOL.
- Update metadata or properties in Adobe assets by using a discovered tool slug and supplying schema-compliant arguments.
- Handle tool schema changes by re-running RUBE_SEARCH_TOOLS before triggering workflows rather than hardcoding slugs.
- Leverage RUBE_REMOTE_WORKBENCH to run composio tools in bulk, using run_composio_tool() for large-scale Adobe tasks.
