Skip to main content
skill CX Codex

Photoshop — Claude Code skill: drive Photoshop from the shell

This skill lets a coding agent work inside Adobe Photoshop: inspect the open document, layers and selection, then make bounded edits.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add SFKislev/Flue --skill photoshop -a claude-code
Open on GitHub

What Photoshop does

It runs on Flue, a local bridge between the shell and the application. The agent pipes ExtendScript into photoshop_bridge.py and gets structured JSON back. Shell to bridge to ExtendScript to result.

Reach for it when the request is about something happening inside Photoshop: check the open document, look at layers or the selection, apply a small edit, run a short ExtendScript step. A CLI agent has no way in without a bridge like this.

Read FLUE.md in the skill directory first. It covers how Flue works, the bridge contract, a worked ExtendScript example and safety expectations. If Flue is already installed, also read C:\Users\fredd\.claude\skills\flue\SKILL.md and adapters/photoshop_adapter/APP.md. If it is not, tell the human: the install is pip install flue && flue setup, and it should not run without explicit approval in the current session. Flue acts inside professional desktop software, so keep steps small and inspectable, and avoid destructive actions unless they are asked for.

What it helps with

  • inspect layers and selection in the open document
  • apply a bounded edit to a layout from the terminal
  • run a short ExtendScript step without manual clicking
  • check document state before an export
  • hand the agent a JSON result to branch on

Example prompts for the agent

  • Inspect the open Photoshop document and list its layers with visibility.
  • Hide the watermark layer and return JSON with the new state.
  • Check the active selection and tell me its pixel dimensions.

How to install Photoshop

1Skills CLI (Vercel)

npx skills add SFKislev/Flue --skill photoshop -a claude-code

2Manually: put the files in place

~/.claude/skills/photoshop/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/photoshop/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about Photoshop

How do I install the Photoshop skill in Claude?

Run npx skills add SFKislev/Flue --skill photoshop -a claude-code. The skill file lands at ~/.claude/skills/photoshop/SKILL.md.

What does the Photoshop skill do?

It lets an agent operate inside Adobe Photoshop through Flue: the agent pipes ExtendScript into photoshop_bridge.py and gets structured JSON back.

What do I need for it to work?

Flue has to be installed — pip install flue && flue setup. Without it the skill tells the human and does not install anything on its own without approval in the current session.

Source text

SKILL.md · MIT
---
name: Photoshop
description: Control Adobe Photoshop from the shell via Flue - ExtendScript bridges without an MCP server.
---
This skill lets a coding agent operate **Adobe Photoshop** on the desktop through [Flue](https://github.com/SFKislev/flue), a local shell-to-application bridge. The agent pipes ExtendScript into `photoshop_bridge.py` and gets structured JSON back.

> agent shell -> `photoshop_bridge.py` -> ExtendScript -> JSON result

## When to use
The human requests work performed **inside Photoshop** — inspect the open document, layers, selection; make bounded edits; run small ExtendScript steps. A CLI agent cannot act inside Photoshop without a bridge like Flue.

## How to proceed
1. **Read `FLUE.md` in this directory first.** It explains how Flue works, the bridge contract, a worked ExtendScript example, and safety expectations. 
2. **If Flue is installed:** also read `C:\Users\fredd\.claude\skills\flue\SKILL.md` and `adapters/photoshop_adapter/APP.md` for the operational contract, then work from there.
3. **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 Illustrator, Premiere, After Effects, InDesign, Audition, Blender, Houdini, 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.

© SFKislev · MIT · SFKislev/Flue

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set10

flue A skill that lets an agent run code inside desktop apps like Photoshop, Blender, Unity and Excel. Useful when the work has to happen in the application itself. CX Codex +1 12,600installs Blender Connects an agent to a running Blender instance via Flue. It sends Python code directly into bpy without an MCP server and returns structured JSON. CX Codex +1 2,800installs Illustrator Control desktop Adobe Illustrator from the shell using the Flue bridge. The skill runs ExtendScript scripts and returns structured JSON without an MCP server. CX Codex +1 2,100installs Adobe Connects coding agents to Photoshop, Illustrator, Premiere, After Effects, InDesign, and Audition via Flue. Runs ExtendScript and returns JSON without an MCP server. CX Codex +1 1,900installs InDesign Connects a coding agent to desktop Adobe InDesign using the Flue bridge. It lets the agent inspect spreads, frames, and styles without an MCP server. CX Codex +1 1,800installs Autodesk This skill lets a coding agent work inside Autodesk 3ds Max: inspect the open scene, objects, modifiers and materials, make bounded edits, run a small script. CX Codex +1 1,800installs Premiere Control Adobe Premiere Pro from the shell through Flue. The agent pipes ExtendScript into premiere_bridge.py and gets structured JSON back. CX Codex +1 1,800installs Houdini Controls SideFX Houdini from the shell using the Flue Python bridge without an MCP server. Useful for inspecting nodes, parameters, and geometry. CX Codex +1 1,800installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor