Skip to content

forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-digital-engagement-messaging-site-integrate

service-digital-engagement-messaging-site-integrate

Verified

Integrates a Messaging for In-App and Web (MIAW) Embedded Messaging chat widget into an Experience Cloud site by patching the site's LWR or Aura page bundle, deploying, publishing, and verifying guest access. Use when the user wants to embed messaging on an Experience site, add a chat widget to a community, place the Embedded Messaging component on an LWR or Aura page, wire an embedded service deployment to a site, references the retrieved bundle artifacts (`content.json`, `homeGuestLayout.json`, or a `*.site-meta.xml` file), or automates the retrieve/patch-JSON/deploy/publish flow instead of clicking through Experience Builder. DO NOT TRIGGER when creating the messaging channel (use service-digital-engagement-channel-configure), when creating or updating the EmbeddedServiceConfig deployment (use service-digital-engagement-deployment-configure), or when generating a standalone JavaScript snippet for a non-Experience website.

FileKindSize
SKILL.mdskill md16.9 KB
references/aura_patch.mdmarkdown2.4 KB
references/bundle_detection.mdmarkdown2.5 KB
references/deploy_and_publish.mdmarkdown3.6 KB
references/lwr_patch.mdmarkdown3.7 KB
references/lwr_route_scaffolding.mdmarkdown1.8 KB
references/manual_fallback.mdmarkdown3.0 KB
scripts/detect_bundle_type.shexecutablescript1.1 KB
scripts/patch_aura_bundle.shexecutablescript4.1 KB
scripts/patch_lwr_bundle.shexecutablescript7.3 KB

references/lwr_route_scaffolding.md

View on GitHub
# LWR Route Scaffolding — Delegation

Some LWR site templates declare route types in their theme that the retrieved bundle does not contain (commonly `too-many-requests`). If a required route is missing at deploy time, the deploy fails with a route-type validation error.

Route + view creation is owned by **`experience-lwr-site-generate`**. This skill does not duplicate that procedure. Delegate to that skill and pass through the messaging-specific context.

## When to invoke the delegate

Trigger the delegation when the messaging-widget deploy in Phase 4 fails with a missing-route or missing-view error mentioning a `routeType` that is not present under `digitalExperiences/site/<siteName>/sfdc_cms__route/`.

## What to hand off

Give `experience-lwr-site-generate` these three items:

- **Site name** — `<siteName>` (same value used throughout this skill).
- **Route type reported by the deploy error** — e.g. `too-many-requests`.
- **Retrieve directory** — `<retrieve-dir>` so the scaffolded pair lands next to the existing route/view directories.

The delegate skill covers the full procedure: `configure-content-route.md` (route file shape), `configure-content-view.md` (view file shape), and `handle-component-and-region-ids.md` (fresh-UUID stamping so the scaffolded view does not collide with existing IDs).

## Messaging-specific delta

After the delegate returns, verify the specific deploy error is cleared before proceeding:

```bash
sf project deploy validate --source-dir force-app/main/default --target-org <org-alias>
```

If the validation surfaces additional missing route types, re-invoke the delegate for each. Only proceed to Phase 4's real deploy once validation passes.

If the delegate is unavailable, fall back to Phase 6's manual Experience Builder path — do **not** attempt to scaffold routes ad-hoc from this skill.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall