@salesforce/b2c-dx-mcp 2.1.1 → 3.0.0

package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-sites/evals/trigger-evals.json

@@ -0,0 +1,12 @@
+[
+  {"query": "I'm writing a deployment script and I need to pull the list of site IDs from our sandbox programmatically. I want the output as JSON so I can parse it with jq and feed the IDs into our import step.", "should_trigger": true},
+  {"query": "We just deployed a new cartridge called plugin_loyalty and I need to add it to the RefArch site's cartridge path, right after app_storefront_base. How do I do that without messing up the existing order?", "should_trigger": true},
+  {"query": "I'm trying to figure out which of our storefronts are actually online right now on the staging instance. Is there a quick way to check their status from the terminal?", "should_trigger": true},
+  {"query": "I need to verify that the cartridge path on our production instance matches what we have configured in our deployment manifest. How do I pull down the current cartridge path for a specific site?", "should_trigger": true},
+  {"query": "We're decommissioning two sites from our instance and I need to first check all the site IDs and their statuses before we start the removal process. Can I get a table view of everything from the CLI?", "should_trigger": true},
+  {"query": "Our deployment pipeline needs to reorder the cartridge path so that int_newpayment comes before int_oldpayment for the SiteGenesis site. I want to script this so it runs after every code deploy.", "should_trigger": true},
+  {"query": "I need to set up the XML for a new site preference that controls whether our loyalty feature is enabled. What's the metadata format for preferences.xml?", "should_trigger": false},
+  {"query": "How do I create a brand new storefront site in Business Manager with its own catalog and price book?", "should_trigger": false},
+  {"query": "I need to push my cartridge code to the sandbox after making changes to my controllers. What's the deploy command?", "should_trigger": false},
+  {"query": "I want to import a site archive with all the metadata and preferences onto a fresh sandbox. How do I structure the import directory?", "should_trigger": false}
+]

