CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adobe-illustrator-integrations

Build, debug, package, and document Adobe Illustrator integrations: CEP extension panels, C++ SDK plug-ins (.aip), the coming UXP plugins, MCP servers that drive Illustrator, computer-use automation, and OS scripts (batch, PowerShell, bash, AppleScript) that run ExtendScript in Illustrator. Use when creating or fixing an Illustrator extension or plug-in, choosing between a script, extension, or plug-in, connecting an AI tool to Illustrator, automating Illustrator from the command line, or writing install and usage docs for an Illustrator tool someone will publish. Pairs with adobe-illustrator-scripting for the ExtendScript DOM.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered overview: dense tables, copy-paste-ready automation specifics, a sequenced workflow with an explicit test checkpoint, and clean routing to four real one-level-deep reference files. The minor deductions are the date-heavy timeline section (which will age) and the lack of an explicit test-failure feedback loop in the workflow.

Suggestions

Add a short feedback loop to the Workflow's test step, e.g., 'if the exported PNG does not match the expected output, fix the script and re-test before packaging', to reach full workflow clarity.

Move the specific UXP/CEP dates (December 2028, December 2029, Spring 2027) into a compact 'Timeline / deprecation' note or into the relevant reference files, keeping the body's guidance stable as dates pass.

DimensionReasoningScore

Conciseness

The body is dense and information-forward: two comparison tables, a workflow list, and terse guardrails, with no padding and no explanation of concepts Claude already knows (the 'Adobe's own terms' definitions are Illustrator-specific CEP/.aip/UXP terminology, not generic). It falls short of the lean-everywhere anchor because the Extensibility Timeline section carries specific dates ("December 2028", "December 2029", "Spring 2027") and a cited blog post that will age, and a few sentences (e.g., the table preamble) could be trimmed further.

4 / 5

Actionability

The guidance is copy-paste ready: exact COM calls "DoJavaScriptFile(JavaScriptFile, [Arguments], [ExecutionMode])" with the note that "ExecutionMode 1 never shows the debugger", the exact AppleScript pattern "do javascript \"$.evalFile(new File(arguments[0]))\" with arguments {scriptPath}" with the injection-safe argument-passing note, concrete paths like "Presets/<locale>/Scripts" and "PlayerDebugMode", and even exact menu-path formatting rules ("Object > Path > Offset Path"). These cover the common cases the body itself handles, with per-topic detail correctly pushed to the reference files.

5 / 5

Workflow Clarity

The 7-step Workflow is clearly sequenced (Scope, Pick the tier, Write the ExtendScript core, Add the front end, Test, Package, Document) and step 5 is an explicit validation checkpoint ("run every option, export a PNG of the result, and compare it with the expected output"), supported by safety guardrails ("Work on copies of user documents"). It stops short of anchor 5 because there is no error-recovery feedback loop (what to do when the test comparison fails) and no checklist for the packaging step.

4 / 5

Progressive Disclosure

The body is a genuine overview (~100 lines) that routes each topic to a real, clearly signaled, one-level-deep reference file with inline scope annotations — "CEP panel: references/cep-extensions.md (folder layout, manifest, CSInterface, debug mode, signing, install)" — and a References section listing all four bundle files (all present and substantive, 64-255 lines) with one-line descriptions. Cross-links inside the references are lateral peer pointers (e.g., cpp-plugins.md pointing to publishing-docs.md), not nested chains, so navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names concrete capabilities across every integration tier, includes an explicit 'Use when' clause with natural trigger phrases, and explicitly delimits its scope against the companion scripting skill. The only gap is a handful of missing natural synonyms such as .jsx or 'panel' as trigger words.

DimensionReasoningScore

Specificity

The description opens with four concrete verbs ("Build, debug, package, and document") and enumerates the full range of integration types with named technologies and file formats: "CEP extension panels, C++ SDK plug-ins (.aip), the coming UXP plugins, MCP servers that drive Illustrator, computer-use automation, and OS scripts (batch, PowerShell, bash, AppleScript)". This is comprehensive, concrete coverage of the domain, matching the anchor for multiple specific concrete actions with comprehensive coverage rather than the 'several actions, minor gaps' anchor below.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is "Build, debug, package, and document Adobe Illustrator integrations: CEP extension panels, C++ SDK plug-ins (.aip)..." and the 'when' is a dedicated clause with concrete triggers ("Use when creating or fixing an Illustrator extension or plug-in, choosing between a script, extension, or plug-in, connecting an AI tool to Illustrator..."). It additionally names its companion skill ("Pairs with adobe-illustrator-scripting for the ExtendScript DOM"), which is a clear bonus beyond the anchor-5 example.

5 / 5

Trigger Term Quality

The 'Use when' clause contains natural phrasings users would actually say: "creating or fixing an Illustrator extension or plug-in", "connecting an AI tool to Illustrator", "automating Illustrator from the command line", "writing install and usage docs". A few natural trigger terms are absent (e.g., ".jsx", "panel", "scripting" as a standalone word), which places it at good-but-not-comprehensive coverage rather than the comprehensive synonyms-and-extensions anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly staked: everything around Illustrator integrations (panels, plug-ins, MCP servers, OS automation, docs), with an explicit boundary against the sibling DOM-scripting skill ("Pairs with adobe-illustrator-scripting for the ExtendScript DOM"). Triggers like "Illustrator extension or plug-in" and "connecting an AI tool to Illustrator" are unlikely to fire for an unrelated skill, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

github/awesome-copilot

Path

skills/adobe-illustrator-integrations/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.