Skip to content

forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-digital-engagement-channel-configure

service-digital-engagement-channel-configure

Verified

Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW). Use when the user needs to create, deploy, and activate a messaging channel configured with Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent routing. Generates MessagingChannel metadata, deploys it to the target org, and activates the channel with User Verification, pre-chat forms, automated responses, consent settings, and all customizable channel options via Metadata API. TRIGGER when the user mentions messaging channel, MIAW, enhanced chat, in-app messaging, web messaging setup, or references a .messagingChannel-meta.xml file. DO NOT TRIGGER when the user is configuring legacy Live Agent chat, Embedded Service deployments without messaging, or standard Omni-Channel routing rules without a messaging channel.

references/recaptcha_handoff.md

View on GitHub
# reCAPTCHA handoff

The reCAPTCHA key is not exposed through any API or Metadata field, so this skill cannot read, set, or verify it. An admin completes it in Setup; the skill hands over a link and the steps.

## Rules

- Never write `captchaKey` or `isCaptchaEnabled` in the channel XML. A full-document deploy preserves a key the admin already set in Setup, so redeploying never clobbers it.
- Never say reCAPTCHA is configured or enabled, or that it is not. Say this skill does not set or check it; the admin completes the steps below and sees the result in Setup.
- Give a plain Setup link only. Never run `sf org open --url-only` or output any URL carrying a session token (`frontdoor`, `sid=`); those are credentials.
- The reCAPTCHA Verification section is hidden for Mobile-only channels. Do not offer these steps for a channel the user says is Mobile-only.

## When to raise it

- The user asks about reCAPTCHA, captcha, or bot protection: give the full handoff.
- Standalone, at the end of the output, unless the user said the channel is Mobile-only: one line, "This skill does not set or check reCAPTCHA; ask me for the Setup steps."
- Delegated: do not raise it.

## Build the link

1. Get the channel Id:
   ```bash
   sf data query -o <org> --json -q "SELECT Id FROM MessagingChannel WHERE DeveloperName='<CHANNEL_DEV_NAME>'"
   ```
2. Path: `/lightning/setup/LiveMessageSetup/<ChannelId>/view?lightning__channelType=EmbeddedMessaging`. Prefix it with the org's `instanceUrl` if known (`result.instanceUrl` from `sf org display --json`; never print or copy the access token), otherwise give the path.

3. No channel Id yet (the query returns no row, or the channel is not deployed): never deploy only to get one. Give the generic route, Setup → Messaging Settings → open the channel, with the admin steps below, and carry on with the rest of the flow.

## Limitation to tell the user

The link is plain, so it works only if the admin is already logged in to the org with Setup access. If not, they should log in first and then open the link, or go to Setup → Messaging Settings and open the channel.

## Admin steps

1. Have the reCAPTCHA key pair from Google ready.
2. Open the link and find the **reCAPTCHA Verification** section.
3. Check **Use reCAPTCHA** first. The **reCAPTCHA API Key Pair** field and **New API Key Pair** button stay greyed out until it is checked.
4. Select an existing key in **reCAPTCHA API Key Pair**, or click **New API Key Pair** and add yours.
5. Save. Setup does not allow saving with the box checked until a key pair is set.
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