All AEM as a Cloud Service skills: component development, Workflow model design, development, triggering, launchers, debugging, and triaging, Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening, Rapid Development Environment (RDE) deployment, log inspection, snapshots, and troubleshooting via `aio aem rde`, Jackrabbit Oak query/index tuning (property, Lucene index definitions), and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Migrates on-premise / AMS DAM asset-processing workflows (enabled DAM Update Asset launchers, overlaid or custom asset workflow models, custom process steps) to AEM as a Cloud Service. On Cloud Service the asset microservices create renditions and extract metadata; anything else the old workflow did runs afterwards as a post-processing workflow started by the Custom Workflow Runner (CustomDamWorkflowRunnerImpl), and custom renditions move to processing profiles.
This branch runs Adobe's own Asset Workflow Migration Tool (adobe/aem-cloud-migration, wf-migrator JAR). The tool makes every change to the project. scripts/asset-workflow-run.js only checks the environment, runs the tool and checks it finished; your job is to gather the user's decisions and guide the review. Do not re-implement or hand-patch what the tool does — if its output is wrong, tell the user and report it to the tool's repository.
Adobe docs: Asset Workflow Migration Tool, asset microservices and post-processing workflows. Step categories (what the tool keeps, removes or maps): workflowSteps.properties.
Only workflows that still do something on Cloud Service need migrating. The Step 0 runbook (pattern assetWorkflowMigration) lists enabled launchers whose glob is under /content/dam; it does not read the models. Open each launcher's model with the user:
CreateVersionProcess, ReplicationWorkflowProcess, …) — becomes a post-processing workflow.CreateWebEnabledImageProcess with custom sizes, simple ImageMagick CommandLineProcess) — the tool maps them to a Migrated from <model> processing profile.PATH, curl (the first run downloads the pinned JAR) and git.content-package module (the tool rewrites those, adds aem-cloud-migration.* modules and edits the reactor POM).--allow-dirty only if the user accepts that the tool's changes can then not be undone with git; the script then prints no git undo.The script pins wf-migrator 0.7.0 and checks the SHA-256 of the download. --jar <path> uses a local copy instead (the script then reports a custom JAR). Do not use 0.6.0 or older: they lack split handling, the Completed step, ImageMagick renditions, runner config merging and XML formatting (adobe/aem-cloud-migration#25). To upgrade, change TOOL_VERSION, TOOL_URL and TOOL_SHA256 in asset-workflow-run.js and run the opt-in end-to-end test (ASSET_WF_E2E=1 npm test).
node scripts/asset-workflow-run.js <projectRoot> # [--jar <path>] [--report-dir <dir>] [--allow-dirty]The tool exits 0 even when it fails, so the script counts a run as successful only if it printed Migration complete. and wrote migration-report.md (default <project>/target/asset-workflow-migration/, with wf-migrator.log next to it). Exit codes: 0 done, 1 tool failed, 2 stopped before changing anything. Never present a failed run as done.
What the tool does: disables the asset launchers, rewrites the models it migrates, writes processing profiles and a Custom Workflow Runner config (/apps/aem-cloud-migration/config.author/…CustomDamWorkflowRunnerImpl.cfg.json) into new aem-cloud-migration.* modules, deletes every jcr_root/var workflow path from the project and its filters (runtime models are regenerated on sync), and writes the report.
Do this before anything is committed. To undo everything, use the undo line the script printed: git checkout . && git clean -fd when the tree was clean before the run, and never after an --allow-dirty run (it would discard the user's own changes too).
migration-report.md section by section: launchers disabled, runner configurations, models changed, paths deleted, processing profiles, Migration Issues.wf-migrator.log. The tool prints Migration complete. even when it skipped a launcher or model it could not parse (Unable to parse …), and it still deletes the var paths. A skipped model is not migrated: fix its XML and rerun from a clean tree.git diff. Confirm each migrated model ends with DAM Update Asset Completed and each runner entry points at the right model and glob.CommandLineProcess) but does not migrate or list that model. Open every model behind a disabled launcher and flag:
CommandLineProcess commands that are not simple ImageMagick conversions. The report lists the ones it could not map under Migration Issues; they need an Asset Compute custom worker.UNSUPPORTED in workflowSteps.properties (for example CreateSubAssetsProcess, IDSJobProcess, ExtractImagesProcess). Ask whether what they produced is still needed and agree a replacement: a custom worker, a profile rendition, or dropping it.PROCESS that is not an Adobe class; the tool keeps them). For each one in the project source, check with the user that it runs on Cloud Service: it uses only APIs available there. Hand code that needs changes to the matching Branch B patterns (asset-manager, replication, scr-to-osgi-ds) instead of editing it here.Deploy the migrated project (an RDE is quickest: aem-rde skill) and work through these with the user:
GET /var/workflow/models/<id>.json must return 200.CustomDamWorkflowRunnerImpl with the expected postProcWorkflowsByPath / postProcWorkflowsByExpression. Look for overlapping entries; Adobe does not document which one wins when several match, so merge the models if the wrong one runs.git diff).conditions (for example jcr:content/jcr:mimeType!=video/.*) do not carry over to the runner. Upload an asset the old condition excluded and check the post-processing workflow handles or skips it as intended; add a guard step otherwise..tessl-plugin
skills
aem-rde
aem-workflow
code-assessment
asset-manager
evals
event-migration
references
replication
request-controlled-security-bypass
resource-change-listener
scripts
tuning-oak-query-indexes
content-distribution
create-component
assets
references
dispatcher
incident-response
references
dispatcher-foundation
performance-tuning
references
dispatcher-foundation
security-hardening
references
dispatcher-foundation
technical-advisory
references
dispatcher-foundation
workflow-orchestrator
references
dispatcher-foundation
ensure-agents-md
references
migration
evals
files
legacy-project
ui.apps
src
main
content
jcr_root
apps
example
components
page
references
asset-workflow
dispatcher
integrations
legacy-ui
template-modernization
validation
scripts
dispatcher-tool
repo-modernizer-tool
validate-migration