Agent skill · software engineering · jeremylongshore
adobe-migration-deep-dive
Analyze and execute a multi-workload migration into or across Adobe services with contract evidence, dependency waves, dual-run reconciliation, cost controls, and rollback. Use when the task requires adobe platform migration program. Trigger with "Adobe migration plan", "move workflow to Adobe", or "Adobe platform consolidation".
Why this skill is useful
Adds detailed migration scripts and strategies for transitioning to Adobe APIs, which are not commonly found in public documentation.
What it needs
Requires bash installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Platform Migration Program Overview Analyze and execute a multi-workload migration into or across Adobe services with contract evidence, dependency waves, dual-run reconciliation, cost controls, and rollback. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract A migration is a set of product-specific contracts, not an endpoint translation. Auth ownership, entitlement, async behavior, input/output fidelity, storage custody, content rules, limits, events, and operational tooling must each map from source to target. Recheck the dated evidence map before relying on mutable product behavior. Authentication Choose S2S or user auth per data owner, not migration convenience. Preserve source/target identity and access evidence and never copy secrets or production content into test fixtures. Instructions 1. Inventory source workflows, volumes, identities, data classes, formats, SLAs, costs, dependencies, and retirement constraints. 2. Map each capability to current Adobe service/version or classify it as gap, redesign, or retire; exclude EOL products. 3. Define adapters, canonical data contracts, idempotency, provenance, reconciliation, storage, and rollback boundaries. 4. Build synthetic and sampled approved parity tests for outputs, metadata, ordering, policy, latency, and cost. 5. Migrate in dependency waves with shadow/dual-run only where duplicate actions and spend are controlled. 6. Reconcile every wave, cut over from explicit thresholds, archive receipts, and remove approved obsolete paths and credentials. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-migration-deep-dive