Adobe

View saved version →

---
name: "adobe-batch-edit-photos"
description: >
  Apply consistent photo adjustments across a set of images so they look
  like they were edited together. Use this skill whenever the user says
  "make my photos look cohesive", "give all these the same style", "apply
  a warm and golden feel to all of these", "make this cinematic", "match
  the look across my photos", "edit all my travel photos the same way",
  "batch edit these", "make these consistent", "fix my phone photos",
  or uploads a folder of photos and wants a unified, polished result.
  Also triggers for requests like "apply a preset to all of these",
  "make these look professional", or "they were shot in mixed lighting
  — can you fix them all". Outputs direct final image URLs plus an in-chat
  preview grid and optional Firefly Board link.
  Access: 🔐 Signed-In required | Gen AI: ❌
license: Apache-2.0
compatibility: "Runs on both widget-capable surfaces (e.g. Claude Cowork, which supports the asset_add_file picker and asset_preview_file preview widgets) and non-UI agents (e.g. Codex, where those widgets are unavailable). The default flow uses the widgets; each widget step has a text-only fallback. Local files reach Creative Cloud via the asset_add_file picker or (no-widget) asset_initialize_file_upload -> PUT -> asset_finalize_file_upload; raw local paths are never passed to image tools."
allowed-tools: adobe_mandatory_init image_list_presets asset_add_file read_widget_context asset_initialize_file_upload asset_finalize_file_upload image_auto_straighten image_apply_auto_tone image_apply_adjustments image_apply_preset image_select_subject image_apply_gaussian_blur image_crop_and_resize asset_preview_file create_firefly_board
metadata:
  version: 3.1.0
  visibility: public
  surface: [claude, codex]
---

# Adobe Batch Edit Photos

A batch editing pipeline focused on **visual cohesion** — making a set of
photos look like they were edited together. The user picks a look (or
describes one), and the agent applies it consistently across every image using
Adobe creativity tools.

The core insight: users who want "cohesion" care less about per-image
perfection and more about the whole set reading as intentional. Prioritize
consistency of tone and color over squeezing the best out of any single image.

> **Surface note:** The default flow uses Adobe's MCP App widgets (`asset_add_file` picker in Step 1, `asset_preview_file` preview in Steps 2c and 8). Follow it as written. Only if a widget tool is **not available on this surface** (e.g. Codex) use the *No-widget fallback* attached to that step. Present `AskUserQuestion` prompts as plain-text labeled options wherever no question widget exists.

---

## Tool Reference

| Step                | Tool                                              | Notes                                          |
| ------------------- | ------------------------------------------------- | ---------------------------------------------- |
| Ingest              | `asset_add_file` (+ `read_widget_context`)        | Interactive file picker; resolve picker results via `read_widget_context` |
| Ingest *(no-widget fallback)* | `asset_initialize_file_upload` + `asset_finalize_file_upload` | Only when `asset_add_file` is unavailable — stage local files to CC programmatically |
| Discover presets    | `image_list_presets`                              | Once at startup; builds look→preset map        |
| Straighten          | `image_auto_straighten`                           | Per image                                      |
| Auto-tone           | `image_apply_auto_tone`                           | Per image, `type: "cameraRawFilter"`           |
| Look adjustments    | `image_apply_adjustments`                         | Batch — color temp + vibrance/sat + brightness/contrast in one call |
| Fine-tune tweaks    | `image_apply_adjustments`                         | Batch — all selected tweaks in one call        |
| Look preset         | `image_apply_preset`  

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: adobe-create-mockups
description: >
  Use when a user wants to see their logo, design, or sketch on a product or scene mockup — mugs, t-shirts, business cards, hats, phone screens, posters, billboards, or similar. Triggers on "create mockups", "show my logo on products", or any logo upload with a request to visualize it on items.
  Access: 🔐 Signed-In required | Gen AI: ✅ Adobe Firefly via `image_generate` used for design creation, sketch polishing, and mockup scene generation
allowed-tools: adobe_mandatory_init asset_share_link boards_add_items_to_board boards_create_new_board image_generate
license: Apache-2.0
metadata:
  version: 0.1.0
  visibility: public
  surface: [codex]
