Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/adobe-migration-deep-dive

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-migration-deep-dive

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈888 when used: this file. ≈837 more on demand in 1 file.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈359 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

Approval Boundaries

Program, identity, security, data, product, budget, and operations owners approve their waves. Live content movement, dual writes, cutover, and deletion require separate explicit approval.

Error Handling

  • Do not claim parity from happy-path samples only.
  • Do not map a retired Lightroom service to a different Lightroom API by name.
  • Pause on count, content, provenance, authorization, or cost divergence.

Output

Return capability map, contracts, wave plan, test corpus, parity evidence, decisions, cutover/rollback, cleanup, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Reconcile a synthetic PDF workflow across source and target.
  • Classify a source capability with no current Adobe equivalent as a gap.

Validation

Exercise and record expected and observed results for:

  • auth mismatch
  • format drift
  • policy difference
  • duplicate action
  • cost drift
  • rollback

Resources

  • Current first-party evidence map — recheck dated Adobe sources before execution.
  • Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill establishes a secure, evidence-based framework for Adobe platform migrations, focusing on documentation review and planning. It incorporates robust security practices, including the use of synthetic fixtures with canaries, explicit exclusion of secrets from artifacts, and mandatory human approval gates for all live actions. All external references target official developer documentation from a well-known service.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<source-platform> <target-services> <migration-scope>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "program-migration"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adobe-migration-deep-dive