CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

adobe/aem-cloud-service

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

cross-boundary.mdskills/migration/references/dispatcher/

Dispatcher Conversion — Cross-Boundary Router (Branch E)

This is phase 5 (JUDGMENT + CROSS-BOUNDARY) of the flow in context.md: once the tool has converted the config and phase 4 has verified it, route each remaining concern to the owner that already knows how to resolve it instead of reimplementing it here.

Router

ConcernOwnerWhere
Cloud Manager variablesmigration Branch Arun scripts/dispatcher-crossboundary.js; hand the cmVars artifact to Branch A (../../SKILL.md → Branch A / osgi-cfg-json-cloud-manager.md); secretLike entries get Branch A's secret handling
Immutable/default freshness & driftdispatcher skillconfig-authoring → sdk(action="diff-baseline"), sdk(action="check-files"); validation-playbook.md §6 managed defaults
Filter/ACL security posture (deny-by-default, no allow-all, sensitive-path denies)dispatcher skillsecurity-hardening → security-baseline-checklist.md + sensitive-paths-catalog.md; run lint(strict). Required after conversion — filter-acl-loss (phase 4) is a rule-count gate, not a posture check, so a preserved-but-insecure policy still needs this pass.
Security headers / edge / CDN splitdispatcher skillsecurity-hardening (headers) and performance-tuning (cache/edge)
Config validation & qualitydispatcher skillconfig-authoring → validate / lint (already routed by validation.md)

Why delegate. The dispatcher skill owns these via the core-7 MCP tools for cloud configs; Branch E contributes the conversion delta + CM handoff and hands off the rest.

See also

  • context.md — the 6-phase flow this doc is phase 5 of, and the mode taxonomy.
  • config-generation.md — phase 2; the config.yaml contract the tool is driven with.
  • output-verification.md — phase 4; the verification gate that must clear before this routing pass runs.
  • validation.md — phase 6; already delegates config validation/quality to the dispatcher skill.
  • current-sdk-conventions.md — the target end-state conventions these owners resolve against.

skills

migration

references

dispatcher

config-generation.md

context.md

conversion-patterns.md

cross-boundary.md

current-sdk-conventions.md

output-verification.md

validation.md

bpa-helper.md

cam-mcp.md

guava-cache.md

input-stream.md

oak-index.md

osgi-cfg-json-cloud-manager.md

vault-package-dependencies.md

README.md

SKILL.md

README.md

tile.json