package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-slas/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: b2c-slas
+description: Create, update, and manage SLAS (Shopper Login and API Access Service) clients using the b2c CLI. Use this skill whenever the user needs to provision a SLAS client, update OAuth scopes, rotate client secrets, get a shopper access token, or configure shopper authentication for headless, PWA, or Storefront Next (SFNext) storefronts — even if they just say "I need a shopper token" or "set up auth for my storefront".
+---
+
+# B2C SLAS Skill
+
+Use the `b2c` CLI plugin to manage SLAS (Shopper Login and API Access Service) API clients and credentials.
+
+> **Important:** SLAS is for **shopper** (customer) authentication used by storefronts and headless commerce. For **admin** tokens (OCAPI, Admin APIs), use `b2c auth token` - see [b2c-config skill](../b2c-config/SKILL.md).
+
+> **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli slas client list`).
+
+## Configuration
+
+Values like `tenantId`, `shortCode`, `slasClientId`, and `slasClientSecret` resolve from `dw.json` / `SFCC_*` env vars / the active instance / configuration plugins. Examples below show minimal usage; **add flags only to override configured values** — passing these as flags is usually unnecessary. If a required value is missing, the CLI emits an actionable error pointing at the flag, env var, and config key.
+
+Run `b2c setup inspect` to see the resolved configuration and which source provided each value (`--json` for scripting; secrets stay masked by default). For precedence rules and troubleshooting, see the `b2c-cli:b2c-config` skill.
+
+Relevant overrides:
+
+- `--tenant-id` / `SFCC_TENANT_ID` / `tenantId`
+- `--short-code` / `SFCC_SHORTCODE` / `shortCode`
+- `--slas-client-id` / `SFCC_SLAS_CLIENT_ID` / `slasClientId`
+- `--slas-client-secret` / `SFCC_SLAS_CLIENT_SECRET` / `slasClientSecret`
+
+Commands that target an existing client (`get`, `update`, `delete`, and `open`) use the configured `slasClientId` when their positional client ID is omitted. A positional client ID takes precedence over configuration.
+
+## When to Use
+
+Common scenarios requiring SLAS client management:
+
+- **Testing Custom APIs**: Create a client with custom scopes (e.g., `c_loyalty`) to test your Custom API endpoints
+- **PWA/Headless Development**: Configure clients for composable storefronts
+- **Integration Testing**: Create dedicated test clients with specific scope sets
+
+## Examples
+
+### List SLAS Clients
+
+```bash
+# list all SLAS clients for the configured tenant
+b2c slas client list
+
+# JSON output
+b2c slas client list --json
+
+# target a different tenant than the active config
+b2c slas client list --tenant-id abcd_123
+```
+
+### Get SLAS Client Details
+
+```bash
+# get details for the configured SLAS client
+b2c slas client get
+
+# override the configured client ID
+b2c slas client get my-client-id
+```
+
+### Create SLAS Client
+
+```bash
+# create a new SLAS client with default scopes (auto-generates UUID client ID)
+b2c slas client create --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 --channels RefArch --scopes sfcc.shopper-products,sfcc.shopper-search --redirect-uri http://localhost:3000/callback
+
+# create a public client
+b2c slas client create --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 --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 --channels RefArch --default-scopes --redirect-uri http://localhost:3000/callback --json
+```
+
+Note: By default, the tenant is automatically created if it doesn't exist.
+
+**Warning:** Use `--scopes` (plural) for client scopes, NOT `--auth-scope` (singular). The `--auth-scope` flag is a global authentication option for OAuth scopes.
+
+### Create Client for Custom API Testing
+
+When testing a Custom API that requires custom scopes:
+
+```bash
+# Create a private client with custom scope for testing
+# Replace c_my_scope with your API's custom scope from schema.yaml
+b2c slas client create \
+  --channels RefArch \
+  --default-scopes \
+  --scopes "c_my_scope" \
+  --redirect-uri http://localhost:3000/callback \
+  --json
+
+# Output includes client_id and client_secret - save these for token requests
+```
+
+**Important:** The custom scope in your SLAS client must match the scope defined in your Custom API's `schema.yaml` security section.
+
+### Get a Shopper Token
+
+Use `b2c slas token` to obtain a shopper access token for API testing. The `--site-id` is specific to the request and must be provided per call.
+
+The command applies shared HTTP middleware, including headers from `SFCC_EXTRA_HEADERS`
+(a JSON object) or `--extra-headers`, to authorization, login, and token requests.
+JSON output nests token fields under `response` (for example, `.response.accessToken`).
+For authentication failures, use `--log-level debug` to capture HTTP status and the SLAS response correlation ID.
+
+```bash
+# Guest token with auto-discovery (finds first public SLAS client)
+b2c slas token --site-id RefArch
+
+# Registered customer token
+b2c slas token --site-id RefArch --shopper-login user@example.com --shopper-password secret
+
+# JSON output (includes refresh token, expiry, usid, etc.)
+b2c slas token --site-id RefArch --json
+
+# Use token in a subsequent API call
+TOKEN=$(b2c slas token --site-id RefArch)
+curl -H "Authorization: Bearer $TOKEN" "https://$SHORTCODE.api.commercecloud.salesforce.com/..."
+
+# Override the SLAS client explicitly (e.g., targeting a private client for client_credentials flow)
+b2c slas token --site-id RefArch --slas-client-id my-client --slas-client-secret sk_xxx
+
+# Registered customer token against a private client (registered login is always PKCE-protected;
+# the client secret is sent as Basic auth in addition to the PKCE code_verifier)
+b2c slas token --site-id RefArch --slas-client-id my-client --slas-client-secret sk_xxx \
+  --shopper-login user@example.com --shopper-password secret
+```
+
+### Update SLAS Client
+
+```bash
+# update the configured client's display name
+b2c slas client update --name "New Name"
+
+# override the configured client ID and rotate its secret
+b2c slas client update my-client-id --secret new-secret-value
+
+# add scopes (appends to existing by default)
+b2c slas client update my-client-id --scopes sfcc.shopper-baskets
+
+# replace scopes instead of appending
+b2c slas client update my-client-id --scopes sfcc.shopper-baskets --replace
+
+# replace channels
+b2c slas client update my-client-id --channels RefArch,SiteGenesis --replace
+```
+
+### Delete SLAS Client
+
+```bash
+# delete the configured SLAS client
+b2c slas client delete
+
+# override the configured client ID
+b2c slas client delete my-client-id
+```
+
+### Open SLAS Client
+
+```bash
+# open the configured SLAS client in the Admin UI
+b2c slas client open
+
+# override the configured client ID
+b2c slas client open my-client-id
+```
+
+### More Commands
+
+See `b2c slas --help` for a full list of available commands and options in the `slas` topic.
+
+## Related Skills
+
+- `b2c:b2c-custom-api-development` - Creating Custom APIs that require SLAS authentication
+- `b2c-cli:b2c-scapi-custom` - Checking Custom API registration status

package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-slas/evals/trigger-evals.json

@@ -0,0 +1,12 @@
+[
+  {"query": "I'm setting up authentication for our new headless storefront and I need to create a client with the right scopes, including a custom c_loyalty scope for our loyalty API. How do I provision this?", "should_trigger": true},
+  {"query": "I need a shopper access token to test some API endpoints with curl. What's the quickest way to get one for my RefArch site?", "should_trigger": true},
+  {"query": "Our security team wants us to rotate the client secret on our existing shopper auth client and also add a new scope. How do I update it?", "should_trigger": true},
+  {"query": "We're launching a new mobile app that needs its own auth client separate from our web storefront. I need to create it with a specific set of allowed scopes and a particular redirect URI. Walk me through provisioning that.", "should_trigger": true},
+  {"query": "I need to clean up old auth clients that were created during development. Can I get a list of all the shopper login clients on our tenant so I can identify which ones are safe to delete?", "should_trigger": true},
+  {"query": "We're migrating from session-based auth to token-based for our PWA and I need to understand how to set up the client credentials for guest and registered shopper flows. I also need to make sure the scopes cover our custom APIs.", "should_trigger": true},
+  {"query": "I need an admin API token so my CI pipeline can make Data API calls to import product data. How do I authenticate?", "should_trigger": false},
+  {"query": "How do I set up an API client in Account Manager with the right roles for deploying code to our sandboxes?", "should_trigger": false},
+  {"query": "I want to implement passwordless login using magic links in my storefront. What's the flow for sending a login email and handling the callback?", "should_trigger": false},
+  {"query": "My dw.json has client_id and client_secret for the CLI but it's not authenticating. How do I troubleshoot the OAuth token exchange?", "should_trigger": false}
+]

package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-webdav/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: b2c-webdav
+description: List, upload, download, and manage files on B2C Commerce instances via WebDAV. Use this skill whenever the user needs to upload files to IMPEX directories, download exports from an instance, list remote files, create or delete directories, zip or unzip files on the server, manage file transfers to sandboxes, or browse instance file systems — even if they just say "upload a file to the instance" or "check what's in the IMPEX folder".
+---
+
+# B2C WebDAV Skill
+
+Use the `b2c` CLI plugin to perform WebDAV file operations on Salesforce B2C Commerce instances. This includes listing files, uploading, downloading, and managing files across different WebDAV roots.
+
+> **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli webdav ls`).
+
+## MCP equivalent
+
+Prefer `webdav_list`, `webdav_get`, and `webdav_put` when available for one-directory
+listings, exact text reads, and single-file transfers. `webdav_get` uses HTTP byte
+ranges (`offset`, `maxBytes`, returned `size`/`nextOffset`); `outputPath` downloads a
+whole file. `webdav_put` accepts `content` or `sourcePath`; parent must exist,
+replacement needs `overwrite: true`. Local paths are on the MCP host, relative to
+`projectDirectory`. Transfers cap at 64 MiB; no prerequisite skill read.
+Use `cartridge_deploy` for local cartridge selection/mapping. Keep the CLI for
+recursive transfers, mkdir, delete, ZIP/UNZIP, or extra flags not exposed by MCP.
+
+## Configuration & Authentication
+
+The CLI auto-discovers the target instance and credentials from `SFCC_*` environment variables (including project `.env`), the selected project-local or shared `dw.json`, and configuration plugins. `package.json` supplies only non-sensitive defaults. **Flags like `--server`, `--client-id`, `--client-secret`, `--username`, and `--password` are usually unnecessary** — only pass them to override what's auto-detected.
+
+Run `b2c setup inspect` to see the resolved configuration and which source provided each value (use `--json` for scripting; secrets stay masked by default). For precedence rules and troubleshooting, see the `b2c-cli:b2c-config` skill.
+
+## WebDAV Roots
+
+The `--root` flag specifies the WebDAV directory:
+
+- `impex` (default) - Import/Export directory
+- `temp` - Temporary files
+- `cartridges` - Code cartridges
+- `realmdata` - Realm data
+- `catalogs` - Product catalogs
+- `libraries` - Content libraries
+- `static` - Static resources
+- `logs` - Application logs
+- `securitylogs` - Security logs
+
+## Examples
+
+### List Files
+
+```bash
+# list files in the default IMPEX root
+b2c webdav ls
+
+# list files in a specific path
+b2c webdav ls src/instance
+
+# list files in the cartridges root
+b2c webdav ls --root=cartridges
+
+# list files with JSON output
+b2c webdav ls --root=impex --json
+```
+
+### Download Files
+
+```bash
+# download a file from IMPEX (default root)
+b2c webdav get src/instance/export.zip
+
+# download to a specific local path
+b2c webdav get src/instance/export.zip -o ./downloads/export.zip
+
+# download from a specific root
+b2c webdav get customerror.log --root=logs
+
+# output file content to stdout
+b2c webdav get src/instance/data.xml -o -
+```
+
+### Upload Files
+
+```bash
+# upload a file to IMPEX
+b2c webdav put ./local-file.zip src/instance/
+
+# upload to a specific root
+b2c webdav put ./my-cartridge.zip --root=cartridges
+```
+
+### Create Directories
+
+```bash
+# create a directory in IMPEX
+b2c webdav mkdir src/instance/my-folder
+
+# create a directory in a specific root
+b2c webdav mkdir my-folder --root=temp
+```
+
+### Delete Files
+
+```bash
+# delete a file
+b2c webdav rm src/instance/old-export.zip
+
+# delete from a specific root
+b2c webdav rm old-file.txt --root=temp
+```
+
+### Delete Cartridges
+
+To delete cartridges from a code version, use the `cartridges` root with the path format `{code-version}/{cartridge-name}`:
+
+```bash
+# delete a cartridge from a code version
+b2c webdav rm v25_1_0/app_mysite --root=cartridges
+
+# delete multiple cartridges
+b2c webdav rm v25_1_0/app_mysite --root=cartridges
+b2c webdav rm v25_1_0/int_myintegration --root=cartridges
+
+# list cartridges in a code version first
+b2c webdav ls v25_1_0 --root=cartridges
+```
+
+**Important:** The path is `{code-version}/{cartridge-name}`, not `/cartridges/{code-version}/...`. The `--root=cartridges` (or `-r cartridges`) flag sets the WebDAV root.
+
+### Zip/Unzip Remote Files
+
+```bash
+# create a zip archive of a remote directory
+b2c webdav zip src/instance/my-folder
+
+# extract a remote zip archive
+b2c webdav unzip src/instance/archive.zip
+```
+
+### Import-Set Managed State
+
+Do not manually script marker files when the goal is to apply a local set of site import/export archives once. Use the higher-level command:
+
+```bash
+b2c job import-set
+```
+
+To start over without deleting the previous history, use a new set ID and keep using it on subsequent runs:
+
+```bash
+b2c job import-set --set-id migrations-reset-20260818
+```
+
+To reset the default history in place, remove it and rerun the import set:
+
+```bash
+b2c webdav rm --root=impex b2c-cli/import-sets/migrations
+b2c job import-set
+```
+
+For a custom set ID, replace the final `migrations` path segment with that ID. Resetting in place permanently forgets which archives succeeded and makes every current archive pending again, so only use it when every archive is safe to reapply. `--break-lock` is for recovery and does not reset history.
+
+For the canonical workflow, naming convention, retry behavior, and recovery rules, use the `b2c-cli:b2c-site-import-export` skill's **Apply an Ordered, Idempotent Import Set** section.
+
+### More Commands
+
+See `b2c webdav --help` for a full list of available commands and options in the `webdav` topic.
+
+## Related Skills
+
+- `b2c-cli:b2c-logs` - Filtered log retrieval, search, and real-time tailing (preferred for log exploration)
+- `b2c-cli:b2c-code` - Higher-level code deployment (preferred for cartridge upload)
+- `b2c-cli:b2c-site-import-export` - Canonical site archive and idempotent import-set guidance
+- `b2c-cli:b2c-job` - Run and monitor jobs

