Salesforce B2C Commerce SLAS (Shopper Login and API Access Service) client management Skill
/plugin marketplace add SalesforceCommerceCloud/b2c-developer-tooling/plugin install b2c-cli@b2c-developer-toolingThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Use the b2c CLI plugin to manage SLAS (Shopper Login and API Access Service) API clients and credentials.
# list all SLAS clients for a tenant
b2c slas client list --tenant-id abcd_123
# list with JSON output
b2c slas client list --tenant-id abcd_123 --json
# get details for a specific SLAS client
b2c slas client get --tenant-id abcd_123 --client-id my-client-id
# create a new SLAS client with default scopes (auto-generates UUID client ID)
b2c slas client create --tenant-id abcd_123 --channels RefArch --default-scopes --redirect-uri http://localhost:3000/callback
# create with a specific client ID and custom scopes
b2c slas client create my-client-id --tenant-id abcd_123 --channels RefArch --scopes sfcc.shopper-products,sfcc.shopper-search --redirect-uri http://localhost:3000/callback
# create a public client
b2c slas client create --tenant-id abcd_123 --channels RefArch --default-scopes --redirect-uri http://localhost:3000/callback --public
# create client without auto-creating tenant (if you manage tenants separately)
b2c slas client create --tenant-id abcd_123 --channels RefArch --default-scopes --redirect-uri http://localhost:3000/callback --no-create-tenant
# output as JSON (useful for capturing the generated secret)
b2c slas client create --tenant-id abcd_123 --channels RefArch --default-scopes --redirect-uri http://localhost:3000/callback --json
Note: By default, the tenant is automatically created if it doesn't exist.
# update an existing SLAS client
b2c slas client update --tenant-id abcd_123 --client-id my-client-id
# delete a SLAS client
b2c slas client delete --tenant-id abcd_123 --client-id my-client-id
The tenant ID can be set via environment variable:
SFCC_TENANT_ID: SLAS tenant ID (organization ID)See b2c slas --help for a full list of available commands and options in the slas topic.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.