Adobe
sfkislev/flue
Control Adobe desktop apps (Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition) via shell commands using Flue.
What is Adobe?
This skill enables a coding agent to operate Adobe desktop applications through Flue, a local shell-to-application bridge that pipes ExtendScript commands and returns structured JSON results. Use it when you need to inspect or edit documents inside Adobe apps from the command line.
- Execute ExtendScript commands in Photoshop, Illustrator, Premiere Pro, After Effects, InDesign, and Audition
- Pipe structured commands through per-app bridge processes and receive JSON responses
- Inspect open documents and projects without manual interaction
- Perform bounded edits and small ExtendScript steps programmatically
- Access the same bridge contract across multiple Adobe applications
How to install Adobe
npx skills add null --skill adobe- Flue installed and configured (install via `pip install flue && flue setup`)
- One or more Adobe desktop applications (Photoshop, Illustrator, Premiere Pro, After Effects, InDesign, or Audition) installed and running
- Read FLUE.md and the matching app adapter documentation (e.g., `adapters/photoshop_adapter/APP.md`)
How to use Adobe
- 1.Identify which Adobe application the task targets (Photoshop, Illustrator, Premiere, After Effects, InDesign, or Audition)
- 2.Load the matching adapter bridge process (e.g., `adapters/photoshop_adapter/photoshop_bridge.py`)
- 3.Compose an ExtendScript command and pipe it to the bridge via stdin
- 4.Parse the returned JSON response to confirm the action or retrieve document data
- 5.Repeat with additional commands as needed, keeping steps small and inspectable
Use cases
- Automate repetitive editing tasks in Photoshop or Illustrator from a CLI workflow
- Query document properties and layer information from an open project
- Execute small, inspectable edits in Premiere Pro or After Effects timelines
- Batch process InDesign documents or Audition audio files via shell commands
- Integrate Adobe app operations into a larger agent-driven automation pipeline
- Coding agents (Claude Code, Cursor) automating Adobe workflows
- Developers building CLI bridges to professional desktop software
- Teams automating design or media production tasks
- Users who want programmatic control of Adobe apps without manual UI interaction
Adobe FAQ
No. Flue works as a direct shell-to-application bridge without requiring an MCP server. It uses stdin/stdout to communicate with per-app bridge processes.
Photoshop, Illustrator, Premiere Pro, After Effects, InDesign, and Audition. Flue also supports Blender, Houdini, Autodesk 3ds Max, Unity, and Microsoft Office through the same contract.
The agent will notify you and provide the install command (`pip install flue && flue setup`). Installation requires explicit approval before proceeding.
Flue is safe but should be used carefully. Treat the human as the driver, prefer small inspectable steps, and avoid destructive actions unless explicitly requested.
Read FLUE.md in the skill directory for the bridge contract and a worked example, then consult the matching `adapters/<app>_adapter/APP.md` for app-specific operations.
Full instructions (SKILL.md)
Source of truth, from sfkislev/flue.
name: Adobe description: Control Adobe desktop apps - Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition - from the shell via Flue, without an MCP server.
This skill lets a coding agent operate Adobe desktop applications through Flue, a local shell-to-application bridge. The agent pipes ExtendScript into a per-app bridge process and gets structured JSON back. Flue covers Photoshop, Illustrator, Premiere Pro, After Effects, InDesign, and Audition through a consistent stdin/stdout contract.
agent shell ->
<app>_bridge.py-> ExtendScript -> JSON result
When to use
The human requests work performed inside an Adobe desktop app — inspect the open document or project, make bounded edits, run small ExtendScript steps. A CLI agent cannot act inside these apps without a bridge like Flue.
How to proceed
- Read
FLUE.mdin this directory first. It explains how Flue works, the bridge contract, a worked ExtendScript example, and safety expectations. - Identify which Adobe app the human is working in — Photoshop, Illustrator, Premiere, After Effects, InDesign, or Audition — and use the matching adapter (e.g.
adapters/photoshop_adapter/photoshop_bridge.py). - If Flue is installed: also read
C:\Users\fredd\.claude\skills\flue\SKILL.mdand the matchingadapters/<app>_adapter/APP.mdfor the operational contract, then work from there. - If Flue is not installed: tell the human. The install command is
pip install flue && flue setup. Do not install without explicit approval in the current session.
Other apps
Flue also supports Blender, Houdini, Autodesk 3ds Max, Unity, and Microsoft Office through the same stdin/stdout contract. One install covers all adapters.
Safety
Flue acts inside professional desktop software. Treat the human as the driver; prefer small, inspectable steps; avoid destructive actions unless explicitly requested. Flue is MIT-licensed and reviewable on GitHub / PyPI before use.
Related skills
More from sfkislev/flue and the wider catalog.
Audition
Control Adobe Audition from the shell via Flue—ExtendScript bridges without an MCP server.
Autodesk
Control Autodesk 3ds Max and other desktop apps from the shell via Flue, without an MCP server.
Blender
Control Blender from the shell via Flue, a Python bridge to bpy without an MCP server.
flue
Control desktop software like Photoshop, Blender, and Office from your agent via native automation APIs.
Houdini
Control SideFX Houdini from the shell via Flue, a Python bridge to hou without an MCP server.
Illustrator
Control Adobe Illustrator from the shell via Flue ExtendScript bridges.