package/node_modules/@salesforce/b2c-agent-plugins/b2c-cli/skills/b2c-webdav/evals/trigger-evals.json

@@ -0,0 +1,12 @@
+[
+  {"query": "How do I upload a zip file to the IMPEX directory on my instance so I can run a site import job on it?", "should_trigger": true},
+  {"query": "I need to delete an old directory from the cartridges WebDAV root. How do I remove files remotely?", "should_trigger": true},
+  {"query": "Can I list the files on my sandbox instance and then download a specific export file to my local machine?", "should_trigger": true},
+  {"query": "I need to unzip an archive that's already on the instance in the IMPEX upload directory. Can I do that remotely?", "should_trigger": true},
+  {"query": "How do I create a new directory on the instance and upload multiple files into it?", "should_trigger": true},
+  {"query": "I want to check what's in the IMPEX share folder on our staging instance to see if the nightly export ran successfully.", "should_trigger": true},
+  {"query": "How do I tail the error logs on my sandbox in real time to debug a production issue?", "should_trigger": false},
+  {"query": "I want to deploy my cartridge code to the sandbox and activate the new code version.", "should_trigger": false},
+  {"query": "How do I trigger a site import job after uploading my data archive to the instance?", "should_trigger": false},
+  {"query": "I need to set up file watching so my local code changes auto-sync to the sandbox during development.", "should_trigger": false}
+]

