/service-helpagent-coordinate

name: service-helpagent-coordinate
description: "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)."
allowed-tools: Bash Read Write Edit Glob Grep WebFetch AskUserQuestion TodoWrite
metadata:
  version: "0.9"
  domains: ["Service", "Agentforce", "Experience"]
  minApiVersion: "67.0"
  relatedSkills:
    - "agentforce-generate"
    - "dx-org-permission-set-assign"
    - "experience-lwr-site-generate"
    - "integration-connectivity-connected-app-configure"
    - "platform-metadata-deploy"
    - "service-agentforce-channel-configure"
    - "service-agentforce-contact-center-coordinate"
    - "service-concierge-portal-generate"
    - "service-digital-engagement-channel-configure"
    - "service-digital-engagement-deployment-configure"
    - "service-digital-engagement-messaging-site-integrate"
  cliTools:
    - tool: ["curl"]
      semver: ">=7.0.0"
    - tool: ["sf"]
      semver: ">=2.139.6"
    - tool: ["python3"]
      semver: ">=3.8"

service-helpagent-coordinate: Service Cloud Help Agent, guided setup

Use this skill to stand up a **Service Cloud Help Agent** (an Agentforce Service Agent) on a Salesforce org from Claude Code, following the same guided flow as the Help Agent Quick Setup wizard. This is a **coordinate** skill: it orchestrates existing skills against a canonical spec — it does **not** author a new agent primitive.

Why this skill exists

Salesforce's official Help Agent template-creation API is not yet shipped. Without it, Claude has no built-in concept of "Help Agent" and would otherwise generate a generic agent. `assets/help-agent-spec.md` substitutes for the missing API: its agent script is the canonical template the eventual Quick Start UI will produce. Treat the spec as source of truth for the agent's lineage (topics, actions, instructions).

Scope

**In scope:**

• Guided, four-checkpoint Help Agent setup (identity → grounding → channel → go-live)
• Knowledge grounding via Agentforce Data Library (ADL)
• Web Chat / Help Portal channel setup and Experience Cloud site embed
• Readiness checks (licenses, Einstein Agent User, Data Cloud permission sets)

**Out of scope — delegate elsewhere:**

• OAuth / External Client App setup → [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md)
• Raw agent authoring with no Help Agent lineage → `agentforce-generate`
• Metadata deploy/retrieve → `platform-metadata-deploy`

Prerequisites

• Claude Code + Salesforce CLI installed and an authenticated org (see repo `README.md`)
• MCP servers registered: `salesforce-api-context`, `metadata-experts`, `sobject-reads`
• Salesforce Skills installed into `.agents/skills/` (or `.claude/skills/`)
• **A Salesforce org with the required features enabled (or enable-able via metadata):** Agentforce, Einstein Generative AI, Knowledge, Experience Cloud, and Data Cloud. Any org shape that meets this bar works — production, sandbox, scratch, or Developer Edition. The readiness check in `assets/help-agent-spec.md` §4.0 detects each feature and enables what can be enabled; it stops with a clear message if a required capability is missing and cannot be turned on.

Skills this coordinates

The spec feeds these existing skills — do **not** author a new Help Agent skill:

| Skill | Role | |---|---| | `agentforce-generate` | Agent authoring + ADL provisioning/grounding (see its `references/data-library-reference.md`, `references/org-setup-for-adl.md`) | | `dx-org-permission-set-assign` | Data Cloud permission-set assignment | | `service-digital-engagement-channel-configure` + `service-agentforce-channel-configure` | Deploy channel (Queue routing), then PATCH `SessionHandlerId` to bind agent (see `references/channel-web-chat.md`) | | `service-digital-engagement-deployment-configure` | Embedded Service Deployment — supports both LWR (`ChatterNetworkPicasso`) and Aura (`ChatterNetwork`) sites | | `experience-lwr-site-generate` | Experience Cloud (LWR) site — used when the org has no Live LWR site yet | | `service-digital-engagement-messaging-site-integrate` | Widget placement + embed (Checkpoint 4) |

Skills inventory pre-flight (advisory — never a hard stop)

This skill delegates to several sibling skills. Depending on the runtime, those dependencies resolve one of two ways: as directories under `.claude/skills/`, **or** through a runtime skill catalog that the harness resolves on demand (no local directory). An absent `.claude/skills/<name>` directory therefore does **not** prove a dependency is unavailable — it is normal when the catalog resolves skills at invocation time.

Run this check **once, silently, for your own awareness** — never as the run's first user-facing output:

for skill in agentforce-generate dx-org-permission-set-assign service-digital-engagement-channel-configure service-digital-engagement-deployment-configure experience-lwr-site-generate service-digital-engagement-messaging-site-integrate service-concierge-portal-generate service-agentforce-channel-configure; do
  [ -d ".claude/skills/$skill" ] && echo "OK: $skill" || echo "resolve-at-runtime: $sk