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
On-premise or AMS DAM asset-processing workflows to asset microservices and post-processing workflows. No Java BPA pattern in this session.
Paths that start with scripts/ are relative to the migration skill directory, the folder of SKILL.md.
If the user asks to migrate DAM asset workflows — DAM Update Asset customizations, asset workflow launchers, custom asset process steps, ImageMagick CommandLineProcess renditions — or mentions Adobe's Asset Workflow Migration Tool / wf-migrator / aem-cloud-migration, follow the 4-step flow. Adobe's wf-migrator JAR makes every change; the skill runs it, gathers the user's decisions and guides the review, and never edits project files itself. The tool version is wf-migrator 0.7.0, pinned by checksum and downloaded on first run; v0.6.0 lacks its fixes (split handling, Completed step, ImageMagick, runner config, XML formatting), so do not use it. Start by reading context.md. Skip Branch B.
node scripts/asset-workflow-run.js <project>. The first run downloads the pinned JAR and checks its SHA-256; --jar <path> uses a local copy instead (context.md). It needs Java 11+ and a clean git tree. Exit 0 = the tool finished; 1 = the tool failed; 2 = stopped before changing anything. Never present a failed run as done.target/asset-workflow-migration/migration-report.md, the script's warnings and git diff with the user, including the models and custom Java steps the report does not cover (context.md). Keep the result or undo it with the undo line the script printed (git checkout . && git clean -fd only when the tree was clean before the run)..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