package/node_modules/@salesforce/b2c-agent-plugins/b2c-experimental/skills/b2c-scaffold/SKILL.md

@@ -0,0 +1,168 @@
+---
+name: b2c-scaffold
+description: Generate B2C Commerce cartridges, controllers, hooks, custom APIs, job steps, and Page Designer components from scaffold templates. Use this skill whenever the user needs to create a new cartridge, add a controller or hook to an existing cartridge, bootstrap a custom API endpoint, or generate boilerplate for job steps or Page Designer components — even if they just say "create a new cartridge" or "I need a controller for loyalty".
+---
+
+# B2C Scaffold Skill
+
+Use the `b2c scaffold` commands to generate B2C Commerce components from templates.
+
+> **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead.
+
+## Examples
+
+### List Available Scaffolds
+
+```bash
+# list all scaffolds
+b2c scaffold list
+
+# list only cartridge scaffolds
+b2c scaffold list --category cartridge
+
+# show extended info (description, tags)
+b2c scaffold list -x
+```
+
+### Generate a Cartridge
+
+```bash
+# generate interactively
+b2c scaffold cartridge
+
+# generate with name
+b2c scaffold cartridge --name app_custom
+
+# generate to specific directory
+b2c scaffold cartridge --name app_custom --output ./src/cartridges
+
+# skip prompts, use defaults
+b2c scaffold cartridge --name app_custom --force
+
+# preview without creating files
+b2c scaffold cartridge --name app_custom --dry-run
+```
+
+### Generate a Controller
+
+```bash
+# generate interactively (prompts for cartridge selection)
+b2c scaffold controller
+
+# generate with all options
+b2c scaffold controller \
+  --option controllerName=Account \
+  --option cartridgeName=app_custom \
+  --option routes=Show,Submit
+```
+
+### Generate a Hook
+
+```bash
+# generate a system hook
+b2c scaffold hook \
+  --option hookName=validateBasket \
+  --option hookType=system \
+  --option hookPoint=dw.order.calculate \
+  --option cartridgeName=app_custom
+
+# generate an OCAPI hook
+b2c scaffold hook \
+  --option hookName=modifyBasket \
+  --option hookType=ocapi \
+  --option hookPoint=dw.ocapi.shop.basket.beforePOST \
+  --option cartridgeName=app_custom
+```
+
+### Generate a Custom API
+
+```bash
+# generate a shopper API
+b2c scaffold custom-api \
+  --option apiName=loyalty-points \
+  --option apiType=shopper \
+  --option cartridgeName=app_custom
+
+# generate an admin API
+b2c scaffold custom-api \
+  --option apiName=inventory-sync \
+  --option apiType=admin \
+  --option cartridgeName=app_custom
+```
+
+### Generate a Job Step
+
+```bash
+# generate a task-based job step
+b2c scaffold job-step \
+  --option stepId=custom.CleanupOrders \
+  --option stepType=task \
+  --option cartridgeName=app_custom
+
+# generate a chunk-based job step
+b2c scaffold job-step \
+  --option stepId=custom.ImportProducts \
+  --option stepType=chunk \
+  --option cartridgeName=app_custom
+```
+
+### Generate a Page Designer Component
+
+```bash
+b2c scaffold page-designer-component \
+  --option componentId=heroCarousel \
+  --option componentName="Hero Carousel" \
+  --option componentGroup=content \
+  --option cartridgeName=app_custom
+```
+
+### Get Scaffold Info
+
+```bash
+# see parameters and usage for a scaffold
+b2c scaffold info cartridge
+b2c scaffold info controller
+```
+
+### Search Scaffolds
+
+```bash
+# search by keyword
+b2c scaffold search api
+
+# search within a category
+b2c scaffold search template --category page-designer
+```
+
+### Create Custom Scaffolds
+
+```bash
+# create a project-local scaffold
+b2c scaffold init my-component --project
+
+# create a user scaffold
+b2c scaffold init my-component --user
+
+# validate a custom scaffold
+b2c scaffold validate ./.b2c/scaffolds/my-component
+```
+
+## Built-in Scaffolds
+
+| Scaffold | Category | Description |
+|----------|----------|-------------|
+| `cartridge` | cartridge | B2C cartridge with standard structure |
+| `controller` | cartridge | SFRA controller with routes and middleware |
+| `hook` | cartridge | Hook with hooks.json registration |
+| `custom-api` | custom-api | Custom SCAPI with OAS 3.0 schema |
+| `job-step` | job | Job step with steptypes.json registration |
+| `page-designer-component` | page-designer | Page Designer component |
+
+## Related Skills
+
+- `b2c-cli:b2c-code` - Deploy generated cartridges to B2C instances
+- `b2c:b2c-controllers` - SFRA controller patterns and best practices
+- `b2c:b2c-hooks` - B2C hook extension points
+- `b2c:b2c-custom-api-development` - Custom API development guide
+- `b2c:b2c-custom-job-steps` - Job step implementation patterns
+- `b2c:b2c-page-designer` - Page Designer component development

