Repository navigation
Conversation
Orchestrator skill for sandbox and realm setup (storefront datasets, search indexes, Storefront Next storefronts, replication) with confirmation before changes to shared instances. Featured in the MCP skill listing and server instructions.
clavery
requested review from
patricksullivansf,
wei-liu-sf and
yhsieh1
as code owners
October 30, 2026 15:45
Contributor
📘 Docs previewYour documentation changes are published at: https://d3uhw92m2zac57.cloudfront.net/pr-835/ Commit This preview updates on every push and is removed when the PR is closed. |
clavery
had a problem deploying
to
b2c-docs-preview
October 30, 2026 15:57 — with
GitHub Actions
Error
clavery
had a problem deploying
to
b2c-docs-preview
October 30, 2026 16:04 — with
GitHub Actions
Error
Cover the API client and scopes for CLI storefront creation, generating project code with create-storefront, and getting the .env file (one-time Business Manager download, or rebuilding non-secret values from the instance) in the b2c-setup skill and the Storefront Next guide.
…refront The skills drift test rejects b2c sfnext create-storefront (a JIT plugin command), and the Storefront Next CLI reference documents only pnpm dlx.
…setup b2c am clients create now shows the client's details and asks for confirmation (--force skips it; required with --json or when not interactive), and defaults the token endpoint auth method to client_secret_basic so new clients work with their secret. Skills and docs explain how to create an API client with the user's own sign-in, and require agents to confirm every detail with the user first.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a
b2c-setupskill: one place to start when setting up a new sandbox or realm. The skill has three parts:Safety comes first. The assistant identifies the instance by hostname, not configuration name. Before each change to staging, production or development, it names the instance and the command and waits for approval. Production and development get data by replication, never by direct import. The skill also recommends a Safety Mode policy for each shared instance.
The MCP server now features the skill:
b2c-mcp-serverskill index.A new Realm Setup guide is first under Operations & Administration and covers the same flow for users. Operations, Storefront Next, Safety Mode and the sibling skills (sandbox, site import/export, storefronts, replication) link to it or to the skill.
Testing
Manual:
b2c-setupappears in the skill listing. Then ask to "set up my new realm" and check that the assistant loads the skill and asks before each change to staging or production.