Sanity Migration
sanity-io/agent-toolkit
Plans, implements, and reviews migrations from other CMSes and content systems into Sanity.
Design and create AEM Workflow models on AEM as a Cloud Service.
Apache-2.0Auto-check passed
Install Workflow Model Design
$ npx skills add adobe/skills --skill workflow-model-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install adobe/skills workflow-model-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .claude/skills/workflow-model-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .claude/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add adobe/skills --skill workflow-model-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install adobe/skills workflow-model-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .agents/skills/workflow-model-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .agents/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/skills --skill workflow-model-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install adobe/skills workflow-model-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .cursor/skills/workflow-model-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .cursor/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/adobe/skills.git --path plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add adobe/skills --skill workflow-model-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install adobe/skills workflow-model-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .gemini/skills/workflow-model-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .gemini/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install adobe/skills workflow-model-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add adobe/skills --skill workflow-model-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .github/skills/workflow-model-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .github/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add adobe/skills --skill workflow-model-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install adobe/skills workflow-model-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/adobe/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design .opencode/skills/workflow-model-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "workflow-model-design" agent skill from https://github.com/adobe/skills/tree/main/plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design into .opencode/skills/workflow-model-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow-model-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
workflow-model-design- GitHub stars
- 195
- Token cost
- ~1.7k tokens
- SKILL.md length
- 608 words
- Files
- 10 (incl. references)
- Skills in repo
- 105
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Design and create AEM Workflow models on AEM as a Cloud Service.
- Works in 5 steps: Place model XML at:… → Add to ui.content package with… → Deploy via Cloud Manager pipeline → …
- Creating workflow models via the Workflow Model Editor
- SKILL.md covers Audience, Variant Scope, Dependencies and Workflow, plus 5 more sections
- Calls mvn
What it does
Workflow Model Design is an agent skill from adobe/skills. Design and create AEM Workflow models on AEM as a Cloud Service. Use when creating workflow models via the Workflow Model Editor or content package XML, defining step types (PROCESS, PARTICIPANT, DYNAMICPARTICIPANT, ORSPLIT, ANDSPLIT), configuring step properties, declaring workflow variables, and deploying models through the Cloud Manager pipeline.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/workflow-foundation/README.md`, `references/workflow-foundation/api-reference.md` and `references/workflow-foundation/architecture-overview.md`).
It works with Adobe Experience Manager. The repository describes itself as: Adobe Skills for Agents. The licence is Apache-2.0.
When your agent uses it
- Creating workflow models via the Workflow Model Editor
- Content package XML
- Defining step types (PROCESS
- DYNAMICPARTICIPANT
Example prompts
- “/workflow-model-design”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Place model XML at: conf/global/settings/workflow/models//.content.xml (the flow/parsys design-time format — not jcr:content/model/)
- Add to ui.content package with filter.xml entry mode="merge"
- Deploy via Cloud Manager pipeline
- Open Tools → Workflow → Models → select model → Edit → Sync
- Verify the model appears in /var/workflow/models/ via CRX/DE and all steps render on the canvas
What it can do on your machine
Read from SKILL.md and the folder at commit cbc9952. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Workflow Model Design loads about 1.7k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 608 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from adobe/skills at commit cbc9952, republished under its Apache-2.0 licence (© adobe). 608 words, ~1,734 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow-model-design/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- workflow-model-design
- description
- Design and create AEM Workflow models on AEM as a Cloud Service. Use when creating workflow models via the Workflow Model Editor or content package XML, defining step types (PROCESS, PARTICIPANT, DYNAMIC_PARTICIPANT, OR_SPLIT, AND_SPLIT), configuring step properties, declaring workflow variables, and deploying models through the Cloud Manager pipeline.
- license
- Apache-2.0
Workflow Model Design (Cloud Service)
Design workflow models for AEM as a Cloud Service: step structure, transitions, OR/AND splits, variables, and model XML deployment.
Audience
Developers (and the IDE LLM acting on their behalf) authoring AEM workflow models for AEM as a Cloud Service — designing the step graph, splits, joins, transitions, and the model XML that ships through the Cloud Manager pipeline.
Variant Scope
- AEM as a Cloud Service only.
- Models are stored at
/conf/global/settings/workflow/models/. Do not write to/libsor/etc—/libsis immutable and/etc/workflow/models/is the legacy 6.5 path, deprecated on AEMaaCS. - Deploy via Cloud Manager pipeline; design-time → runtime sync is required after deploy (Tools → Workflow → Models → Sync).
- Not for AEM 6.5 LTS. If the target is 6.5 LTS, stop and use the 6.5-lts variant of this skill —
/etc/workflow/models/legacy auto-deploy andmvn install -PautoInstallPackagedeploys documented there do not apply on AEMaaCS.
Dependencies
workflow-foundationreferences (architecture, API, JCR paths, Cloud Service guardrails) — load alongside.workflow-development— every PROCESS step in the model needs aWorkflowProcess(orprocess.label) registered as an OSGi service. Model XML and Java code are co-authored.workflow-launchers— when a launcher routes content into the model, see launcher-side guardrails.
Workflow
Model Design Progress
- [ ] 1) Clarify the workflow purpose: what triggers it, what steps are needed, who approves
- [ ] 2) Map out steps: PROCESS (auto), PARTICIPANT (human), OR_SPLIT (decision), AND_SPLIT (parallel)
- [ ] 3) Decide payload type: single JCR_PATH page/asset, or multi-page via workflow package
- [ ] 4) Identify workflow variables needed for inter-step data passing
- [ ] 5) Design model XML: flow/parsys layer with correct nt:unstructured step components and sling:resourceType per step
- [ ] 6) Add filter.xml entry with mode="merge" for the model path
- [ ] 7) Deploy via Cloud Manager pipeline
- [ ] 8) Open the model in Tools → Workflow → Models → Edit → Sync; verify the model appears in /var/workflow/models/ and all steps render on the editor canvas
- [ ] 9) Start a test workflow instance; confirm it runs to completionOutput Contract
Generate only these files for a /conf-based model:
| File | Node type | Purpose |
|---|---|---|
jcr_root/conf/.../models/<id>/.content.xml | cq:Page | Model root page |
jcr_root/conf/.../models/<id>/jcr:content/.content.xml | cq:PageContent | Title, template, resourceType |
jcr_root/conf/.../models/<id>/jcr:content/flow/.content.xml | nt:unstructured + parsys | Step nodes |
Never generate — hard stops:
- ❌ Any file under
jcr_root/var/— AEM Sync writes/var/workflow/models/automatically after you click Sync in the editor. Never ship/varcontent in a content package. - ❌ A
model/directory insidejcr:content/at the/confpath — acq:WorkflowModelnode with<nodes>and<transitions>is the runtime format. It must never appear under/conf. The Workflow Model Editor cannot open a model that contains it. - ❌
<filter root="/var/workflow/models/..."/>in filter.xml —/varis never a package filter target. The only filter entry needed is the/confpath. - ❌ Any path under
/etc/workflow/models/— deprecated and unsupported on AEM as a Cloud Service.
filter.xml — correct entry:
<filter root="/conf/global/settings/workflow/models/my-workflow" mode="merge"/>Node Types Quick Reference
| Type | Purpose | Key metaData property |
|---|---|---|
START | Entry point | — |
END | Terminal | — |
PROCESS | Auto-executed Java step | PROCESS = FQCN or process.label |
PARTICIPANT | Human task (static assignee) | PARTICIPANT = principal name |
DYNAMIC_PARTICIPANT | Human task (runtime assignee) | DYNAMIC_PARTICIPANT = chooser.label |
OR_SPLIT | One branch selected by rule | Transition rule = ECMAScript (Rhino) |
AND_SPLIT | All branches execute in parallel | — |
AND_JOIN | Wait for all parallel branches | — |
EXTERNAL_PROCESS | Poll an external system | EXTERNAL_PROCESS = FQCN |
Show full SKILL.md (217 more words)Show less
Default Path Rule
Unless the user explicitly names a specific AEM site, always generate models at /conf/global/settings/workflow/models/<id>. Do not infer a site-scoped path (e.g., /conf/wknd/…) from conversational context such as "for the WKND site" or "install on the WKND instance." Workflow models are not site-scoped by default — they are global resources. Only use /conf/<site>/settings/workflow/models/<id> when the user explicitly states that the model should be scoped to a specific site.
Cloud Service Deployment
- Place model XML at:
conf/global/settings/workflow/models/<name>/.content.xml(theflow/parsysdesign-time format — notjcr:content/model/) - Add to
ui.contentpackage withfilter.xmlentrymode="merge" - Deploy via Cloud Manager pipeline
- Open Tools → Workflow → Models → select model → Edit → Sync
- Verify the model appears in
/var/workflow/models/<name>via CRX/DE and all steps render on the canvas
Design-time vs runtime paths: /conf/global/settings/workflow/models/ stores the editor's
flow/parsys format — this is what you author and deploy. Steps are nt:unstructured nodes with
sling:resourceType; no cq:WorkflowNode or cq:WorkflowTransition nodes appear here.
/var/workflow/models/ holds the runtime copy generated by Sync — it uses cq:WorkflowModel,
cq:WorkflowNode, and cq:WorkflowTransition. Never write cq:WorkflowModel nodes to the /conf
path, and never hand-author /var content — AEM manages the runtime layer entirely via Sync.
References
- step-types-catalog.md — complete step type reference with XML snippets
- model-xml-reference.md — full model XML structure and property reference
- model-design-patterns.md — common design patterns: linear, decision, parallel, loop-back
- architecture-overview.md
- jcr-paths-reference.md
- cloud-service-guardrails.md
© adobe, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references) in plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design of adobe/skills.
- SKILL.md
- references/workflow-foundation/README.md
- references/workflow-foundation/api-reference.md
- references/workflow-foundation/architecture-overview.md
- references/workflow-foundation/cloud-service-guardrails.md
- references/workflow-foundation/jcr-paths-reference.md
- references/workflow-foundation/quick-start-guide.md
- references/workflow-model-design/model-design-patterns.md
- references/workflow-model-design/model-xml-reference.md
- references/workflow-model-design/step-types-catalog.md
Open the folder on GitHubat commit cbc9952
Compare with similar skills
Workflow Model Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Workflow Model Design this skilladobe/skills | 195 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Sanity Migrationsanity-io/agent-toolkit | 187 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Content Management Systemsgithub/awesome-copilot | 40k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| App Builder UI ScaffolderNeverSight/learn-skills.dev | 216 | 1 repos | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Authoring Analysismajiayu000/claude-skill-registry | 666 | 2 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Block Inventorymajiayu000/claude-skill-registry | 666 | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Content Management Systems
github/awesome-copilot
Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and…
App Builder UI Scaffolder
NeverSight/learn-skills.dev
Generates React Spectrum UI code for Adobe Experience Cloud Shell apps and AEM UI Extensions from annotated patterns.
Authoring Analysis
majiayu000/claude-skill-registry
Analyze content sequences and determine authoring approach (default content vs blocks).
Block Inventory
majiayu000/claude-skill-registry
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring.
Identify Page Structure
majiayu000/claude-skill-registry
Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import.
More from adobe/skills
All 105 skills in this repoAdobe App Builder Action Scaffolder
adobe/skills
Scaffolds, implements, deploys and debugs Adobe Runtime actions in App Builder projects, with templates for webhooks, events, database CRUD, sequences and Asset Compute workers.
CDP Extension Pilot
adobe/skills
Launches Chrome with an unpacked extension over CDP, opens its sidepanel, popup or options page, and hands over to cdp-connect for clicks, typing and screenshots.
Web Page Resource Collector
adobe/skills
Extracts icons, metadata, text, forms, videos and social links from any web page with playwright-cli, with SVG icon classification and cleanup.
Page Langs
adobe/skills
Detect all languages used on a webpage — both declared (html@lang, hreflang alternate links, nested lang= attributes, meta content-language) and actually present in the body text (Google CLD3 via…
Page Prep
adobe/skills
Prepare any webpage for clean interaction by detecting and removing disruptive overlays (cookie banners, GDPR consent, modals, popups, newsletter signups, paywalls, login walls).
Page Reduce
adobe/skills
Reduce a webpage to a structural skeleton with semantic tokens.
Related
Works with
Questions about Workflow Model Design
What does Workflow Model Design do?
Design and create AEM Workflow models on AEM as a Cloud Service. Workflow Model Design is an agent skill from adobe/skills. Design and create AEM Workflow models on AEM as a Cloud Service.
When should I use Workflow Model Design?
Workflow Model Design fits situations like: creating workflow models via the Workflow Model Editor; content package XML; defining step types (PROCESS; DYNAMICPARTICIPANT.
How do I install Workflow Model Design in Claude Code?
Run `npx skills add adobe/skills --skill workflow-model-design -a claude-code`. Or copy the skill folder (plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design in adobe/skills) into .claude/skills/workflow-model-design in your project. Claude Code loads it when a task matches its description.
How do I install Workflow Model Design in Codex?
Run `npx skills add adobe/skills --skill workflow-model-design -a codex`. Or copy the skill folder (plugins/aem/cloud-service/skills/aem-workflow/workflow-model-design in adobe/skills) into .agents/skills/workflow-model-design in your project. Codex loads it when a task matches its description.
Can I use Workflow Model Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add adobe/skills --skill workflow-model-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-model-design, .gemini/skills/workflow-model-design, .github/skills/workflow-model-design and .opencode/skills/workflow-model-design in your project.
What does Workflow Model Design need to run?
Going by SKILL.md and its folder, Workflow Model Design needs the command-line tools its instructions call (mvn).
Does Workflow Model Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Workflow Model Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Workflow Model Design use?
Workflow Model Design is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Workflow Model Design use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.6k tokens, read only when the agent opens those files.
What are the alternatives to Workflow Model Design?
Skills that share tags, products or a category with Workflow Model Design: Sanity Migration (sanity-io/agent-toolkit, 187 stars), Content Management Systems (github/awesome-copilot, 40k stars), App Builder UI Scaffolder (NeverSight/learn-skills.dev, 216 stars) and Authoring Analysis (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Workflow Model Design?
adobe (a GitHub organization) maintains it in adobe/skills, which has 195 GitHub stars. The repository holds 105 skills in this directory. The repository was last updated on October 6, 2026.
Source: adobe/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.