b2c-config_skill
- TypeScript
20
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill salesforcecommercecloud/b2c-developer-tooling --skill b2c-config- SKILL.md5.8 KB
Overview
This skill helps you view and debug the B2C CLI configuration and trace where each credential or setting is coming from. It exposes resolved configuration, source attribution, and tools to manage named instance configurations so you can fix authentication, connectivity, and instance selection problems quickly.
How this skill works
Use the setup inspect command to display the resolved configuration with each value labeled by its source (dw.json, env vars, plugins, ~/.mobify, etc.). You can unmask sensitive values for deeper debugging, emit JSON for scripts, and target specific instances or config files. Instance commands list, create, switch, and remove named instance entries stored in dw.json.
When to use it
- Authentication failures or revoked credentials — confirm clientId/clientSecret or username/password are loaded.
- Connection or hostname mismatch errors — verify hostname, webdavHostname, and hostname protection sources.
- When commands use the wrong instance — check and set the active instance.
- CI/CD or scripts that must read precise config — use JSON output to validate sources.
- When you need to confirm MRT API key, OAuth scopes, or TLS/mTLS certificate loading.
Best practices
- Run b2c setup inspect --json in automated checks to assert expected sources and values.
- Use --unmask only in secure environments and avoid logging full secrets in shared logs.
- Prefer environment variables or CLI flags for CI where secret rotation is frequent.
- Check the source column first to understand why a value is chosen (priority rules apply).
- Manage instances with setup instance create/set-active to avoid accidental operations on the wrong site.
Example use cases
- Debug a failing b2c auth token command by confirming clientId/clientSecret and their source.
- Verify that a staging instance is active before running code deployment commands.
- Scripted validation in CI: assert that dw.json or env vars provide required SCAPI and MRT keys.
- Recover from swapped credentials: find which plugin or env var is overriding dw.json.
- Inspect TLS/mTLS settings when two-factor WebDAV auth or certificate passphrases fail.
FAQ
Run b2c setup inspect --unmask. Only use this on trusted machines and avoid exposing output in shared logs.
Which source wins when the same value is defined in multiple places?
Resolution follows priority: CLI flags/env vars, high-priority plugin sources, dw.json, ~/.mobify (MRT API key only), lower-priority plugin sources, then package.json b2c key.