package/node_modules/@salesforce/b2c-agent-plugins/b2c-experimental/skills/b2c-scaffold/evals/trigger-evals.json

@@ -0,0 +1,12 @@
+[
+  {"query": "I'm starting a new loyalty feature and need a fresh cartridge called app_custom_loyalty with a controller and a hook wired up. What's the fastest way to set up the boilerplate?", "should_trigger": true},
+  {"query": "I need to add a new custom REST API endpoint for a loyalty points service. I want the boilerplate generated — the route definition, the schema, and the handler script. Can you set that up?", "should_trigger": true},
+  {"query": "I want to create a Page Designer component called heroCarousel for our homepage. I'd like to preview what files get created before actually writing them. How do I generate it?", "should_trigger": true},
+  {"query": "We're starting a new project and I need to generate two controllers — one for account pages and one for the wishlist feature — along with their corresponding ISML templates. Can you scaffold both at once?", "should_trigger": true},
+  {"query": "I need to wire up a new hook for the order placement flow. I want the hook definition, the registration in hooks.json, and a skeleton implementation script. What's the quickest way to generate all of that?", "should_trigger": true},
+  {"query": "I'm adding a scheduled job to our cartridge that processes abandoned carts. I need the step type definition and the skeleton module with the execute function. Can you generate the boilerplate files for a new job step?", "should_trigger": true},
+  {"query": "How do I push my cartridge code to a sandbox instance and activate the new code version?", "should_trigger": false},
+  {"query": "I'm implementing a batch job that processes orders in chunks. What's the read/process/write pattern and where does the step type definition go?", "should_trigger": false},
+  {"query": "I need to configure the attributes and rendering template for an existing Page Designer component. How do I add a new attribute group to the component's JSON definition?", "should_trigger": false},
+  {"query": "My controller is throwing an error when I try to call a model method. How do I debug the server-side script execution and check the request parameters?", "should_trigger": false}
+]

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/.codex-plugin/plugin.json

