skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
salesforcecommercecloud/b2c-developer-tooling89 installs

b2c-site-import-export

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

How do I install this agent skill?

npx skills add https://github.com/salesforcecommercecloud/b2c-developer-tooling --skill b2c-site-import-export
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill facilitates the management of Salesforce B2C Commerce site archives and metadata using the b2c CLI. It includes standard workflows for importing and exporting configuration data. While the skill processes external XML data—which presents a standard attack surface for indirect prompt injection—no malicious patterns or unauthorized behaviors were detected.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    2/2 files flagged

What does this agent skill do?

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.

Use the CLI for XML imports and exports, including settings absent from SCAPI contracts. Without a terminal, MCP site_archive_import imports XML given as text (skill://mcp/b2c-mcp-site-import/SKILL.md); it does not export. 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 the archive with b2c validate ./archive (MCP: validate_xml_schema) and fix every error.
  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. For a full instance export use --all; --site all, --catalog all, etc. select every object of one type. Prefer these flags over hand-written --data-units JSON. 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.
  • Sample storefront datasets and new-instance setup: b2c-cli:b2c-setup.

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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-site-import-export">View b2c-site-import-export on skillZs</a>