Turn Sandbox Refresh SOPs into Post-Copy Config JSON

Where this fits

A release engineer just received a refreshed sandbox and a messy folder of SOPs: endpoint tables, PDF runbooks, and a screenshot of an outbound message config. They need to rebuild the post-copy automation file quickly. This skill parses those artifacts and generates the exact JSON config consumed by Salesforce sandbox post-copy automation—without manual transcription.

Why agents benefit

• Reads multi-format input: PDF, xlsx, csv, JSON, docx, Markdown, plain text, even a screenshot of an endpoint table, so the agent does not need pre-normalized data.
• Emits the config schema with ConfigurationName, Label, Fields, IsActive, and ExecutionOrder, plus OutboundMessages and RemoteSiteSettings entries.
• Triggers naturally from phrases like 'post-copy config', 'post-refresh automation JSON', 'convert this SOP to config', reducing prompt engineering.
• Disambiguates from deploy/execute skills, routing to platform-metadata-deploy or automation-sandbox-post-copy-configure when appropriate.
• Preserves SOP-to-config traceability, making agent output auditable against the source runbook.

Practical scenarios

Migrating an endpoint SOP after a sandbox refresh

You have a customer's 'Sandbox Refresh Planner.xlsx' with OBM endpoint names, field lists, and remote site URLs. The agent reads the workbook and produces a ready-to-review post-copy JSON array.

Converting a PDF runbook with screenshots

A stakeholder sends a PDF SOP and a cropped screenshot of endpoint tables. The skill extracts entries and normalizes them into config fields, so you can validate labels and execution order before automation.

Generating remote site settings JSON from Markdown docs

An engineering wiki stores remote site settings as a table in Markdown. The agent converts that table into RemoteSiteSettings entries and pairs them with OutboundMessages in one generated config file.

Add it to your agent workflow

Install the skill with:

npx skills add forcedotcom/sf-skills --skill automation-sandbox-post-copy-config-generate

Then ask: 'Read this sandbox refresh SOP PDF and generate the post-copy config JSON.' The agent will output the JSON array with the expected keys, ready for review or handoff to a deploy skill. For related context and skill comparisons, see this entry in the OpenAgentSkill directory: https://www.openagentskill.com/skills/forcedotcom-automation-sandbox-post-copy-config-generate

Compare before adopting

Before adding it, compare against:

• Quality signals: Does the generated JSON preserve exact field names and execution order from the source SOP? Does it handle ambiguous endpoint tables reliably?
• Maintenance freshness: Is the skill compatible with the Salesforce post-copy automation tool version you use? Check its GitHub history.
• Alternatives: A generic extraction agent may produce JSON, but likely without the Salesforce-specific schema and trigger phrases.
• Workflow fit: Does it stop at config generation, and is your pipeline ready to send that JSON to platform-metadata-deploy or automation-sandbox-post-copy-configure?

Why it is worth tracking

The skill is part of forcedotcom/sf-skills, a Salesforce-maintained collection with 964 stars, which signals active community adoption and frequent updates. Track it when you standardize sandbox refresh automation; if your team receives SOPs in mixed formats, this skill removes a repetitive manual step and keeps generated config consistent. Re-evaluate whenever Salesforce changes post-copy automation limits or introduces new config keys.