@@ -0,0 +1,39 @@
+{
+  "name": "b2c-ops",
+  "version": "1.9.0",
+  "description": "B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, and incident triage.",
+  "author": {
+    "name": "Salesforce"
+  },
+  "homepage": "https://salesforcecommercecloud.github.io/b2c-developer-tooling/",
+  "repository": "https://github.com/SalesforceCommerceCloud/b2c-developer-tooling",
+  "license": "Apache-2.0",
+  "keywords": [
+    "salesforce",
+    "b2c-commerce",
+    "operations",
+    "administration",
+    "runbooks",
+    "incident-triage"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "B2C Operations",
+    "shortDescription": "Job health and incident investigation runbooks.",
+    "longDescription": "Review scheduled work, investigate checkout and failed orders, and prepare evidence-backed handoffs using B2C Commerce tools.",
+    "developerName": "Salesforce",
+    "category": "Productivity",
+    "capabilities": [
+      "Read"
+    ],
+    "logo": "./assets/logo.svg",
+    "composerIcon": "./assets/logo.svg",
+    "brandColor": "#0D9DDA",
+    "websiteURL": "https://salesforcecommercecloud.github.io/b2c-developer-tooling/",
+    "defaultPrompt": [
+      "Review scheduled jobs and flag incomplete updates",
+      "Investigate checkout failures without changing the instance",
+      "Prepare a developer handoff for this incident"
+    ]
+  }
+}

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/README.md

