/automation-sandbox-post-copy-config-generate

name: automation-sandbox-post-copy-config-generate
description: "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 and RemoteSiteSettings 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 execute/run the post-copy automation tool. This is the only skill for Salesforce sandbox post-copy config generation."
metadata:
  version: "1.0"

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/config_template.json` and copy an entry from it for each action. Every output entry is exactly one of these two shapes — five top-level keys, no others, no wrapper object:

[
  {
    "ConfigurationName": "OutboundMessages",
    "Label": "IR_Account_OBM_PROD",
    "Fields": { "EndpointUrl": "https://uat.example.com/services/account", "Object": "Account" },
    "IsActive": true,
    "ExecutionOrder": 1
  },
  {
    "ConfigurationName": "RemoteSiteSettings",
    "Label": "R12_Remote_Site",
    "Fields": { "RemoteSiteUrl": "https://uat.example.com" },
    "IsActive": true,
    "ExecutionOrder": 2
  }
]

• `ConfigurationName`: exactly `OutboundMessages` or `RemoteSiteSettings` — never `Type`, `Name`, or `Operation`.
• OBM `Fields`: `EndpointUrl` + `Object` (both required). RemoteSite `Fields`: `RemoteSiteUrl` only — never `Url`/`RemoteSiteURL`.
• Top level is a JSON array. No `steps`/`actions`/`records` wrapper. No `<…>` or `REPLACE_WITH_…` 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.

**Every emitted entry must have every Field populated with a real value from the customer source.** No empty strings, no `null`, no `<from-backup>` / `TBD` / `TODO` placeholders. Customers should never see an unpopulated field in the output — if a value cannot be located, skip the entry and surface it. See the corresponding rule below.

---

Required Inputs

Gather or infer before generating:

• **SOP source(s)**: One or more paths (or pasted content) in any of:

PDF, xlsx, csv, JSON, docx, Markdown, plain text, or images (.png/.jpg/.jpeg/.tiff/.bmp). Multiple files are common — the action list and the endpoint table sometimes live in different files. Read every file the user supplies.

• **Target output path**: Where the JSON config should be written. Default

to `post-copy-config.json` in the current directory unless specified.

• **Scope filter** (optional): If the SOP covers many environments

(e.g., fcQA, fcUAT, multiple sandboxes), confirm which subset the user wants in the output.

If the user provides a clear SOP and target, generate immediately without asking unnecessary questions.

---

Workflow

All steps are sequential. Steps 1–5 (reading the SOP, the catalog, the template, and the schema) are **prerequisites to writing** — you may not skip to the write step. If you catch yourself about to emit JSON without having read `assets/config_template.json` and `references/configuration_catalog.md`, go back and read them first.

1. **Locate and read every supplied SOP source** — read `references/source_format_handling.md` for the exact extraction recipe per format (PDF, xlsx, csv, JSON, docx, image). At a glance:

• **PDF**: extract text with `pypdf` (text layer) and OCR

image-based pages with `pytesseract` if the text layer is empty.

• **xlsx**: read every sheet with `openpyxl` (`data_only=True`),

scan all columns including ones outside the visible default range, check cell comments and embedded media.

• **csv / JSON / Markdown / text**: read directly.
• **docx**: extract paragraphs and tables with `python-docx`.
• **Images** (.png/.jpg/...): use the `Read` tool to view, then

decide if the image carries data (a table of endpoint URLs, a setup screenshot showing values to capture) or is purely illustrative (architecture diagram, flow chart). Extract values only from data-bearing images. See the image-handling rules in `references/source_format_handling.md`.

• For very large SOPs (>50 pages / >20 sheets), focus on