Agent skill · forcedotcom
experience-portal-create
Create / provision / set up a NEW Digital Experience (Communities) / Experience Cloud site — employee service, IT support, help desk, HR, customer, and partner portals — via the headless-360 MCP site-creation APIs. Use whenever a user asks to create/provision/set up a portal, site, or community, e.g.: 'create an employee service portal', 'create an IT Support Portal', 'create an Agentforce Employee Center', including wiring MIAW (Messaging for In-App/Web) at create. This is the site-CREATION skill and OWNS provisioning a new Aura OR LWR Experience Builder site from scratch — trigger it even when the user says 'Experience Builder site' or 'LWR site', as long as a NEW site is wanted. It always writes a portal-creation report as its final step (never ad hoc via CLI) and never makes a legacy Tabs+Visualforce site. DO NOT TRIGGER only for modifying an EXISTING site's pages/routes/theme/branding/guest-access metadata (experience-lwr-site-generate), existing-site customization (experience-ui-bundle), CMS, Commerce.
What it needs
About 10k tokens when loaded.
What this skill does
Create Digital Experience Portal Create a new Digital Experience (formerly Communities) portal/site in Salesforce. Supports employee service portals, partner portals (PRM), and general customer communities. Every operation runs through the headless-360 MCP server (mcpheadless-360discover → mcpheadless-360describe → mcpheadless-360dispatch / mcpheadless-360dispatchreadonly). Do not use the Salesforce CLI (its api request, data query, or org open subcommands), the project-codey MCP server, raw curl, or any other HTTP client — dispatch/dispatchreadonly is the only way this skill talks to the org. See references/mcp-invocation.md for the exact call shapes. Scope In scope: Creating Digital Experience sites via the headless-360 Connect API dispatcher. Portal type selection. Basic configuration (name, URL, templates). Self-service portals with embedded service configs. Making the site reachable end to end — activating the Network (status: Live), adding member profiles, and publishing the Experience Builder pages (see references/post-creation-activate-publish.md). Out of scope: Deep post-creation customization (page layout/component authoring in Builder). Content authoring. Branding beyond initial setup. Individual per-user record management (membership is added at the profile/permission-set level, not per user). --- Execution model (read first) Every org call is a dispatch: mcpheadless-360dispatchreadonly(url, method: "GET", queryParams) for reads, mcpheadless-360dispatch(url, method, body) for writes; read statuscode + body from the response. To resolve the endpoint for a portal type, use mcpheadless-360discover(query=...) and mcpheadless-360describe(id=...) as needed. Connect API create/list operations for Experience Cloud are not always indexed by discover/describe — when a lookup returns nothing, dispatch the well-known versioned Connect API path directly (see references/mcp-invocation.md) rather than concluding the capability is missing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/experience-portal-create--f92aa3