@@ -0,0 +1,31 @@
+# B2C Operations Runbooks
+
+Agent skills for administrators, operators, and developers investigating B2C
+Commerce health and incidents. Available as the `b2c-ops` plugin and bundled in
+the B2C MCP. No demo workspace or application source is required.
+
+| Skill                      | Outcome                                                                                   |
+| -------------------------- | ----------------------------------------------------------------------------------------- |
+| `b2c-production-triage`    | Scope an incident, correlate evidence, and prepare a handoff.                             |
+| `b2c-job-health`           | Review scheduled work and investigate failed or incomplete updates.                       |
+| `b2c-checkout-triage`      | Investigate broader checkout/payment symptoms and select relevant evidence.               |
+| `b2c-order-failure-triage` | Enumerate FAILED orders, quantify impact, and correlate failed inputs with logs and jobs. |
+
+See the [Operations guide](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/operations)
+for setup and example requests. Direct plugin installation adds guidance; it
+does not grant access or install the MCP/CLI. MCP users need no separate install.
+
+## Adding a runbook
+
+Follow the repository's MCP development skill and workflow authoring reference.
+Create `skills/<task>/SKILL.md` with a descriptive trigger, observable outcome,
+MCP/CLI choices, bounded investigation, intervention checkpoint, and recovery or
+handoff. Put conditional detail in `references/`; keep each entry independently
+discoverable. Use installed skill names for native assistants and exact skill
+URIs for MCP. Verify capabilities against code and current contracts.
+
+Each addition needs an agent-plugin changeset and acceptance scenarios that
+include missing access and partial evidence. Update the Operations guide when
+it adds a capability worth highlighting; do not mirror the skill inventory there.
+Record tooling gaps separately; do not make a new tool just to mirror a runbook.
+Never include demo answers, tenant defaults, or customer data.