Build, debug, package, and document Adobe Illustrator extensions, C++ SDK plug-ins, UXP plugins, MCP servers, and OS automation scripts.
- GitHub stars
- 41,038
- Files
- 5
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the adobe-illustrator-integrations skill do?
adobe-illustrator-integrations is an agent skill. Build, debug, package, and document Adobe Illustrator extensions, C++ SDK plug-ins, UXP plugins, MCP servers, and OS automation scripts.
Summary generated from the skill's SKILL.md.
About the adobe-illustrator-integrations skill
Developers building tools for Adobe Illustrator can use this skill to manage the entire lifecycle of an integration. It provides guidance for creating CEP extension panels, native C++ SDK plug-ins, and upcoming UXP plugins. It is designed for those who need to decide whether a feature should be delivered as a simple ExtendScript, a dockable HTML panel, or a high-performance native tool.
Beyond UI-based tools, the skill assists in setting up MCP servers that allow AI agents to drive Illustrator or configuring OS automation via batch, PowerShell, bash, or AppleScript. It helps organize project files and write technical documentation for published assets. While the adobe-illustrator-scripting skill handles the internal document object model, this skill focuses on the surrounding infrastructure, such as packaging signed ZXP files, debugging with the VS Code ExtendScript Debugger, and managing cross-platform automation through COM or AppleScript.
What an agent can do with it
- 1Select an integration typeDecide whether to build a script, a CEP extension, or a C++ plug-in based on your specific requirements.
- 2Develop CEP extension panelsBuild and fix HTML and JavaScript user interfaces that host ExtendScript within Illustrator.
- 3Automate Illustrator via command lineRun ExtendScript files using system scripts like PowerShell or bash to include Illustrator in a larger pipeline.
- 4Connect AI agents to IllustratorBuild or review an MCP server so an AI tool can interact with and drive Illustrator tasks.
- 5Create technical documentationWrite installation and usage instructions for a tool you intend to publish.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the adobe-illustrator-integrations skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the adobe-illustrator-integrations skill in Claude Code
~/.claude/skills/adobe-illustrator-integrations/SKILL.md
$ npx degit github/awesome-copilot/skills/adobe-illustrator-integrations ~/.claude/skills/adobe-illustrator-integrationsInstall the adobe-illustrator-integrations skill in Claude Code (project)
.claude/skills/adobe-illustrator-integrations/SKILL.md
$ npx degit github/awesome-copilot/skills/adobe-illustrator-integrations .claude/skills/adobe-illustrator-integrationsInstall the adobe-illustrator-integrations skill in Codex
~/.agents/skills/adobe-illustrator-integrations/SKILL.md
$ npx degit github/awesome-copilot/skills/adobe-illustrator-integrations ~/.agents/skills/adobe-illustrator-integrationsInstall the adobe-illustrator-integrations skill in Gemini CLI
~/.gemini/skills/adobe-illustrator-integrations/SKILL.md
$ npx degit github/awesome-copilot/skills/adobe-illustrator-integrations ~/.gemini/skills/adobe-illustrator-integrationsInstall the adobe-illustrator-integrations skill in Claude.ai
npx degit github/awesome-copilot/skills/adobe-illustrator-integrations adobe-illustrator-integrations && zip -r adobe-illustrator-integrations.zip adobe-illustrator-integrations # claude.ai → Customize → Skills → + → Create skill → Upload a skill → adobe-illustrator-integrations.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablegithub/awesome-copilot/skills/adobe-illustrator-integrations is public and reachablegithub.com/github/awesome-copilot/tree/HEAD/skills/adobe-ill ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/github/awesome-copilot/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/github/awesome-copilot/blob/HEAD/skills/adobe-ill ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/github/awesome-copilot/blob/HEAD/skills/adobe-ill ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 106 linesgithub.com/github/awesome-copilot/blob/HEAD/skills/adobe-ill ↗Pass
SKILL.md
View on GitHubAdobe Illustrator Integrations
Guidance for everything that sits around an Illustrator script: the panel a user clicks, the native plug-in that adds a tool, the command line or AI agent that starts Illustrator work from outside, and the documentation that ships with it. For the Illustrator DOM itself (documents, layers, paths, colors, exports), use the adobe-illustrator-scripting skill.
When to Use This Skill
- Choosing how to deliver an Illustrator feature: a script, a CEP extension, a C++ plug-in, a UXP plugin, an MCP server, or an OS automation script
- Building or fixing a CEP extension panel (HTML, JavaScript, and an ExtendScript host)
- Building or fixing a C++ plug-in (
.aip) with the Illustrator SDK - Running
.jsxscripts from batch, PowerShell, bash, Python, or AppleScript, including passing parameters and reading results - Building or reviewing an MCP server that lets an AI tool drive Illustrator
- Working in Illustrator through a computer-use tool when no scripting route exists
- Writing step-by-step instructions people follow by hand, or install and usage docs for an asset, script, extension, or plug-in someone will publish
- Organizing the files of an Illustrator project (sources, linked assets, exports, docs) so automation can find them
Script, Extension, or Plug-in
Adobe's own terms:
- A script is ExtendScript (
.jsx), AppleScript, or VBScript run against Illustrator's scripting object model. It has no persistent UI beyond ScriptUI dialogs. - An extension is a CEP panel: an HTML and JavaScript UI hosted in Illustrator that calls ExtendScript through
CSInterface.evalScript. - A plug-in is native code built with the Illustrator C++ SDK (
.aip). In apps that already run UXP (Photoshop, InDesign, Premiere Pro), "plugin" also means a UXP plugin; Illustrator UXP plugins are not public yet.
| Option | What it is | UI | Installs to | Ships as | Pick it when |
|---|---|---|---|---|---|
| Manual instructions | Steps a person follows | Illustrator's own | Nothing | A document | The task is rare, or needs judgment at every step |
| ExtendScript script | .jsx run in Illustrator |
Optional ScriptUI dialog | Presets/<locale>/Scripts or anywhere (File > Scripts > Other Script) |
.jsx file |
One action, batch work, or a step another tool calls |
| CEP extension | HTML panel plus ExtendScript host | Dockable panel | CEP extensions folder |
Signed .zxp |
Users need a persistent panel with controls and previews |
| C++ plug-in | Native .aip from the Illustrator SDK |
Tools, menus, notifiers, native dialogs | Plug-ins folder or the Additional Plug-ins Folder | .aip per OS and major version |
You need a custom tool, live effects, speed, or events scripts cannot reach |
| UXP plugin | Modern JavaScript plugin model | Panels and dialogs | Through Creative Cloud | .ccx |
Plan for it; Illustrator's public beta is due by Spring 2027 |
| MCP server | A process an AI tool calls, which runs scripts in Illustrator | The AI tool's chat | The AI tool's MCP config | A package or repo | An agent should create or inspect artwork through tools |
| OS automation | Batch, PowerShell, bash, or AppleScript that starts scripts | None | Anywhere | Script files | Illustrator work is one step of a larger pipeline |
Start with the lowest tier that meets the need. A script that works is the core of every higher tier: a CEP panel, an MCP tool, and an OS script all end up calling ExtendScript.
Extensibility Timeline
From Adobe's announcement "Investing in the future of Creative Cloud extensibility" (blog.developer.adobe.com, September 2026):
- Illustrator UXP plugins: public beta by Spring 2027.
- CEP in Illustrator, After Effects, and Media Encoder: the Adobe Marketplace stops accepting new CEP submissions in December 2028, and CEP is disabled by default from December 2028.
- CEP leaves these apps from December 2029, with at least two years between each app's UXP public beta and CEP's removal from new versions.
- ExtendScript is not affected by the transition.
So a CEP extension built today has a working life of a few years. Keep its logic in plain ExtendScript files the panel calls, which carry over to a UXP plugin or an MCP server unchanged.
Workflow
- Scope: what the user does, which Illustrator versions and OSes it must run on, and who installs it.
- Pick the tier from the table above.
- Write the ExtendScript core first with the adobe-illustrator-scripting skill, as functions that take a plain settings object and return a result string, so any front end can call them.
- Add the front end:
- CEP panel: references/cep-extensions.md (folder layout, manifest,
CSInterface, debug mode, signing, install) - C++ plug-in: references/cpp-plugins.md (SDK, build, PiPL, suites, notifiers, debugging)
- Command line, MCP server, or computer use: references/automation-and-mcp.md (COM, AppleScript, parameters, results, MCP design, safety)
- CEP panel: references/cep-extensions.md (folder layout, manifest,
- Test inside Illustrator on a copy of a real document: run every option, export a PNG of the result, and compare it with the expected output.
- Package: a signed ZXP for CEP, a per-OS
.aipfor plug-ins, a versioned folder or package for scripts and servers. - Document with references/publishing-docs.md: requirements, compatibility, install steps per OS, a walkthrough with screenshots, a GIF, troubleshooting, and a changelog.
Running a Script From Outside Illustrator
| Platform | Route | Notes |
|---|---|---|
| Windows | COM Illustrator.Application |
DoJavaScriptFile(JavaScriptFile, [Arguments], [ExecutionMode]) and DoJavaScript(JavaScriptCode, [Arguments], [ExecutionMode]); ExecutionMode 1 never shows the debugger |
| macOS | AppleScript do javascript |
do javascript "$.evalFile(new File(arguments[0]))" with arguments {scriptPath}, with the path passed to osascript as an argument so it never enters script source; check the exact app name for your version |
| Both | VS Code ExtendScript Debugger | Adobe's extension for running and debugging .jsx against a running app |
| Windows (legacy) | ExtendScript Toolkit -run |
32-bit, does not run on macOS 10.15 or later; keep only for old pipelines |
Pass parameters through a sidecar key=value file (no JSON parser or eval needed in ES3) and have the script write its result to a file, because arguments handling differs between launchers. The patterns are in references/automation-and-mcp.md.
Instructions People Follow by Hand
When the deliverable is a set of steps rather than code (for a complex graphic, or for an asset someone downloads):
- Name the Illustrator version the steps were checked on, and give menu paths exactly as they appear (
Object > Path > Offset Path). - One action per step, with the panel and the value to set (
Stroke panel: Weight 2 pt, Align Stroke to Inside). - Show the expected result after each group of steps, with a screenshot or a small PNG.
- Mark the steps that differ on Windows and macOS (shortcuts, file dialogs, font paths).
- Offer the scripted route next to the manual one when a script exists.
Guardrails
- Work on copies of user documents; never overwrite an original without a backup.
- Ask before writing into Adobe's install folders, the system CEP folder, or the registry.
- Development mode (
PlayerDebugMode) belongs on development machines only. Ship signed ZXPs to users. - Never commit signing certificates, certificate passwords, API keys, or tokens. Read secrets from environment variables.
- Prefer scripting, COM, or AppleScript over clicking through the UI; use computer use only for what has no scripting route.
- Never automate around sign-in, licensing, or account dialogs.
- Fonts from Adobe Fonts cannot be bundled in a plug-in or extension; document them as a requirement instead.
- Version-specific details (CEP version, SDK version, menu names) change; say which version you checked and point to Adobe's docs.
References
- references/cep-extensions.md: CEP panels from folder layout to signed ZXP
- references/cpp-plugins.md: C++ plug-ins with the Illustrator SDK
- references/automation-and-mcp.md: command-line runs, MCP servers, and computer use
- references/publishing-docs.md: install and usage docs for a published Illustrator tool
- Adobe CEP Resources (CEP 12 cookbook,
CSInterface.js, ZXPSignCMD): Adobe-CEP/CEP-Resources - Adobe CEP getting-started guides (packaging, signing, distribution): Adobe-CEP/Getting-Started-guides
- UXP and CEP timeline: Investing in the future of Creative Cloud extensibility
Files in this skill
5adobe-illustrator-integrations skill questions
How do I install the adobe-illustrator-integrations skill in Claude Code?
Run npx degit github/awesome-copilot/skills/adobe-illustrator-integrations ~/.claude/skills/adobe-illustrator-integrations. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the adobe-illustrator-integrations skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What is the difference between a script, an extension, and a plug-in in Illustrator?
A script is ExtendScript (.jsx) with optional ScriptUI; an extension is a CEP panel using HTML/JS; a plug-in is native code built with the C++ SDK.
What is the timeline for UXP plugins in Adobe Illustrator?
Illustrator's public beta for UXP plugins is expected by Spring 2027.