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
Source → target: Legacy AEM 6.x / AMS / on-prem → AEM as a Cloud Service. Scoped under skills/aem/cloud-service/skills/migration/ so this is not confused with Edge Delivery or 6.5 LTS.
This skill drives the migration workflow: BPA data, CAM/MCP, one pattern per session, and target discovery. Transformation rules and steps live in the code-assessment skill — once a finding's pattern is identified, hand off to {code-assessment}/<pattern>/SKILL.md (or the relevant shared reference under {code-assessment}/references/).
Setup: Use the aem-cloud-service install (see repository root README) so both migration and code-assessment paths are available. If you already have the monorepo open with resolvable {code-assessment} paths, no separate install step is required.
For the person driving the agent: references/quick-start.md has what to say for each kind of migration, with copy-paste prompts.
From the repository root (parent of the skills/ directory):
| Symbol | Path |
|---|---|
{code-assessment} | skills/aem/cloud-service/skills/code-assessment/ |
Examples: {code-assessment}/SKILL.md, {code-assessment}/scheduler/SKILL.md, {code-assessment}/references/scr-to-osgi-ds.md.
Applies to finding and editing the user's AEM project (Java, bundles, config, HTL), not to reading installed skill files under {code-assessment}.
grep, and file reads/writes for migration targets.~, other clones, or arbitrary absolute paths to "discover" sources unless the user explicitly names those paths or asks you to include them.filePath or class-to-file mapping does not resolve under a workspace root, stop and tell the user which paths are missing — do not hunt elsewhere on the filesystem. Ask them to open the correct project in the IDE or adjust paths.Find the branch for the request and read its file before anything else. Each of Branches A and C–I skips Branch B. A, C, E, G, H and I take no BPA pattern id.
| Branch | The user asks to… | Read first, and follow |
|---|---|---|
| A — OSGi configs → Cloud Manager | scan config files; create or set up Cloud Manager environment secrets or variables; move passwords or secrets out of OSGi / .cfg.json / ui.config; or mentions $[secret:] / $[env:] | references/osgi-cfg-json-cloud-manager.md immediately: the product rules and the workflow are in that file. A short prompt is enough; the user need not name the file. |
| B — Java / HTL / BPA pattern | fix one pattern, from a BPA CSV, from CAM, or in files they name | The steps under Branch B below |
| C — Template modernization | migrate static templates to editable templates ("create editable templates", "generate /conf templates", "static to editable", "parsys to container"); generate AEM Modernize Tools rules (structure / component / policy rewrite rules) | template-modernization-context.md, then per template editable-template-creation.md and aem-modernization.md, then template-modernization-validation.md |
D — Legacy UI (lui, cdw) | convert Classic UI / ExtJS dialogs; upgrade Coral 2 dialogs; migrate custom ExtJS widgets; fix LUI or CDW findings; or mentions cq:Dialog / xtype / cq:Widget | The steps under Branch D below |
| E — Dispatcher conversion | convert or migrate an AMS / on-premise Dispatcher configuration | references/dispatcher/flow.md: six phases around Adobe's dispatcher-converter. HARD STOP on filter-acl-loss. Do not present the result as done on validation failure. |
F — Oak index (oakIndex, beta) | fix Oak index findings; convert _oak_index definitions | references/oak-index.md: six steps around Adobe's index-converter. Compute the next free -custom-N, never assume -custom-1. Flag a datatype mismatch as needs_manual_review; do not apply it silently. Tell the user that the output needs a careful review. |
| G — Validate a migration (beta) | validate, verify or smoke-test migrated code on the local Cloud SDK | references/validation/validate-migration.md. It never edits customer source; a failure goes back to the branch that owns the pattern. |
| H — Asset workflow migration | 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 | references/asset-workflow/flow.md: four steps around Adobe's wf-migrator, which makes every change. The skill runs it and guides the review; it never edits project files itself. Never present a failed run as done. |
| I — Repository restructuring (beta) | restructure the project for AEM as a Cloud Service; split a content package into code (ui.apps) and content (ui.content); create ui.config or the all package; or mentions the Repository Modernizer | references/repo-structure/flow.md: five steps around Adobe's repository-modernizer. The plan review with the user is required. The tool's output is a copy: check it, then adopt it on a branch. Run this before the other branches when the project has no ui.config or all. |
Branch B — Java / HTL / BPA pattern migration:
Read {code-assessment}/SKILL.md — critical rules, Java baseline links, Pattern Guides table, Manual Pattern Hints.
Read the pattern guide (or reference) for the single active pattern:
scheduler → {code-assessment}/scheduler/SKILL.md (pattern guide)resourceChangeListener → {code-assessment}/resource-change-listener/SKILL.md (pattern guide)replication → {code-assessment}/replication/SKILL.md (pattern guide)eventListener / eventHandler → {code-assessment}/event-migration/SKILL.md (pattern guide — both JCR and OSGi Event Admin paths)assetApi → {code-assessment}/asset-manager/SKILL.md (pattern guide)htlLint → {code-assessment}/references/data-sly-test-redundant-constant.md (reference — HTL lint is a single shared reference, not a dedicated pattern guide)vault-package-dependencies → references/vault-package-dependencies.md (reference — heuristic pom.xml scan)guavaCache → references/guava-cache.md (reference — Guava cache → Caffeine)inputStream → references/input-stream.md (reference — triage of the DG / java.io.inputstream advisory; detection is scripts/input-stream-runner.js, not the code-assessment analyzer)The last three live under migration only, not under code-assessment: these shapes occur only in code carried over from legacy AEM.
When code uses SCR, ResourceResolver, or console logging, read {code-assessment}/references/scr-to-osgi-ds.md and {code-assessment}/references/resource-resolver-logging.md (or the hub {code-assessment}/references/aem-cloud-service-pattern-prerequisites.md).
Do not transform Java or HTL until the pattern guide (or reference) is read (branch B). Branch A does not require {code-assessment} pattern guidance.
Behavior pinning (before-eligible Java patterns). For guavaCache, scheduler, resourceChangeListener, and eventListener/eventHandler, Step 5 pins a one-per-finding characterization test around each edit (green before → transform → green after). Rules and skeletons: references/characterization-tests.md.
Branch D — Legacy UI Migration (legacy-ui/ sub-folders):
lui, sub-types legacy.dialog.classic and legacy.dialog.coral2 only): read dialog/context.md (getBpaFindings('lui', …), filter to the dialog sub-types, skip all others with a note); convert with extjs-to-coral3.md (convert-extjs) or coral2-to-coral3.md (upgrade-coral2); validate with dialog/validation.md.cdw): read cdw/context.md (getBpaFindings('cdw', …), inventory the xtypes); per xtype apply cdw/conversion.md (a mapping, or a scaffolded Granite UI component); validate with cdw/validation.md.ui.apps or equivalent content package with .html HTL templatesGet targets with getBpaFindings from ./scripts/bpa-findings-helper.js; do not reimplement collection logic by hand unless the helper is unavailable. The flow, the call, collection caching and the batching rules: references/bpa-helper.md.
mcpFetcher + projectId) the first call fetches from CAM and caches; with a BPA CSV the first call parses it and caches. With neither, the helper reports no-source: ask the user for one.htlLint is not in a BPA CSV. It uses proactive rg discovery; see htlLint flow.Critical: On MCP failure, stop the workflow immediately and give the user the exact tool error message (verbatim), including "not found" / 404-style project errors. Do not continue with migration steps, infer a different CAM project from the workspace, or switch to manual/local migration on your own.
Exception: enablement restriction errors (prefix documented in references/cam-mcp.md) must be shown verbatim with no paraphrase and no automatic fallback until the user addresses them.
After stopping, you may summarize what failed in plain language and re-show the projects. Continue only when the user explicitly directs the next step: a CAM project id or name from the list, a BPA CSV path, or specific Java files for the manual flow. Retries and error categories are in references/cam-mcp.md; still no silent fallback. Never hide tool errors from the user.
Optional prompt after stop (user must reply): "Reply with the CAM project to use (id or name from the list), a path to your BPA CSV, or the Java files for a manual migration."
When the user opens with a broad review/scan request ("review my code for AEMaaCS migration", "scan my project for AEM migration") and does not name a single pattern, generate a read-only migration runbook before any apply work. It is one command; do not read the generator's source:
node scripts/runbook-generator.js <workspaceRoot> --out ./migration-runbook.md --cache ./migration-runbook.jsonAdd --csv <bpa.csv> for a BPA CSV. For CAM, for an LLM scan when the command prints ⚠️ Needs LLM scan: …, for how each pattern is detected, and for what to tell the user afterwards: references/runbook.md. Read it before you run a runbook with CAM data.
Skip Step 0 when the user names a specific pattern up front: go straight to the relevant apply flow.
If the user asks to fix everything or BPA mixes patterns, ask which pattern first. Prefer one commit per pattern session.
First check the branches other than B (see Required delegation): A (OSGi configs), C (templates), D (Legacy UI: lui for dialogs, cdw for widgets), E (Dispatcher), F (Oak index, oakIndex), G (validate), H (asset workflows), I (repository restructuring).
Otherwise map the request to a pattern id: scheduler, resourceChangeListener, replication, eventListener, eventHandler, assetApi, htlLint, lui, cdw, inputStream. If unclear, use Manual Pattern Hints in {code-assessment}/SKILL.md or ask the user to pick one of those.
If the id is missing from the code-assessment catalog ({code-assessment}/references/patterns.md), say the pattern is not supported yet. Exception: the migration-only references routed in Branch B step 2 (vault-package-dependencies, guavaCache, inputStream) are supported even though they aren't in that catalog.
In this order, and stop at the first that has findings for the active pattern:
./migration-runbook.json: reuse findingsByPattern[<pattern>] and tell the user that you do. Heuristic entries (htlLint, osgiConfig) are candidates: re-confirm each before editing.getBpaFindings for BPA patterns (scheduler, resourceChangeListener, replication, eventListener, eventHandler, assetApi, lui, cdw). If MCP fails, obey MCP errors and fallback.rg for htlLint; scripts/input-stream-runner.js for inputStream, which always runs once because BPA names classes and not lines; the inventory of Branch E for dispatcherConversion.Every path serves five findings per batch. How to read the cache, the envelope, and the rules for lui, inputStream, htlLint and osgiConfig targets: references/targets.md. Read it before the first batch.
STOP. Read {code-assessment}/SKILL.md and the pattern guide (or reference) for the active pattern — see Branch B step 2 above for the pattern → file routing table.
For each finding in the returned batch only (up to 5):
guavaCache, scheduler, resourceChangeListener, eventListener/eventHandler), write one characterization test for this finding and run it green before editing — this pins current behavior. Follow that file's efficiency contract exactly: one fill-in skeleton, one attempt, skip-fast with pin-skip: <reason>. Never debug a test. All other patterns (including replication, assetApi, and every non-Java pattern) skip this step.pinned. Red after the edit → a real regression: revert this finding's edit, record pin-fail → reverted, and move on — do not retry or edit the test.After finishing the batch, summarise for this batch only: paging.returned of paging.total processed (with class names), files touched, and any skips/failures. For before-eligible patterns, add each finding's pin outcome (pinned | pin-skip: <reason> | pin-fail → reverted) per references/characterization-tests.md — omit this line entirely for patterns that are not before-eligible. If paging.hasMore, tell the user "Processed batch of N (offset {offset}–{offset + returned − 1} of {total}). Reply continue for the next batch, or name specific classes."; otherwise say the pattern is done and move to the session report.
Then stop and wait — resume only when the user explicitly asks, per the Batched-processing rules.
User-named files → classify (code-assessment Manual Pattern Hints or ask) → confirm the pattern guide or reference exists → read {code-assessment}/SKILL.md + the pattern guide (or reference) — see Branch B step 2 routing — → transform → report.
htlLint does not use BPA CSV or CAM/MCP. Its three steps (read the reference, discover with rg, fix and report): references/htl-lint.md.
Findings come in batches of 5, whatever the source. The fetch (MCP call or CSV parse) happens once and is cached; each further batch is a slice of the cache.
limit: null.result.paging.nextOffset. Never compute offset + limit yourself.paging.hasMore === false.The full rules and an example exchange: references/bpa-helper.md.
The source priority for BPA patterns and the snippets to show the user: references/bpa-helper.md.
.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