automation-sandbox-post-copy-configure
Installation
SKILL.md
Automation: Sandbox Post-Copy Configure
Apply a Salesforce sandbox post-copy automation JSON config to a target
org. Three canonical ConfigurationName values are pinned:
OutboundMessages and RemoteSiteSettings take the compound-Metadata
PATCH route (Steps A–E); ScheduledApex takes the anonymous-Apex route
(Step F), because CronTrigger is read-only in the Tooling API. Any
other ConfigurationName is derived and describe-verified. Every A–E
entry — pinned or derived — must pass Step B (describe returns 200 with
a Metadata compound field) before any PATCH is planned; Step B does
not apply to ScheduledApex. Entries whose API cannot be verified are
surfaced in the summary and skipped — never guessed at.