What problem does it solve? Legacy AEM code using AssetManager binary-path APIs (createAssetForBinary, getAssetForBinary, removeAssetForBinary) breaks on AEM as a Cloud Service because those APIs no longer exist, and client-facing upload servlets violate the cloud runtime's Direct Binary Access model. ## Core Features & Use Cases - Path A migration (create/upload): Replaces removed createAssetForBinary/getAssetForBinary calls and client-facing upload servlets with Direct Binary Access via @adobe/aem-upload and the HTTP Assets API. - Path B migration (delete): Replaces removeAssetForBinary with in-JVM resolver.delete() plus commit using a service-user resolver, or external HTTP Assets API DELETE calls authenticated with IMS bearer tokens. - Governance and setup: Covers Repoinit service-user creation, ServiceUserMapperImpl.amended mapping, SCR-to-DS annotation conversion, SLF4J logging, and a full review checklist. - Use Case: A team migrating a legacy AEM 6.5 codebase to AEMaaCS finds servlets calling removeAssetForBinary; this Skill rewrites them to use a service-user ResourceResolver with idempotent deletes and proper jcr:removeNode permissions. ## Quick Start Ask the assistant to migrate this legacy servlet that uses AssetManager.removeAssetForBinary to an AEM Cloud Service compatible implementation.