npx claudepluginhub salesforcecommercecloud/b2c-developer-tooling --plugin b2c-cliThis skill uses the workspace's default tool permissions.
Use the `b2c` CLI plugin to **run existing jobs** and import/export site archives on Salesforce B2C Commerce instances.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Use the b2c CLI plugin to run existing jobs and import/export site archives on Salesforce B2C Commerce instances.
Tip: If
b2cis not installed globally, usenpx @salesforce/b2c-cliinstead (e.g.,npx @salesforce/b2c-cli job run).
Creating a new job? If you need to write custom job step code (batch processing, scheduled tasks, data sync), use the
b2c:b2c-custom-job-stepsskill instead.
# run a job and return immediately
b2c job run my-custom-job
# run a job and wait for completion
b2c job run my-custom-job --wait
# run a job with a timeout (in seconds)
b2c job run my-custom-job --wait --timeout 600
# run a job with parameters (standard jobs)
b2c job run my-custom-job -P "SiteScope={\"all_storefront_sites\":true}" -P OtherParam=value
# show job log if the job fails
b2c job run my-custom-job --wait --show-log
Some system jobs (like search indexing) use non-standard request schemas. Use --body to provide a raw JSON request body:
# run search index job for specific sites
b2c job run sfcc-search-index-product-full-update --wait --body '{"site_scope":["RefArch","SiteGenesis"]}'
# run search index job for a single site
b2c job run sfcc-search-index-product-full-update --wait --body '{"site_scope":["RefArch"]}'
Note: --body and -P are mutually exclusive.
The job import command automatically waits for the import job to complete before returning. It does not use the --wait option.
# import a local directory as a site archive
b2c job import ./my-site-data
# import a local zip file
b2c job import ./export.zip
# keep the archive on the instance after import
b2c job import ./my-site-data --keep-archive
# import an archive that already exists on the instance (in Impex/src/instance/)
b2c job import existing-archive.zip --remote
# show job log on failure
b2c job import ./my-site-data --show-log
# export site data using the job export command
b2c job export
# search for job executions
b2c job search
# search with JSON output
b2c job search --json
# wait for a specific job execution to complete
b2c job wait <execution-id>
See b2c job --help for a full list of available commands and options in the job topic.
b2c:b2c-custom-job-steps - For creating new custom job steps (batch processing scripts, scheduled tasks, data sync jobs)b2c-cli:b2c-site-import-export - For site archive structure and metadata XML patterns