Agent-Skills.md

Agent Skills: Site Archives

Import and export site archives containing metadata XML on B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to import a site archive directory or zip to an instance, export site configuration as XML, structure a site archive folder (sites/site_template/meta/), write or debug metadata XML files (system-objecttype-extensions.xml, custom-objecttype-definitions.xml, preferences.xml), or push custom attributes, custom object types, or site preferences to a sandbox via site import. Also use when an import job fails with schema validation errors — even if they just say "push metadata to the sandbox" or "import my XML files".

UncategorizedID: salesforcecommercecloud/b2c-developer-tooling/b2c-site-import-export

Repository

salesforcecommercecloud/b2c-developer-tooling
SalesforceCommerceCloudLicense: Apache-2.0
4612

Install this agent skill to your local

pnpm dlx add-skill https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/tree/HEAD/skills/b2c-cli/skills/b2c-site-import-export

Skill Files

Browse the full folder contents for b2c-site-import-export.

Download Skill

Loading file tree…

skills/b2c-cli/skills/b2c-site-import-export/SKILL.md

Skill Metadata

Name
b2c-site-import-export
Description
Author, validate, import, and verify B2C Commerce site archives and metadata XML; export selected data for inspection or migration.

Site Archives

Use b2c job import / b2c job export to transfer site archives. If b2c is unavailable, use npx @salesforce/b2c-cli.

Configuration and tool choice

CLI and MCP share resolved configuration: SFCC_* variables (including project .env), project/shared dw.json, and plugins. package.json provides nonsecret defaults. Use --project-directory outside the target project. Inspect with b2c setup inspect --json or MCP config_inspect; keep secrets masked. Configured values normally make credential flags and manual dw.json reads unnecessary. For resolution issues, use b2c-cli:b2c-config.

No dedicated MCP archive-transfer tool exists. Use the CLI for XML imports and exports, including settings absent from SCAPI contracts. MCP scapi_execute can manage supported Admin fields; a metadata record alone does not prove that promotion discounts or targeting rules are configured.

Import and verify

  1. Resolve the target site/catalog and intended change. Include only relevant data in the archive; preserve unrelated settings and requested enabled state.
  2. Author XML in the platform archive layout. Check the relevant XSD with b2c docs schema <name> (list names with --list), then validate locally.
  3. Import the directory or zip. The command waits by default; --show-log shows job logs on failure. Check completion before retrying.
  4. Read back the affected fields. If the API omits them, export the matching data unit and inspect the relevant XML records. A successful job alone is insufficient.
b2c job import ./archive --show-log
b2c job export --site MySite --site-data campaigns_and_promotions --output ./verification

--site alone exports all site data; specify --site-data for focused work. Directory output retains the platform's generated *_export root. Do not overwrite an existing/applied migration. Exports may contain secrets or unrelated defaults; review and trim before committing, preserving XSD-required fields.

Focused references

  • Archive layout and XML workflows: archive workflows.
  • Attribute/type XML patterns: metadata XML.
  • Remote imports, size splitting, and import-set options: import options.
  • Export flags, data units, and compact JSON results: the export reference in the b2c-job skill.
  • Ordered migrations, naming, history, and recovery: b2c-cli:b2c-import-set-migrations.
  • Service configuration XML: b2c:b2c-webservices.

Jobs prefer SCAPI; --api-backend auto can fall back to OCAPI on supported rejections. Archive transfer uses WebDAV in either case. For job scopes, backend selection, and monitoring, use the relevant section of b2c-cli:b2c-job.