Skip to content

forcedotcom/sf-skills / plugins/builder/dx-org-lifecycle/skills/automation-sandbox-post-copy-configure

automation-sandbox-post-copy-configure

Verified

Apply a Salesforce sandbox post-copy automation JSON config against a target org. Use when the user asks to apply, run, execute, dry-run, or preview a post-copy or post-refresh config file (e.g. `post-copy-config.json`) against a sandbox — including activating/deactivating a Flow (PATCH `FlowDefinition.Metadata.activeVersionNumber` to the version, or `null`), re-pointing an OBM endpoint, updating a RemoteSiteSetting URL, or re-scheduling a ScheduledApex job after refresh. Also trigger for phrasings like "apply post-copy config", "run post-copy automation", "activate Flow <name> post-refresh", "deactivate Flow <name>", "re-point outbound messages after refresh", or "configure sandbox after refresh". Per entry, derive the Tooling API sobject, verify via describe, resolve the Id via SOQL, then PATCH the compound `Metadata` field (`ScheduledApex` uses anonymous Apex). DO NOT TRIGGER for generating config JSON from an SOP (use `automation-sandbox-post-copy-config-generate`) or for deploying metadata XML.

examples/sample_execution_summary.md

View on GitHub
# Sample Execution Summary

The exact shape of the summary the skill writes to
`./post-copy-<mode>-summary.md` and prints when a run completes.
Grouped by phase, ordered by `ExecutionOrder` ascending. Every entry
from the input config appears exactly once.

---

## Post-Copy Configure Run — 5 entries applied against `dev-sandbox`

Config file: `./post-copy-config.json`
Target org: `dev-sandbox` (Sandbox — instance `NA123`)
Mode: apply (not dry-run)
Continue-on-error: true

### Phase 1 (ExecutionOrder = 1) — 3 entries, all parallel

Verified sobject for `OutboundMessages`: `WorkflowOutboundMessage`
(describe returned 200; `Metadata` compound field present).

| ConfigurationName | Label                | Object   | Sobject                    | Describe | Outcome            | HTTP |
|-------------------|----------------------|----------|----------------------------|----------|--------------------|------|
| OutboundMessages  | IR_Account_OBM_PROD  | Account  | WorkflowOutboundMessage    | 200      | SUCCESS            | 204  |
| OutboundMessages  | IR_Contact_OBM_PROD  | Contact  | WorkflowOutboundMessage    | 200      | SUCCESS            | 204  |
| OutboundMessages  | IR_Legacy_OBM        | Account  | WorkflowOutboundMessage    | 200      | SKIPPED_INACTIVE   | —    |

### Phase 2 (ExecutionOrder = 2) — 2 entries, all parallel

Verified sobject for `RemoteSiteSettings`: `RemoteProxy`
(describe returned 200; `Metadata` compound field present).

| ConfigurationName    | Label              | Object | Sobject     | Describe | Outcome     | HTTP |
|----------------------|--------------------|--------|-------------|----------|-------------|------|
| RemoteSiteSettings   | osbomwtst2         | —      | RemoteProxy | 200      | SUCCESS     | 204  |
| RemoteSiteSettings   | FlexNet_Middleware | —      | RemoteProxy | 200      | NOT_FOUND   | —    |

---

## Totals

| Outcome            | Count |
|--------------------|-------|
| SUCCESS            | 3     |
| NOT_FOUND          | 1     |
| SKIPPED_INACTIVE   | 1     |
| FAILED             | 0     |
| API_NOT_IDENTIFIED | 0     |

## Follow-ups

- `IR_Legacy_OBM` (OutboundMessages, Account) had `IsActive: false`
  in the config and was **not** PATCHed. The record on the target
  org is unchanged. If you intended to deactivate it on the target,
  flip `IsActive: true` in the config and re-run, or deactivate the
  parent WorkflowRule manually.
- `FlexNet_Middleware` (RemoteSiteSettings) was not found on the
  target org. Verify the `SiteName` matches an existing Remote Site
  Setting, or create the record via a metadata deployment before
  re-running the post-copy configure.

---

## Outcome vocabulary

| Outcome                | Meaning |
|------------------------|---------|
| `SUCCESS`              | HTTP 2xx from the PATCH; the record was updated and the read-back matched |
| `NOT_FOUND`            | Lookup returned zero rows; the record does not exist on the target org |
| `AMBIGUOUS`            | Lookup returned multiple rows after client-side filtering; refuse to PATCH |
| `API_NOT_IDENTIFIED`   | No candidate Tooling sobject passed the describe-verify gate for this `ConfigurationName` |
| `FIELD_MAP_UNKNOWN`    | Derived camelCase key was not present in the record's current `Metadata` block; refuse to PATCH the wrong field |
| `FAILED`               | HTTP 4xx (other than 404) or 5xx from the PATCH; include the Salesforce error code and message |
| `FAILED_VERIFY`        | PATCH returned 204 but the read-back value does not match the requested value |
| `SKIPPED_INACTIVE`     | `IsActive: false` in the config; entry was not PATCHed |
| `SKIPPED`              | Entry was skipped for another reason (dry-run, or a preceding phase failure with `continue-on-error = false`) |
| `DRY_RUN`              | Dry-run mode; the request that would be sent is captured but not executed |
| `DELETE_NOT_SUPPORTED` | Entry had `Fields.Action = "Delete"`; this skill does not delete records |
| `NOT_ATTEMPTED`        | Cancelled because an earlier failure aborted the run with `continue-on-error = false` |
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall