forcedotcom/sf-skills / plugins/builder/dx-org-lifecycle/skills/automation-sandbox-post-copy-config-generate
automation-sandbox-post-copy-config-generate
VerifiedGenerates 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 (OBM), RemoteSiteSettings, ScheduledApex, and Flows 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).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.5 KB |
| assets/config_template.json | config | 1.4 KB |
| assets/json_schema.json | config | 5.5 KB |
| examples/sample_sop_excerpt.md | markdown | 1.3 KB |
| examples/sample_sop_to_config.json | config | 1.1 KB |
| references/configuration_catalog.md | markdown | 7.2 KB |
| references/sop_parsing_patterns.md | markdown | 6.3 KB |
| references/source_format_handling.md | markdown | 8.4 KB |
references/configuration_catalog.md
View on GitHub# Configuration Catalog
The fixed catalog of supported `ConfigurationName` values for the post-copy
automation config. **Never invent a new value** — if an SOP step does not
fit a row below, raise it to the user.
The catalog currently covers four types only:
1. `OutboundMessages`
2. `RemoteSiteSettings`
3. `ScheduledApex`
4. `Flows`
Anything else (Custom Labels, Connected Apps, Named Credentials, SSO, etc.)
is out of scope for this skill at present — surface them to the user and
recommend a follow-up to extend the catalog.
## How to use this catalog
For each post-copy action extracted from the SOP:
1. Find the row whose **SOP signal** phrases match the action.
2. Use the `ConfigurationName` from that row.
3. Use one of the listed **Field keys** in your entry's `Fields` object.
4. Put the **concrete value** from the SOP (literal URL, name, etc.) as
the value. If the SOP does not state a concrete value, **skip the
entry** entirely and list it in the response.
## Catalog
### OutboundMessages
- **SOP signal phrases**: "outbound message", "OBM", "endpoint URL",
"Workflow Actions > Outbound Messages".
- **Field keys** (both required for non-delete entries):
- `EndpointUrl` — value is the literal post-refresh URL the SOP gives
for that outbound message.
- `Object` — the SObject the outbound message targets (e.g., `Account`,
`Contact`, `Asset`, `Lead`). This is mandatory because the same
`Label` may apply to multiple OBMs that differ only by entity, and
the post-copy tool needs the Object to disambiguate. Infer from the
OBM name (e.g., `IR_Account_OBM_PROD` → `Account`,
`IR_Contact_OBM_PROD` → `Contact`) or from explicit text in the SOP.
If the entity is genuinely ambiguous and the SOP gives no signal,
skip the entry and surface it.
- **Skip when**: the SOP only names the outbound message but does not
give a new endpoint URL, OR the target Object cannot be determined.
- **Special action**: deletion. When the SOP says "delete all endpoints",
use `Fields: { "Action": "Delete", "Object": "<entity>" }`. (`"Delete"`
is a literal instruction the tool understands, not a placeholder.)
### RemoteSiteSettings
- **SOP signal phrases**: "remote site setting", "remote site", "trusted
URL", "Setup > Security > Remote Site Settings".
- **Field keys**:
- `RemoteSiteUrl` — value is the literal post-refresh URL. The key must
be spelled **exactly** `RemoteSiteUrl`. Do **not** use `Url`,
`RemoteSiteURL`, `SiteUrl`, or `EndpointUrl` (that last one is the OBM
key, not the remote-site key). The post-copy tool matches the field by
exact API name, so any other spelling silently no-ops at runtime.
- **Do NOT add**:
- `RemoteSiteName` — the name lives in the top-level `Label` field.
- `IsActive` — the active flag lives at the top level of the entry.
Putting either inside `Fields` duplicates information the tool already
has and creates ambiguity.
- **Skip when**: the SOP names the remote site but does not give a new
URL.
### ScheduledApex
- **SOP signal phrases**: "scheduled apex", "scheduled job", "cron
trigger", "System.schedule", "Setup > Scheduled Jobs", "re-schedule
the nightly job", "schedule the batch class after refresh".
- **Field keys** (all three required):
- `ApexClassName` — the bare Apex identifier of the class that
implements `Schedulable`. Must match `^[A-Za-z_][A-Za-z0-9_]*$` —
no dots, no spaces, no namespace prefix in this field, no `.cls`
suffix. Example: `NightlyDataSyncScheduler`.
- `CronExpression` — a 6- or 7-field Salesforce cron expression. The
apply-side skill validates the shape, but do not emit a
single-word / malformed value here. Example: `0 0 2 * * ?`
(every day at 2:00 AM).
- `JobName` — the human-readable job name that appears in Setup >
Scheduled Jobs. Post-schedule this equals
`CronTrigger.CronJobDetail.Name`; the apply-side skill uses it
both as the `System.schedule` argument and as the SOQL key when
verifying the job materialized. Typically the same string the
customer uses to refer to the job.
- **Do NOT add**:
- Any other Field key (e.g. `NextFireTime`, `State`, `CronTriggerId`)
— `CronTrigger` is read-only and computed by the platform, so only
the three inputs to `System.schedule` belong in `Fields`.
- **Skip when**: the SOP names a scheduled job but does not give all
three of `ApexClassName`, `CronExpression`, and `JobName`. Never
fabricate one from the others (for example, do not derive a JobName
from the class name or vice versa) — surface the incomplete entry
in the response so the user can supply the missing piece.
### Flows
- **SOP signal phrases**: "flow", "deactivate flow", "activate flow",
"turn off <FlowName>", "turn on <FlowName>", "Setup > Process Automation
> Flows", "post-copy flow deactivation", "reactivate flow after refresh".
- **Field keys**:
- `FlowApiName` (required) — the flow's DeveloperName, which is unique
across Flows in the org. Maps to `FlowDefinition.DeveloperName` in
the Tooling API. Do NOT use the flow label / MasterLabel; labels
are not unique. If the SOP names a flow by label only, look up the
API name within the SOP's own accompanying material (an endpoint
table, companion sheet, screenshot caption) before emitting the
entry. If the API name cannot be located from the supplied SOP
sources, **skip the entry and flag it in the summary** — never
guess or synthesize an API name from the label.
- `Action` (required) — exactly `"Activate"` or `"Deactivate"` (case-
sensitive). Verbatim string literal — the apply-side skill matches
by exact value.
- `VersionNumber` (optional, positive integer) — meaningful only when
`Action` is `"Activate"`. Selects which saved flow version to make
active. If omitted for `Activate`, the apply-side skill resolves to
the latest saved version. Ignored (and should be omitted) for
`Deactivate`.
- **Semantics**:
- `Action: "Deactivate"` deactivates the flow if it is currently
active. If it is already inactive, the apply-side skill records
`ALREADY_INACTIVE` and does not issue a PATCH.
- `Action: "Activate"` activates the requested version (or the
latest saved version if `VersionNumber` is omitted). If the flow
is already active at that version, the apply-side skill records
`ALREADY_ACTIVE` and does not issue a PATCH.
- **Do NOT add**:
- Any other Field key (e.g. `Status`, `ActiveVersionId`,
`activeVersionNumber`, `Label`). Flow activation/deactivation is
driven entirely by `Fields.FlowApiName` + `Fields.Action` (+
optional `Fields.VersionNumber`); the apply-side skill owns the
Tooling API mutation shape.
- **Skip when**: the SOP names a flow but does not indicate whether to
activate or deactivate it, OR the API name (DeveloperName) of the
flow cannot be determined from the SOP. Never fabricate a
`FlowApiName` from the label.
## Adding a new ConfigurationName
If a customer SOP introduces a configuration type not in the list above,
**stop and ask the user**. Adding a new value requires:
1. Update the `enum` in `assets/json_schema.json`.
2. Add a new section to this file.
3. Update `examples/sample_sop_to_config.json` if relevant.
4. Update the description in `SKILL.md` to include the new type.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |