adobe-automator

---
name: adobe-automator
description: "Universal Adobe application automation via ExtendScript bridge. Supports Photoshop, Illustrator, InDesign, Premiere Pro, and After Effects."
metadata:
  {
    "openclaw":
      {
        "requires": { 
          "bins": [], 
          "os": ["windows", "macos"],
          "env": [], 
          "config": [] 
        }
      }
  }
---

# Adobe Master Automator (v1.1.2)

A generalized skill for automating multiple Adobe applications using a cross-platform ExtendScript bridge.

## Supported Applications

- **Photoshop**
- **Illustrator**
- **InDesign**
- **Premiere Pro**
- **After Effects**

## Commands

### runScript
Executes raw ExtendScript (ES3) in the target application.

**Parameters:**
- `app`: Target application (`photoshop`, `illustrator`, `indesign`, `premiere`, `aftereffects`).
- `script`: The JSX code to execute.

## 🛠 AI Protocol

### 1. Technical Constraints
- **ES3 Syntax Only**: Adobe apps use the ExtendScript (ES3) engine. Avoid modern JS features.
- **Target App Availability**: Ensure the target application is installed and running (or able to launch) on the host system.

### 2. Security & Side Effects
> [!CAUTION]
> **High Risk Capability**: The `runScript` command accepts and executes **arbitrary ExtendScript (JSX)** code. Attempting to restrict this would break the skill's core purpose, but users must be aware of the implications.

- **Filesystem Access**: The Adobe ExtendScript engine has **unrestricted access to the host filesystem** via the `File` and `Folder` objects.
- **Untrusted Scripts**: ❌ **NEVER** execute scripts from untrusted sources. A malicious script could delete files, exfiltrate data, or install persistent malware.
- **Verification**: Always inspect the `script` parameter payload before allowing execution.

## Setup

The skill automatically detects your operating system and routes commands to the appropriate application.
- **Windows**: Uses built-in `cscript` (Windows Script Host).
- **macOS