Agent skill · forcedotcom
automation-sandbox-post-copy-config-generate
Generate the JSON config file that the Salesforce sandbox post-copy automation tool consumes, from a customer SOP in any format (PDF, xlsx, csv, JSON, docx, Markdown, plain text, or a screenshot of an endpoint table). Use when the user asks to create, build, generate, produce, or convert a post-copy or post-refresh automation config — turning a sandbox-refresh SOP into a JSON array of OutboundMessages, RemoteSiteSettings, and ScheduledApex entries with ConfigurationName, Label, Fields, IsActive, and ExecutionOrder. Also trigger for phrasings like \"post-copy config\", \"post-refresh automation JSON\", \"update the outbound message (OBM) endpoints after refresh\", \"convert this SOP to config\", \"remote site settings JSON\", \"refresh planner to JSON\", or \"sandbox refresh config\". DO NOT TRIGGER when: user wants to deploy the generated config to an org (use platform-metadata-deploy), or apply/execute/run/dry-run the post-copy automation JSON against a sandbox (use automation-sandbox-post-copy-configure).
What it needs
About 10k tokens when loaded.
What this skill does
Automation: Sandbox Post-Copy Config Generate Convert a customer's sandbox-refresh / post-copy SOP into a structured JSON array that the post-copy automation tool consumes. Each entry is a declarative instruction: which Salesforce configuration to update, which fields are involved, whether it is active, and what order it runs in. STOP — do this before writing any JSON Do not compose the output from memory. Before you write the file, you MUST open and read assets/configtemplate.json and copy an entry from it for each action. Every output entry is exactly one of these three shapes — five top-level keys, no others, no wrapper object: ConfigurationName: exactly OutboundMessages, RemoteSiteSettings, or ScheduledApex — never Type, Name, or Operation. OBM Fields: EndpointUrl + Object (both required). RemoteSite Fields: RemoteSiteUrl only — never Url/RemoteSiteURL. ScheduledApex Fields: ApexClassName + CronExpression + JobName (all three required). Top level is a JSON array. No steps/actions/records wrapper. No <…> or REPLACEWITH… placeholder ever survives into the output. If you announce "I will now write …" without having read the template and catalog, stop and read them first — a from-memory guess produces the wrong keys and fails at runtime. Scope In scope: Reading a customer SOP in any of the supported formats (PDF, xlsx, csv, JSON, docx, Markdown, plain text, pasted excerpt, or images containing data tables — e.g., a screenshot of an Outbound Messages list with endpoint URLs), identifying post-copy / post-refresh actions, mapping each action to a supported ConfigurationName, emitting the canonical JSON array. Out of scope: Generating Salesforce metadata XML (delegate to generating- skills), deploying anything to an org, running the post-copy tool, inferring or fabricating values not present in the SOP — if the SOP does not give a concrete URL/value for an action, skip the action. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/automation-sandbox-post-copy-config-generate--db238e