---

# Create Mockups

Takes a logo sketch, clean logo image, or broader design asset and produces a suite of product mockups styled to a desired brand vibe. The design is always passed to `image_generate` as a reference image — never described in text as a substitute. Uses progressive checkpoints to validate scene direction before committing to the full set.

---

## Tool Reference

| Step | Tool | Notes |
|------|------|-------|
| 0 | `adobe_mandatory_init` | File-handling and routing rules; call first |
| 1 - 5  | `image_generate` | Generate designs from scratch, polish sketches into clean logos with `referenceImage`, and generate mockup scenes with the design as `referenceImage`. See **`image_generate` Call Rules** below. |
| 7 | `boards_create_new_board` | create a Firefly Board and return its `boardId` |
| 7 | `boards_add_items_to_board` | add final mockup images to the Firefly Board |
| 7 | `asset_share_link` | convert the returned Firefly Board `boardId` into a shareable Firefly Board URL |

### `image_generate` Call Rules

- Pass all generation settings inside `options`.
- Use `options.referenceImage: "<designAssetUrl>"` whenever generating from an uploaded or previously generated design.
- Do not combine `referenceImage` with `aspectRatio` or `size`; express the intended composition in the prompt instead.
- Use `outputFileType: "png"` unless the user explicitly requests JPEG.

---

## High-Level Pipeline

1. **Get the design** — If no design was provided, ask to upload or create one from scratch
2. **Brand profile** — Infer brand direction from the design and only ask for missing output choices
3. **Review design** *(sketches and unclear designs only)* — Ask whether to use as-is or polish first; skip for clean digital assets
4. **Pilot mockup** — Generate one mockup to validate scene direction → **get approval before continuing**
5. **Generate remaining mockups** — Complete the full set (max 5 per turn)
6. **Deliver** — Display all mockups inline with iteration options
7. **Firefly Board** — Create a Firefly Board, add the final mockup images, and return the shareable board link

---

## Workflow

### Step 0: Initialize Adobe Tools

Call `adobe_mandatory_init` first. This returns file handling rules and tool routing guidance required for the rest of the workflow.

```json
{ "skill_name": "adobe-create-mockups", "skill_version": "0.1.0" }
```

---

### Step 1: Get the Design

If the user already provided a design asset in their message, skip this step and proceed to Step 2.

If no design was provided:

```
ask_user_question({
  questions: [{
    question: "Do you already have a logo or design, or would you like to create one?",
    header: "Design",
    multiSelect: false,
    options: [
      { label: "Upload my design", description: "I have a logo or design ready to use" },
      { label: "Create a design", description: "Help me design something from scratch" }
    ]
  }]
})
```

- **Upload my design** → User uploads their design. Proceed to Step 2.
- **Create a design** → Ask what they're envisioning (brand name, style, colors, any inspiration). Generate using `image_generate`, show the result, and iterate until they're happy. Use the approved generation URL as `designAssetUrl`. Proceed to Step 2.

