Skip to content

forcedotcom/sf-skills / plugins/builder/service-engagement/skills/service-helpagent-coordinate

service-helpagent-coordinate

Flagged

Use to set up, configure, ground, or go live with a Salesforce Help Agent (an Agentforce Service Agent in Service Cloud) via a guided four-checkpoint flow. Use whenever a user says any of: set up / create / build / add a help agent, service agent, or support chat agent; add or embed a chat widget on a website or Experience Cloud / LWR site; put a help agent on a channel (web chat, voice, phone, help portal); ground a help agent on Salesforce Knowledge; or wants an AI to answer customer questions, manage support cases, and escalate to a human. The right skill even when the request names only one part or references help-agent-spec.md or the Agentforce Quick Setup wizard. DO NOT TRIGGER when authoring a brand-new agent with no Help Agent lineage (use agentforce-generate), configuring OAuth/ECAs (use integration-connectivity-connected-app-configure), or only deploying metadata (use platform-metadata-deploy).

FileKindSize
README.mdmarkdown5.8 KB
SKILL.mdskill md28.5 KB
assets/help-agent-spec.mdmarkdown41.8 KB
references/agent-script.mdmarkdown45.4 KB
references/channel-voice.mdmarkdown2.4 KB
references/channel-web-chat.mdmarkdown19.9 KB
references/output-report-format.mdmarkdown16.4 KB
# service-helpagent-coordinate

A Claude Code skill that stands up a **Service Cloud Help Agent** (Agentforce ASA)
end-to-end on a Salesforce org, following the guided four-checkpoint flow of the
Help Agent Quick Setup wizard.

This is a **`-coordinate`** skill (per sf-skills taxonomy): it orchestrates existing
skills against a canonical spec — it does **not** author a new agent primitive.

## What's here

| Path | Contents |
|---|---|
| `SKILL.md` | The skill: scope, coordinated skills, and the four-checkpoint workflow |
| `assets/help-agent-spec.md` | The canonical Help Agent spec — the guided flow (source of truth), kept small |
| `references/agent-script.md` | The canonical agent script + placeholders; loaded only at agent-creation time |
| `references/channel-web-chat.md` | Web Chat channel provisioning detail; loaded only when Web Chat is chosen |
| `references/channel-voice.md` | Voice channel wiring detail (existing `PstnVoice` numbers only); loaded only when Voice is chosen |
| `references/output-report-format.md` | The two report shapes, templates, and scored-failure list; loaded when writing the final `report.md` |

Help Portal is delegated end-to-end to the sibling skill `service-concierge-portal-generate` — no per-channel reference file lives here for that branch.

The spec is split for **progressive disclosure**: the large agent script and the per-channel
branches live in `references/` and are read only when the flow reaches them, keeping the
always-loaded footprint small.

## Environment setup

Run these once per org before invoking the skill.

### Install and verify the tooling

```bash
claude --version
sf --version
```

Claude Code and the Salesforce CLI must both be installed.

### Activate MCP servers

Setup → Quick Find → **MCP Servers** (Integrations → API Catalog) → **Salesforce Servers** tab.
Activate both: `metadata-experts`, `sobject-reads`.

### Create an External Client App

Setup → **External Client App Manager** → **New External Client App**.

- **API (Enable OAuth Settings)** → Enable OAuth
  - Callback URL: `http://localhost:8080/callback`
  - Scopes: `Access Salesforce hosted MCP servers (mcp_api)` and `Perform requests at any time (refresh_token, offline_access)`
- **Security Settings**: uncheck *Require Secret for Web Server Flow* and *Require Secret for
  Refresh Token Flow*; check *Issue JWT-based access tokens for named users* and *Enable PKCE
  Extension for Authorization Code Flow*.
- Save → Settings → OAuth Settings → **Consumer Key and Secret** → copy the **Consumer Key**.

Claude Code is a public OAuth client — PKCE replaces the client secret. For the automated,
source-controlled ECA path (scopes + certificate/JWT), use the
`integration-connectivity-connected-app-configure` skill.

### Connect the CLI and register the MCP servers

```bash
sf org login web --alias <your-org-alias> --set-default
sf project generate --name help-agent --template standard
cd help-agent
```

Confirm the URL format on each server's detail page — if it contains
`/sandbox/platform/`, substitute that for `/platform/` below. Replace `<CONSUMER_KEY>` with the
key from the ECA:

```bash
claude mcp add salesforce-metadata-experts --transport http "https://api.salesforce.com/platform/mcp/v1/platform/metadata-experts" --callback-port 8080 --client-id <CONSUMER_KEY>
claude mcp add sobject-reads --transport http "https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads" --callback-port 8080 --client-id <CONSUMER_KEY>
claude mcp list
```

### Install Salesforce Skills

```bash
! npx skills add forcedotcom/sf-skills
```

Verify: `! ls .agents/skills/` and `! cat skills-lock.json`.

## Quick start

1. Complete **Environment setup** above.
2. Install this skill into your SFDX project:
   ```bash
   ! cp -R /path/to/service-helpagent-coordinate .agents/skills/service-helpagent-coordinate
   ```
3. In Claude Code:
   ```text
   I want to add a help agent to my Salesforce org so customers can get answers to
   common questions, manage their support cases, and reach a human agent when needed.
   I want it accessible as a chat widget on our customer website.
   ```
   The skill walks four checkpoints — identity → grounding → channel → go-live — waiting
   for your input at each. Nothing is built without confirmation.

## Status

- Tested on orgs with Data Cloud not yet provisioned — the readiness check enables Data
  Cloud (or hands off to the user to enable it) before proceeding. Any org shape that
  supports Agentforce + Data Cloud + Experience Cloud works.
- Creates an **Agentforce Service Agent** on the `QuickASA__QuickASA` template shape.
  This is the shape the eventual Help Agent Quick Start UI produces; treat it as the
  Help Agent lineage even though the official template-creation API is not yet shipped.

## Troubleshooting

- **MCP servers not connecting** — confirm the Consumer Key and the platform-vs-sandbox URL against the server detail page.
- **"No Einstein Agent User found"** — ask Claude Code to create one; it runs the CLI + permission-set steps.
- **Publish fails "Internal Error, try again later"** — `default_agent_user` in the `.agent` file doesn't match an active Einstein Agent User:
  ```bash
  sf data query --json -q "SELECT Username FROM User WHERE Profile.UserLicense.Name = 'Einstein Agent' AND IsActive = true"
  ```
- **OAuth doesn't redirect** — free port 8080 or pick another with `--callback-port` and update the ECA callback URL to match.

## Related

- ECA / OAuth setup skill: `integration-connectivity-connected-app-configure`
- Channel setup vs. final agent wiring: `service-digital-engagement-channel-configure` deploys and
  activates the MessagingChannel with initial Queue routing; `service-agentforce-channel-configure`
  then replaces that routing with the agent binding (fallback queue + `sessionHandlerAsa`). This
  skill coordinates both at Checkpoint 3.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated 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