What problem does it solve? Manually starting AEM workflows after every content change is error-prone and does not scale. This Skill teaches how to configure Workflow Launchers that automatically start workflows in response to JCR node events on AEM as a Cloud Service, without editing immutable /libs paths. ## Core Features & Use Cases - Launcher Configuration: Create cq:WorkflowLauncher nodes with eventType, glob, nodetype, conditions, workflow, and runModes properties deployed via ui.content packages. - OOTB Launcher Overlays: Disable or modify out-of-the-box launchers like dam_update_asset_create by placing override nodes under /conf/global/settings/workflow/launcher/config/. - Loop Prevention & Debugging: Apply excludeList, session user data, and condition patterns to avoid infinite workflow loops, and verify launchers via the Launchers UI and OSGi console. - Use Case: Automatically start the DAM Update Asset workflow whenever an original rendition is uploaded under /content/dam, restricted to the author run mode. ## Quick Start Ask the assistant to create a workflow launcher that starts the DAM Update Asset workflow when a new asset is uploaded under /content/dam on the author instance.