Adobe Design From Template
OpenAIOfficialCreated by Adobe IncDistributed by OpenAI
- Skill
- Tool integration
- Design and creative
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill enables users to create various visual assets such as flyers, social media posts, and presentations by leveraging Adobe Express templates. It guides the user through a structured workflow: searching for a template, applying edits like text updates, image replacement, background color changes, and animation, and finally exporting the result as a PDF or opening it in the Adobe Express editor.
What it does
- Searches for Adobe Express templates based on user-provided design types.
- Updates text content within selected templates.
- Replaces visual elements using generative AI image swapping.
- Modifies background colors using hex codes.
- Applies animation presets to designs.
- Exports finished designs as PDF files or provides direct links to the Adobe Express editor.
When to use it
- When you need to create a visual asset like a poster, business card, or social media post.
- When you want to customize an existing template with specific text or imagery.
- When you need to generate multiple design variations with different background colors.
- When you require a downloadable PDF version of a customized design.
Advantages
- Streamlines the design process by using pre-built templates.
- Allows for iterative editing by threading document updates.
- Provides flexibility to choose between different design variations.
- Supports both interactive gallery interfaces and text-based link navigation.
Usage examples
- “Make me a flyer for an ice cream social.”
- The agent searches for 'ice cream social flyer' templates and presents a selection for you to choose from before proceeding to edits.
- “I need something for Instagram.”
- The agent displays a variety of Instagram post templates and waits for your selection to begin customization.
- “Change the background of this design to coral pink.”
- The agent applies the requested color change to your selected design and presents the updated variations.
- “Replace the dog in this image with a cat.”
- The agent uses generative AI to swap the specified image element and provides the updated document link.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/adobe-design-from-template/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip adobe-design-from-template.zip -d .agents/skills
Documentation by Adobe Inc
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_designresults 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 animportantNote, 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.
{ "skill_name": "adobe-design-from-template", "skill_version": "2.1.0" }Step 1 — Check available tools
After adobe_mandatory_init confirms the "Adobe for creativity" connector is live, check which
tools from the Tool Reference table are actually available on this surface. Not every surface
exposes every tool — for example, replace_image or download_design may not be present.
Record which tools you have. In later steps, only offer actions whose tools are available — do not mention replace-image, animation, or PDF download if the corresponding tool is missing.
Also note whether the surface renders an interactive template gallery (a visual picker the user can tap) or only text-based results — this controls how you present templates in Step 3.
Step 2 — Build the search query (don't ask questions first)
Extract the design type from whatever the user said and go straight to Step 3. Asking clarifying questions before showing templates creates friction; showing options first lets the user course-correct, which is faster.
Keep the query generic — the design type only. Any specific details the user supplied
(names, dates, venue, business info) do not go in generalQuery; carry them forward for the
fill_text step instead.
| User says | generalQuery |
|---|---|
| "make me a flyer" | "flyer" |
| "I need something for Instagram" | "Instagram post" |
| "design a poster for my event" | "event poster" |
| "make a business card" | "business card" |
| "flyer for an ice cream social" | "ice cream social flyer" |
Step 3 — Search for a template
Call search_design:
{
"generalQuery": "<design type from user prompt>",
"pageSize": 24,
"fillDescription": "<any specific text the user gave, verbatim — or omit>"
}Check the result's importantNote first — it specifies exactly how to render the templates and
next-step actions for this turn; follow it. Absent an importantNote, present the results based on
the surface:
Interactive gallery (default): The search renders a visual picker in the chat. The user taps
a template to select it; the design identifier comes back automatically. Use pageSize: 24 to fill the
gallery.
No-gallery fallback (text-only surfaces, e.g. Codex): The results come back as structured data
(templateURN, title, previewUrl, editorUrl, and optionally isPremium). Render all URLs
as markdown hyperlinks — never show raw URLs. Use pageSize: 10 to keep the list scannable. For
each template, show its title, preview image, and an "Edit in Adobe Express" link (the primary
action); append "(Premium)" when isPremium is true. Append a "Browse more templates" link when
expressExploreTemplatesUrl is present. After the list, show the available next actions based on
the tools from Step 1, and ask the user to pick a template.
Always present the full template list and wait for the user to choose. Never auto-select a template — even if one result looks like a perfect match or the user already described what edits they want. The user must explicitly pick by number, title, or URN before you proceed. Describing desired edits (e.g. "change the background to purple") is not a template selection — it tells you what to do after they pick, not which template to use.
Resolve their choice to a templateURN.
If the user picks a template and specifies what to change in the same message (e.g. "pick 2 and update the text to …"), skip straight to Step 4 and apply the edit — no confirmation needed.
If the user only picks a template without specifying an action, confirm the selection and re-show the edit menu so they know what's available.
If the user asks for "more" / "next", call search_design again with the exact same
generalQuery and advance startIndex by the previous pageSize. Do not reword the query.
Step 4 — Apply edits
Note: The
templateURN(or design identifier from the picker) is what identifies the design. Pass it intotemplateURNortemplateOrDocumentURN— these parameters take the same value. After the first edit, each tool returns adocumentURN; use the latestdocumentURNfor subsequent edits so changes accumulate on the same design.
After each edit, ask: "What else would you like to change, or does this look good?"
Edit text / copy
Call fill_text:
{
"templateURN": "<templateURN or latest documentURN>",
"description": "<what to change and what to change it to>",
"generalQuery": "<same, minus any PII>"
}If the user hasn't specified what the text should say, ask before calling.
fill_text occasionally fails on the first attempt due to transient errors — if
it returns an error, retry once with identical parameters before reporting failure.
Replace an image
Generative capability — runs only where the surface permits generative AI (i.e. replace_image is available, e.g. Codex). If replace_image is unavailable, omit it from unsolicited action menus. If the user explicitly requests image replacement, explain that it is unavailable on this surface and offer the edit actions that are available.
Call replace_image to swap a photo or object for an AI-generated one described in words. Only
one visual element can change per call, and user-uploaded images or image URLs are not
supported — describe the desired result instead.
{
"templateOrDocumentURN": "<templateURN or latest documentURN>",
"description": "<what to replace and what it should become, e.g. 'replace the dog with a cheerful Labrador'>",
"generalQuery": "<same as description, with PII removed>"
}The more specific the description (subject, setting, mood, lighting, style), the better the
result. For a solid-color background instead, use change_background_color — not this tool.
Change background color
Call change_background_color:
{
"templateOrDocumentURN": "<templateURN or latest documentURN>",
"backgroundColor": "<hex, e.g. #FF6F61>",
"description": "<e.g. change background to coral pink>",
"generalQuery": "<same, minus any PII>"
}If the user describes a color without a hex (e.g. "coral pink"), pick a reasonable hex value using your judgment.
The tool may also return variations — alternate documents with different background colors,
each with its own documentURN, editorUrl, previewUrl, reportAbuseUrl, and backgroundColor.
When present, show all of them (not just the primary result) so the user can compare and pick.
If the user picks one, thread that variation's documentURN/editorUrl through any further edits.
Animate
Skip this section if animate_design is not available.
Call animate_design:
{
"templateOrDocumentURN": "<templateURN or latest documentURN>",
"description": "<animation style or intent>",
"generalQuery": "<same, minus any PII>"
}Do not ask the user anything for this step — call animate_design directly using their stated
intent (or a sensible default animation if they didn't specify one).
Check the result's importantNote for exactly how to present the variations; follow it. Absent
an importantNote:
Interactive surface (default): The result renders inline; the user can preview directly.
Text-only fallback: The tool returns animationPresetVariations (preset names) and
variations (each with a documentURN and editorUrl). Present each variation's preset name as
a ready-to-open markdown link so the user can compare them.
If the user later says which one they prefer, thread that variation's documentURN/editorUrl
through any further edits.
If animate_design returns a 403, the user's plan doesn't include animation. Skip it and note
in the delivery. Retrying does not resolve a 403 entitlement.
Step 5 — Download the finished design
Skip this step if download_design is not available or if the design has been animated.
download_design exports a static PDF — it does not preserve animation. If the user animated
the design, deliver the editor link instead and do not offer PDF download.
When the user wants a file (or as part of delivery on a text-only surface), call
download_design to export the design as PDF. It returns pre-signed download URLs — one per
page.
{
"documentUrn": "<latest documentURN — note: this parameter uses camelCase>",
"format": "application/pdf",
"pages": "1",
"originatingTool": "<last edit tool used, e.g. fill_text, replace_image, change_background_color>"
}Set pages to a comma-separated list/range (e.g. "1,3-5") for multi-page designs; omit it to
default to page 1. Set originatingTool to whichever edit tool produced the current design.
Present each returned downloadUrl as a plain markdown link.
Step 6 — Deliver
When the user is satisfied:
✅ Here's your finished design:
🎨 Template: [name]
[Edits applied, e.g. ✏️ Copy updated · 🖼️ Image replaced · 🎨 Background changed · ✨ Animated]
📎 Open in Express: [editor link]
⬇️ Download PDF: [downloadUrl(s)] ← only if download_design was usedUse the editorUrl (or editorShortUrl) from the last edit tool's response for the edit link,
and the downloadUrl(s) from download_design for the PDF (if available).
Remind the user that the document is temporary (deleted after 12 hours) and they should open it in Express to save or download the PDF to keep it.
Error handling
| Situation | Action |
|---|---|
fill_text fails on first attempt | Retry once with identical parameters |
replace_image returns 403 | Image replacement isn't on the user's plan; skip and note it, keep the rest of the design |
animate_design returns 403 | Animation isn't on the user's plan; skip and note it in delivery |
download_design reports failed pages | Deliver the pages that succeeded and the editor link; note which pages couldn't be exported |
| Any tool returns 401 | Ask the user to re-authenticate via Adobe OAuth, then retry |
| No templates match query | Try a broader generalQuery |
| User hasn't selected a template yet | Do not advance past Step 3 until a templateURN is resolved; it is required for every subsequent call |
| User skips all edits | Fine — deliver the template link (and PDF, if available/requested) as-is |
| Tool not available on surface | Silently omit that option — do not mention unavailable capabilities to the user |
Constraints
The workflow always begins with a template search before any edits.
Never auto-select a template. Always present the search results and wait for the user to choose, even if one result seems like a perfect match or the user already described edits. Skipping template presentation breaks the workflow.
Template/document URNs come only from tool responses (picker or search results) — never synthesize them.
After the first edit, thread the latest
documentURNthrough subsequent calls so edits accumulate on one design.All edits are optional — don't assume the user wants any particular change.
Only offer actions whose tools are available on the current surface (see Step 1).
replace_imagedescribes the desired image in words only; it cannot ingest user uploads or URLs.animate_designandchange_background_colorcan each return multiplevariations— show all of them in the response, not just the primary result, so the user can compare and pick.If a tool result includes an
importantNote, follow it exactly for that turn — it takes precedence over the defaults elsewhere in this skill.
Files
- ATTRIBUTION.mdAdded by AutoGineer1.0 KiB
- LICENSEAdded by AutoGineer10.0 KiB
- SKILL.md16.2 KiB
- agents/openai.yaml206 B
- assets/icon-large.svg488 B
- assets/icon-small.svg488 B
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: OpenAI Codex
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools
The author says: 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.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Adobe Inc
- Publisher
- OpenAI (Official)
- Distributed by
- OpenAI
- Source
- openai/plugins · plugins/adobe/skills/adobe-design-from-template · commit d420d13
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (written by AutoGineer)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Adobe Inc or OpenAI.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download adobe-design-from-template.zip