Skip to content

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

automation-sandbox-post-copy-config-generate

Verified

Generates 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).

assets/json_schema.json

View on GitHub
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Post-Copy Automation Config",
  "description": "Array of declarative post-copy actions consumed by the Salesforce post-copy automation tool.",
  "type": "array",
  "items": {
    "type": "object",
    "additionalProperties": false,
    "required": [
      "ConfigurationName",
      "Label",
      "Fields",
      "IsActive",
      "ExecutionOrder"
    ],
    "allOf": [
      {
        "if": {
          "properties": { "ConfigurationName": { "const": "RemoteSiteSettings" } }
        },
        "then": {
          "properties": {
            "Fields": {
              "type": "object",
              "additionalProperties": false,
              "required": ["RemoteSiteUrl"],
              "properties": {
                "RemoteSiteUrl": {
                  "description": "The exact API field name for a Remote Site Setting URL. Must be spelled RemoteSiteUrl — Url, RemoteSiteURL, SiteUrl, and EndpointUrl are all invalid.",
                  "type": "string",
                  "minLength": 1
                }
              }
            }
          }
        }
      },
      {
        "if": {
          "properties": { "ConfigurationName": { "const": "OutboundMessages" } }
        },
        "then": {
          "properties": {
            "Fields": {
              "type": "object",
              "required": ["Object"],
              "anyOf": [
                { "type": "object", "required": ["EndpointUrl"] },
                { "type": "object", "required": ["Action"] }
              ]
            }
          }
        }
      },
      {
        "if": {
          "properties": { "ConfigurationName": { "const": "ScheduledApex" } }
        },
        "then": {
          "properties": {
            "Fields": {
              "type": "object",
              "additionalProperties": false,
              "required": ["ApexClassName", "CronExpression", "JobName"],
              "properties": {
                "ApexClassName": {
                  "description": "Bare Apex identifier of the class that implements Schedulable. Must match ^[A-Za-z_][A-Za-z0-9_]*$.",
                  "type": "string",
                  "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"
                },
                "CronExpression": {
                  "description": "Salesforce cron expression — 6 or 7 whitespace-separated fields.",
                  "type": "string",
                  "minLength": 1
                },
                "JobName": {
                  "description": "Human-readable job name. Appears in Setup > Scheduled Jobs and equals CronTrigger.CronJobDetail.Name post-schedule.",
                  "type": "string",
                  "minLength": 1
                }
              }
            }
          }
        }
      },
      {
        "if": {
          "properties": { "ConfigurationName": { "const": "Flows" } }
        },
        "then": {
          "properties": {
            "Fields": {
              "type": "object",
              "additionalProperties": false,
              "required": ["FlowApiName", "Action"],
              "properties": {
                "FlowApiName": {
                  "description": "Flow DeveloperName — unique across Flows in the org. Maps to FlowDefinition.DeveloperName. Must match ^[A-Za-z_][A-Za-z0-9_]*$.",
                  "type": "string",
                  "pattern": "^[A-Za-z_][A-Za-z0-9_]*$"
                },
                "Action": {
                  "description": "Whether the apply-side skill should Activate or Deactivate the flow. Exact string match, case-sensitive.",
                  "type": "string",
                  "enum": ["Activate", "Deactivate"]
                },
                "VersionNumber": {
                  "description": "Optional. Only meaningful when Action is Activate — the specific flow version to activate. If omitted for Activate, the apply-side skill resolves to the latest saved version. Ignored for Deactivate.",
                  "type": "integer",
                  "minimum": 1
                }
              }
            }
          }
        }
      }
    ],
    "properties": {
      "ConfigurationName": {
        "description": "Salesforce configuration / metadata type. Must be one of the values listed in references/configuration_catalog.md.",
        "type": "string",
        "enum": [
          "OutboundMessages",
          "RemoteSiteSettings",
          "ScheduledApex",
          "Flows"
        ]
      },
      "Label": {
        "description": "The metadata Label or DeveloperName of the specific record being updated, exactly as it appears in the SOP.",
        "type": "string",
        "minLength": 1
      },
      "Fields": {
        "description": "Map of API field name -> concrete value taken verbatim from the SOP. Do not include fields that are duplicated by Label (RemoteSiteName) or by the top-level IsActive flag.",
        "type": "object",
        "minProperties": 1,
        "additionalProperties": {
          "type": ["string", "number", "boolean"]
        },
        "$comment": "Per-ConfigurationName key constraints are enforced by the allOf/if-then blocks above."
      },
      "IsActive": {
        "description": "Whether the post-copy tool should execute this action. Default true.",
        "type": "boolean"
      },
      "ExecutionOrder": {
        "description": "Phase number. Entries with no dependency on each other share the same value and run in parallel; lower numbers run before higher.",
        "type": "integer",
        "minimum": 1
      }
    }
  }
}
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