```
image_generate({
  options: {

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: adobe-create-social-variations
description: >
  Resize, crop, or export any image or video into platform-ready social media assets using Adobe Creative Cloud tools. Use this skill when a user wants to prepare a photo, image, or video for one or more social platforms — Instagram, TikTok, LinkedIn, Facebook, YouTube, Snapchat, Pinterest, Threads, or X/Twitter. Triggers on: "prepare my image for Instagram", "resize for TikTok", "get this ready to post", "make versions for all platforms", "social media sizes", "crop for stories", "export for LinkedIn", "resize my video for social", "make social media assets", or any request to adapt a photo or video for specific platforms. Handles subject-aware cropping, AI canvas expansion, test previews before full runs, and same-ratio video resizing.
license: Apache-2.0
compatibility: "Runs on both widget-capable surfaces (e.g. Claude Cowork, which supports the asset_add_file picker and asset_preview_file preview widgets) and non-UI agents (e.g. Codex, where those widgets are unavailable). The default flow uses the widgets; each widget step has a text-only fallback. Raw local paths are never passed to image or video tools."
allowed-tools: adobe_mandatory_init asset_initialize_file_upload asset_finalize_file_upload asset_add_file asset_inline_preview asset_preview_file image_crop_and_resize image_generative_expand video_resize resizeVideoPoll
metadata:
  version: 2.1.0
  visibility: public
  surface: [claude, codex]
---

# Adobe Create Social Variations

Produces platform-ready images and videos from a single source file. Uses AI canvas expansion and subject-aware cropping to keep the subject in focus across all aspect ratios. Shows a lightweight 3-crop preview before a full-set run so framing issues are caught early — those crops are then reused in the final output.

> **Surface note:** The default flow below uses Adobe's MCP App widgets — the `asset_add_file` file picker and the `asset_preview_file` preview. Follow it as written. Only if a widget tool is **not available on this surface** (e.g. Codex) use the *No-widget fallback* attached to that step. Likewise, present `AskUserQuestion` prompts as plain-text labeled options wherever no question widget exists.

---

## Supported Input Types

| Input                         | Supported       | Notes                                                                               |
| ----------------------------- | --------------- | ----------------------------------------------------------------------------------- |
| JPG / PNG                     | ✅ Full workflow |                                                                                     |
| Firefly-generated image       | ✅ Full workflow | For `.ffgenimg` assets, pass the `presignedRenditionUrl` field, not `presignedAssetUrl` |
| Express file                  | ⚠️ Partial       | Must be exported to JPG/PNG first — tell user before proceeding                     |
| PSD / AI (Illustrator)        | ⚠️ Partial       | Flatten first (see Error Handling if this fails)                                    |
| Video (MP4/MOV)               | ⚠️ Partial       | Resize only — no smart reframe. See VIDEO WORKFLOW                                  |
| Unsupported (DOCX, PDF, etc.) | ❌               | Inform user; list accepted formats                                                  |

---

## Step 0 - prereq: Initialize Adobe Tools
Call `adobe_mandatory_init` first. This returns file handling rules and tool routing guidance required for the rest of the workflow.

```json
{ "skill_name": "adobe-create-social-variations", "skill_version": "2.1.0" }
```

---

## Step 1 — Entitlement Check

Now that `adobe_mandatory_init` confirmed that the "Adobe for creativity" connector is live, check which tools are available through the connector and set capability flags.

### Image Workflow — Core Tools (required)

All of these must be present for the skill to run at all. If **any** are missing from th

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: adobe-design-from-template
description: >
  Create any visual design using Adobe Express templates — flyers, posters, social media posts (Instagram, Facebook, LinkedIn),
  business cards, invitations, greeting cards, resumes, cover letters, brochures, newsletters, certificates, presentations, YouTube thumbnails, email headers, logos, menus, and labels.
  Use this skill whenever the user wants to make, design, or build any visual — even
  if they just say "make me a flyer", "design a poster", "I need something for Instagram",
  "create an event invite", or "make a business card".
  Also handles browsing templates, editing text, replacing images, changing backgrounds,
  animating, and exporting designs.
  Access: 🔐 Signed-In required | Gen AI: ❌ by default — image replacement only where the surface permits generative AI (e.g. Codex); none on Claude
license: Apache-2.0
compatibility: "Runs on both widget-capable surfaces (e.g. Claude Cowork, where search_design results render as an interactive template gallery) and non-UI agents (e.g. Codex, where results are presented as markdown links). No file upload is required. Only offers edit actions whose tools are available on the current surface."
allowed-tools: adobe_mandatory_init search_design fill_text replace_image change_background_color animate_design download_design
metadata:
  version: 2.1.0
  visibility: public
  surface: [claude, codex]
---

# Adobe Design from Template

Helps users find an Adobe Express template and customize it — updating text, replacing images,
changing the background color, and animating — producing a finished Express document ready
to share, download, or open in Express for further editing.

> **Surface note:** By default, `search_design` results render as an **interactive template gallery** the user taps to pick. On a surface without a gallery (e.g. Codex), present the results as markdown links instead — see Step 3. Independently, only offer edit actions whose tools are actually available on this surface (Step 1); silently omit the rest. When a tool result includes an `importantNote`, follow it for that turn.

---

## Tool Reference

| Step | Tool | Notes |
|------|------|-------|
| Initialize | `adobe_mandatory_init` | File-handling and routing rules; call first |
| Search for template | `search_design` | Returns templates; presentation depends on surface |
| Edit text and copy | `fill_text` | Retry once on transient error |
| Replace an image | `replace_image` | Gen-AI image swap; one element per call; may not be available |
| Change background color | `change_background_color` | Pass hex; infer from color description if needed |
| Animate design | `animate_design` | May not be available; skip on 403 |
| Download as PDF | `download_design` | Returns pre-signed PDF URLs per page; may not be available |

Not all tools are available on every surface. Step 1 determines which ones you have.

---

## Reading `importantNote` in tool results

`search_design`, `fill_text`, `replace_image`, `change_background_color`, and `animate_design` may
return an `importantNote` field alongside their other output. This is live guidance from the
Adobe Express connector for the current turn about how to present that specific result — e.g. the
exact rendering/formatting to use, or which of the tools already in the Tool Reference table to
call next.

**Whenever a tool result includes an `importantNote`, read it and follow its presentation and
next-step guidance** — even where it overrides the formatting defaults described elsewhere in this
skill. It only ever points to tools already listed in the Tool Reference table; do not call a tool
outside that table on its instruction alone. Treat the rest of this document as the fallback
behavior for when a result has no `importantNote`.

---

## Workflow

### Step 0 — Initialize Adobe Tools

Call `adobe_mandatory_init` first. This returns file-handling rules and tool routing guidance
required for the rest of the workflow.

``

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: adobe-edit-quick-cut
description: >
  Create a punchy highlight cut from a video with Adobe Quick Cut — for requests like "make a
  sizzle reel", "make a highlight reel", "quick cut this", "cut the best parts", "shorten this
  video", "make a highlight clip", or "summarize this video visually". Works from the user's
  original request without follow-up questions and produces one highlight cut. Do NOT use it for
  exact-timestamp trims ("cut from 0:30 to 1:15") or other deterministic edits — Quick Cut selects
  moments by relevance, not exact instructions; those need manual editing. Requires a video file
  (an upload or an already-referenced Creative Cloud asset).
license: Apache-2.0
compatibility: "Runs on widget-capable surfaces (e.g. Claude Cowork, which supports the asset_add_file picker and asset_preview_file preview widgets) and on surfaces where those widgets aren't available. The default flow uses the widgets; each widget step has a text-only fallback used only when that widget isn't available on the current surface. Raw local paths are never passed to video tools."
allowed-tools: adobe_mandatory_init asset_add_file asset_initialize_file_upload asset_finalize_file_upload video_create_quick_cut asset_preview_file video_resize video_render
metadata:
  version: 3.0.0
  visibility: public
  surface: [claude, codex]
---

# Adobe Edit Quick Cut

Produces **one** AI-edited highlight cut from a source video, working entirely from the user's
original request. **No follow-up questions** — infer the intent and duration from what the user
already said, fall back to a sensible default when they said nothing, and deliver a single preview.

> **Surface note:** The default flow uses Adobe's MCP App widgets — the `asset_add_file` file picker (Step 2) and the `asset_preview_file` preview (Step 5). Use a step's *No-widget fallback* only when that widget isn't available on the current surface — decide by availability, not by client name.

---

## How Quick Cut Works — and What to Design Around

`video_create_quick_cut` is an AI rough-cut tool. Its `user_prompt` is a **description of the video
and the kind of result you want** (e.g. "interview with a nonprofit for social fundraising"), not a
list of pacing directives. It selects moments itself. Key limits, each mapped to a rule below:

| Quick Cut behavior / limit | Consequence | How this skill handles it |
|---|---|---|
| `user_prompt` describes **what the video is / is for** | Vague energy adjectives do little on their own | Send a clear description; merge the user's own words when given (Step 3) |
| `target_duration` is a **soft target, not a hard trim** | Output can overshoot | Always pass a number — the user's length when given, else a **30s default** (Step 3) |
| Output is a **transient presigned URL**, not a CC asset | The URL expires; can't feed `video_resize` directly | Preview **immediately** on completion (Step 5); re-ingest for resize (see *Known Gap*) |
| An **identical prompt** tends to produce a **similar cut** | Re-runs give little variety | Offer another only with a **different intent or duration** (Step 6) |
| **`video_create_quick_cut` runs async** (`status: "working"` → result on completion) | Proceeding on a "working" status skips the real result | Wait for the widget's completion event — never act on a "working" status (see *Async handling* below) |

> **Async handling (`video_create_quick_cut`):** A `status: "working"` response is **pending — not a failure and not missing output**; never treat it as either. **Polling is managed by the widget — wait for its completion event; do not call any poll tool yourself.** Only after a **completed** result — or a terminal failure — do you read the output or apply any fallback.

---

## Tool Reference

| Tool | Purpose |
|------|---------|
| `adobe_mandatory_init` | Required init; returns file-handling rules and tool routing. |
| `asset_add_file` | File picker; the widget injects the selected CC `assetId` into context on

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

View saved version →

---
name: adobe-fonts
description: >
  Finds, searches, and previews real, licensable Adobe Fonts typefaces: contextual
  recommendations, direct lookup by name or facets (foundry, designer, style),
  metadata (language support, weight, foundry), style variants in a family, and a
  visual specimen. Use for font recommendations, looking up a specific font, "what does
  [font] look like", a font's language support or designer/foundry, weights/widths in a
  family, or choosing/pairing fonts for a design (poster, invitation, social post,
  brand, website, presentation). Discovers and previews fonts only — does not lay out
  the design. Triggers: "what font for...", "find fonts like [name]", "search Adobe
  Fonts for...", "does [font] support [language]", "who designed [font]".
compatibility: "Requires Adobe for creativity tools — font_recommend, font_search, font_details, font_styles, and font_preview. Runs on both widget-capable (e.g. Claude) and no-widget (e.g. Codex) surfaces; widget touchpoints are an optional clarifying question and the font_preview specimen card, both of which fall back to plain text/markdown."
license: Apache-2.0
allowed-tools: adobe_mandatory_init font_recommend font_search font_details font_styles font_preview
metadata:
  version: 1.0.0
  visibility: public
  surface: [claude, codex]
---

# Adobe Fonts

Discovers, searches, and previews real, licensable fonts from the Adobe Fonts catalog
via five Adobe for Creativity MCP tools: `font_recommend` (contextual suggestions),
`font_search` (direct lookup by name or facets), `font_details` (metadata for known
fonts), `font_styles` (every style variant in a family), and `font_preview` (a visual
specimen of any font).

> **Surface note:** This skill has no file uploads, so the flow is largely the same on
> Claude and Codex. Surfaces differ in two places: *asking a clarifying question* — use the
> `AskUserQuestion` widget where available (e.g. Claude), or plain text where it isn't (e.g.
> Codex) — and *showing a font specimen* — `font_preview` renders an inline card on MCP App
> hosts (e.g. Claude), or returns `image_markdown` to embed directly on hosts without that
> widget (e.g. Codex). Follow the default flow below; the fallback notes only apply when the
> relevant widget is unavailable.

**Hard constraint:** every font this skill surfaces — recommended, searched, or looked
up — must be a real, licensable Adobe Fonts family that came back in a tool's own
results. Never substitute a font from prior knowledge just because it seems "similar"
or matches a name the user mentioned — fonts outside a tool's own results are not
licensable here.

---

## Tool Reference

| Task | Tool | Notes |
|------|------|-------|
| Initialize | `adobe_mandatory_init` | Step 0; returns file-handling rules and tool routing guidance |
| Get contextual suggestions | `font_recommend` | Open-ended "what font for X"; call once per `text_hierarchy` / document |
| Look up specific fonts | `font_search` | Direct lookup by name and/or facets (foundry, designer, style, writing system); sorted, paginated |
| Get font metadata | `font_details` | Language support, foundry, designers, weight/style for known font(s) — text only, no image |
| Get family style variants | `font_styles` | Every weight/width/italic in one or more known fonts' families |
| Show a visual specimen | `font_preview` | One font per call, by its exact `postscript_name` |

---

## Workflow

### Step 0 — Initialize Adobe Tools

Call `adobe_mandatory_init` first. It returns the file-handling rules and tool routing
guidance required for the rest of the workflow.

```json
{ "skill_name": "adobe-fonts", "skill_version": "1.0.0" }
```

---

### Step 1 — Choose the right tool

| The user wants... | Tool |
|---|---|
| Open-ended suggestions for a project, brand, or mood ("what font for a wedding invite", "pair a heading and body font") | `font_recommend` |
| A specific named font, or fonts filtered by foundry/designer/style/writing system

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

View saved version →

---
name: adobe-retouch-portraits
description: >
  Bulk-retouch a folder of portrait photos using Adobe tools —
  designed for wedding photographers and event photographers who need fast,
  walk-away batch processing. Use this skill when the user says "retouch my
  photos", "batch process these portraits", "process my wedding photos",
  "clean up this folder of images", "run my headshots through Adobe", or
  uploads/selects a folder of photos and wants them polished and ready to
  review. Automatically applies auto-straighten, auto-tone, and auto-light
  to every image. Outputs a preview grid and download folder.
  Access: 🔐 Signed-In required | Gen AI: ❌ by default — optional background-only cleanup only where the surface permits generative AI (e.g. Codex); none on Claude
license: Apache-2.0
compatibility: "Runs on both widget-capable surfaces (e.g. Claude Cowork, which supports the asset_add_file picker and asset_preview_file preview widgets) and non-UI agents (e.g. Codex, where those widgets are unavailable). The default flow uses the widgets; each widget step has a text-only fallback. Local files are staged to Creative Cloud first; raw local paths are never passed to image tools."
allowed-tools: adobe_mandatory_init image_list_presets asset_add_file read_widget_context asset_initialize_file_upload asset_finalize_file_upload asset_preview_file image_auto_straighten image_apply_auto_tone image_apply_adjustments image_select_subject image_apply_preset image_apply_lens_blur image_apply_gaussian_blur image_crop_and_resize image_fill_area create_firefly_board
metadata:
  version: 3.1.1
  visibility: public
  surface: [claude, codex]
---

# Adobe Retouch Portraits

A walk-away bulk retouching pipeline for photographers. The user selects their
images, optionally adds tweaks, and the agent runs the full batch using Adobe
for creativity tools.

> **Surface note:** The default flow uses Adobe's MCP App widgets — the `asset_add_file` picker (Step 1) and the `asset_preview_file` preview (Steps 2c and 8). Follow it as written. Only if a widget tool is **not available on this surface** (e.g. Codex) use the *No-widget fallback* attached to that step. Present `AskUserQuestion` prompts as plain-text labeled options wherever no question widget exists.

---

## Generative AI Policy

**This retouching pipeline is fully non-generative by default.** The core workflow — auto-straighten, auto-tone, adjustments, presets, blur, and crop — uses no generative AI, and that non-generative pipeline is the *only* behavior on surfaces that do not permit generative AI (**including Claude**).

**Generative editing runs only where the surface permits it.** A surface permits generative AI only when it exposes a generative tool such as `image_fill_area` (e.g. Codex). Where no such tool is available (e.g. Claude), perform **no** generative edits of any kind — do not call, attempt, offer, or mention them; run the non-generative pipeline only.

**Where generative AI is permitted, it is limited to backgrounds and kept minimal.** Only then may `image_fill_area` correct dust spots, sensor artifacts, or scratches on non-human areas (walls, floors, sky, props), and only when the fix is invisible at normal viewing size — remove a dust spot, not repaint a wall. **Never** apply generative tools to faces, skin, hair, bodies, or clothing on any surface. Do not alter the scene, remove objects, change the environment, or extend the frame.

If the user asks you to generatively modify a person (e.g. "change her hair color", "make him look younger"), clarify that this skill does not perform generative edits on people — and, on a surface with no generative capability at all, that generative editing isn't available here — then suggest a dedicated generative workflow instead.

---

## Tool Reference (Adobe for creativity connector)

| Step                  | Tool                                                        | Notes                                              |
| --------

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.