education-cloud-student-recruitment-agent-configure

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Configuring the Education Cloud Student Recruitment Agent

配置Education Cloud Student Recruitment Agent

Scope

范围

In scope: The full SRA setup sequence — the three platform toggles (Einstein, SRA, Omni-Channel; Agentforce provisioning is a verify-only Step-1 gate, not a toggle the skill flips), the
```
EducationCloudAiAgentAccess
```
permission set + OWD/sharing foundation, Learning Program grounding (Data Cloud data stream + hybrid search index + prompt template) and Knowledge/data-library grounding, creating the Service (unauth) and Employee (auth) agents, adding the 4 packaged SRA subagents, building the customer escalation subagent, cloning and configuring the 6 admissions flows (Service path), and deploying to Experience Cloud channels with user verification.
Out of scope: The Transfer Credit Agent (separate agent, own perms/help — never include its steps); generic Agentforce agent authoring from scratch (see Cross-Skill Integration below); Data Cloud connector plumbing beyond the SRA grounding path; deciding the substance of Knowledge article content — Claude may draft an article for the customer to review, but the customer owns what it says.
The EDU foundation is a checked dependency, not an assumption: SRA depends on base Education Cloud enablement, Person Accounts, R&A domain objects, and Data Cloud. This skill doesn't re-implement base Education Cloud domain enablement, but verifies each piece concretely (step 2a) and only surfaces a gap to the user to fill what it detects.

包含范围：完整的SRA设置流程——三个平台开关（Einstein、SRA、Omni-Channel；Agentforce配置仅为步骤1的验证关卡，并非本技能可切换的开关）、
```
EducationCloudAiAgentAccess
```
权限集+OWD/共享基础、Learning Program grounding（Data Cloud数据流+混合搜索索引+提示模板）以及知识库/数据库grounding、创建服务端（未授权）和员工端（授权）代理、添加4个打包的SRA子代理、构建客户升级子代理、克隆并配置6个招生流（服务路径），以及部署到Experience Cloud渠道并进行用户验证。
排除范围：Transfer Credit Agent（独立代理，拥有专属权限/帮助文档——切勿包含其步骤）；从头开始的通用Agentforce代理创作（见下文跨技能集成）；SRA grounding路径之外的Data Cloud连接器配置；决定知识库文章的内容实质——Claude可起草文章供客户审核，但内容最终由客户决定。
EDU基础是已验证的依赖项，而非假设：SRA依赖于基础Education Cloud启用、个人账户、R&A域对象以及Data Cloud。本技能不会重新实现基础Education Cloud域启用，但会具体验证每一项（步骤2a），仅向用户指出检测到的缺口并要求其填补相应内容。

Required Inputs

必要输入

Gather or infer before starting:

Target org: An Agentforce- and Education-Cloud-provisioned org with admin access — see Workflow step 1 for the gate.
Agent path(s): Unauthenticated (Service agent — the ASA, runs as the Einstein Agent User service account; no guest user), authenticated (Employee agent), or both.
Which subagents/topics the customer wants live (default: all 4 packaged subagents + a custom escalation subagent).
Whether to add Create Inquiry to the Escalation subagent (case-adjacent record creation on live-agent handoff) — ask if unspecified; the two outcomes are handoff-only, or handoff-plus-Create-Inquiry.

Defaults unless specified:

Configure both agent paths if the org has both Service and Employee Agentforce licenses; otherwise the unauth/Service path only.
Confirmation style: conversational, one-step-at-a-time — never autonomous. See Talking to the user below.

开始前需收集或推断以下信息：

目标组织：已配置Agentforce和Education Cloud且拥有管理员权限的组织——见工作流步骤1的关卡要求。
代理路径：未授权（服务端代理——即ASA，以Einstein Agent User服务账户运行；无访客用户）、授权（员工端代理），或两者兼具。
客户希望启用的子代理/主题（默认：所有4个打包的子代理+一个自定义升级子代理）。
是否在升级子代理中添加创建咨询记录功能（转接人工客服时创建相关案例记录）——若未指定则询问用户；两种结果为仅转接，或转接+创建咨询记录。

未指定时的默认设置：

如果组织同时拥有服务端和员工端Agentforce许可证，则配置两种代理路径；否则仅配置未授权/服务端路径。
确认方式：对话式、分步进行——绝不自动执行。见下文与用户沟通部分。

How this skill runs — read first

本技能运行方式——请先阅读

Step 0 resolves the org's current API version; Step 1 is a hard prerequisites gate — clear both before touching anything else. The rest is a linear, sequential set of steps (0–13); confirm before every irreversible or org-shaping action, and end every step with its verify call. (See Talking to the user below.)

Every org-changing step walks a three-tier ladder, then verifies — tier = what runtime you have: T1 headless MCP (

dispatch

dispatch_readonly

, no shell) · T2

sf

CLI (needs a shell) · T3 Setup UI. Try T1; drop to T2 on a route/allowlist failure; T3 if no shell. Steps carry a best-tier tag; the verify-only preflight (step 1) uses STOP/ASK-USER labels instead.

references/execution-model.md

has the ladder detail — allowlist, route signals, query-routing, API-version policy; read it whenever a tier or route is unclear.

Several steps land on T3 with no tier-1/tier-2 write path at all (hand the user the Setup path, then verify) — each is tagged inline where it occurs (e.g.

[T3 · ...]

on steps 8, 9a, 12); every other action has a tier-1 path.

步骤0解析组织当前的API版本；步骤1为硬性前置条件关卡——在执行任何其他操作前需先通过这两个步骤。 其余为线性顺序步骤（0–13）；在执行任何不可逆或影响组织架构的操作前需确认，且每个步骤结束后都要进行验证调用。（见下文与用户沟通部分。）

每个修改组织的步骤都遵循三级阶梯，然后进行验证——层级取决于您拥有的运行环境： T1 无头MCP（

dispatch

dispatch_readonly

，无shell）· T2

sf

CLI（需要shell）· T3 设置UI。优先尝试T1；若路由/白名单失败则降级到T2；若无shell则使用T3。步骤带有最佳层级标签；仅验证的预检步骤（步骤1）使用STOP/ASK-USER标签而非层级标签。

references/execution-model.md

包含阶梯详情——白名单、路由信号、查询路由、API版本策略；当对层级或路由有疑问时请阅读该文档。

有几个步骤只能使用T3，没有T1/T2的写入路径（为用户提供设置路径，然后进行验证）——每个此类步骤都会在文中标记（例如步骤8、9a、12中的

[T3 · ...]

）；其他所有操作都有T1路径。

Talking to the user — customer-facing narration (not optional)

与用户沟通——面向客户的说明（必填）

Mandatory, every run: read
references/customer-narration.md
in full before your first message to the customer — this is not background reading, it's the exact wording rules you follow at every step boundary for the entire session. In short: the step numbers, tier tags (

T1

T2

T3

), and words like "gate," "the spine," or "per the doc" are internal authoring scaffolding — never say them to the customer, who has no idea this skill file exists. Lead every step boundary with the plain-language outcome, not the internal label; give a manual (UI) hand-off its complete concrete detail in the same message that asks the customer to go do it; and before every single create/update/delete, no matter how small, explain what it does and why in plain language, then wait for an explicit go-ahead — never on silence, never batched.

references/customer-narration.md

has the exact phrasing table and the do/don't examples — read it now.

每次运行都必须执行：在向客户发送第一条消息前，完整阅读
references/customer-narration.md
——这并非背景阅读，而是整个会话中每个步骤边界必须遵循的措辞规则。简而言之：步骤编号、层级标签（

T1

T2

T3

）以及“关卡”“核心”“根据文档”等词汇均为内部创作框架——切勿向客户提及，因为客户并不知晓本技能文件的存在。每个步骤边界都应以通俗易懂的结果说明开头，而非内部标签；在要求客户执行手动（UI）操作的消息中，需同时提供完整具体的操作细节；并且在执行任何创建/更新/删除操作前，无论操作多小，都要用通俗易懂的语言解释操作内容及原因，然后等待用户明确同意——绝不能默认沉默即为同意，也不能批量操作。

references/customer-narration.md

包含确切的措辞表及注意事项示例——请立即阅读。

Workflow

工作流

All steps are sequential. Each step is one action + its best tier + a pointer to the reference that carries the exact calls, API names, and traps — read that reference before executing the step. Confirm before irreversible actions; end every step with its verify call.

所有步骤均按顺序执行。每个步骤包含一项操作+最佳层级+指向参考文档的链接（该文档包含确切的调用、API名称及注意事项——执行步骤前请阅读参考文档）。执行不可逆操作前需确认；每个步骤结束后都要进行验证调用。

0 — Resolve the org's current API version

0 — 解析组织当前的API版本

Do this first — before Step 1, before any other call in the run. Every
vXX
used in every step and reference file below comes from this resolution; never substitute a remembered or hardcoded version. CRITICAL: If this session has more than one Salesforce connection available, pin whichever one you use for this call as the org connection for the rest of the run — including after a context compaction. A compacted summary can lose track of which connection was active; don't let that cause a switch to a different one partway through.

Resolve the current API version [T1] —
```
dispatch_readonly({"url": "/services/data/", "method": "GET"})
```
on the org connection you're pinning for this run → take the highest numeric
version
from the returned array and reuse that literal, on that same connection, for every
```
vXX
```
call for the rest of this run. A stale/hardcoded version can make a real entity or feature absent from a schema-catalog read and misread as "the org doesn't have this." Full rationale and the per-surface version-floor exceptions:
```
references/execution-model.md
```
.

请首先执行此操作——在步骤1之前，在本次运行中的任何其他调用之前。以下所有步骤和参考文件中使用的每个
vXX
均来自此解析结果；切勿使用记忆中的版本或硬编码版本。关键提示：如果本次会话有多个Salesforce连接可用，请将用于此调用的连接固定为本次运行的组织连接——包括上下文压缩之后。压缩后的摘要可能会丢失对活动连接的跟踪；切勿让这种情况导致中途切换到其他连接。

解析当前API版本 [T1] — 在您固定的组织连接上执行
```
dispatch_readonly({"url": "/services/data/", "method": "GET"})
```
→ 从返回的数组中获取数值最高的
version
，并在本次运行的所有
```
vXX
```
调用中重复使用该版本，且始终使用同一个连接。过时/硬编码的版本可能会导致架构目录读取中遗漏真实实体或功能，并误判为“组织不具备此功能”。完整原理及各层面版本下限例外情况：
```
references/execution-model.md
```
。

1 — Verify prerequisites & gates

1 — 验证前置条件与关卡

Step 1 is a hard gate — clear it before enabling or building anything. If a STOP check (external grant the skill can't flip) or an ASK-USER check (foundation the skill doesn't own) fails, do not start the toggles or the foundation build — stop and request the grant, or have the user complete the missing Education Cloud foundation setup, then re-verify. Also confirm now, before saying anything to the customer:
references/customer-narration.md
has been read in full this run (see Talking to the user above) — this gate isn't cleared until that's true too. Don't build permissions/OWD/grounding for an agent that can't exist. Full preflight-gate table and every verify call:
references/prerequisites.md
.

Confirm edition & the Einstein-for-EDU license. Both are STOP checks — halt if either is missing. (Agentforce provisioning is verified in item 2; Data Cloud in item 2a.)
Verify the three SRA gates — Agentforce provisioning, Education Cloud enabled, and the runtime
```
orgHasStudentRecruitmentAgentBetaAccess
```
check (a three-part AND — its exact composition and per-part verify live in
```
references/prerequisites.md
```
). Stop if provisioning, the license, or the Gater is missing.
- 2a — Verify the EDU foundation (don't assume base Education Cloud domain enablement has run): EDU enablement, Person Accounts, R&A domain schema, and Data Cloud. Ask the user to complete the first three, then re-verify; Data Cloud is a Home-Org grant (that's a STOP, not something the user can self-serve).

步骤1为硬性关卡——通过后才能启用或构建任何内容。 如果STOP检查（本技能无法切换的外部授权）或ASK-USER检查（本技能不负责的基础设置）未通过，请勿开始开关启用或基础构建——停止操作并请求授权，或让用户完成缺失的Education Cloud基础设置，然后重新验证。另外，在向客户发送任何消息前请确认：本次运行已完整阅读
references/customer-narration.md
（见上文与用户沟通部分）——只有确认后此关卡才算通过。 切勿为无法存在的代理配置权限/OWD/grounding。完整预检关卡表及所有验证调用：
references/prerequisites.md
。

确认版本及Einstein-for-EDU许可证。 两者均为STOP检查——若缺少任何一项则停止操作。（Agentforce配置在第2项中验证；Data Cloud在第2a项中验证。）
验证三个SRA关卡——Agentforce配置、Education Cloud已启用，以及运行时
```
orgHasStudentRecruitmentAgentBetaAccess
```
检查（三项需同时满足——确切组成及各部分验证方式见
```
references/prerequisites.md
```
）。若配置、许可证或Gater缺失则停止操作。
- 2a — 验证EDU基础（请勿假设基础Education Cloud域已启用）：EDU启用、个人账户、R&A域架构以及Data Cloud。要求用户完成前三项，然后重新验证；Data Cloud为Home-Org授权（属于STOP检查，无法由用户自助完成）。

2 — Enable the platform toggles

2 — 启用平台开关

Enable the three platform toggles [T1] — each has its own write path: Einstein Setup (
```
EinsteinGPTPlatformEnabled
```
),
```
RecruitmentAgentEnabled
```
, and Omni-Channel (
```
OmniChannelSettings
```
— required for channel deploy). →
```
references/platform-enablement.md
```

启用三个平台开关 [T1] — 每个开关都有独立的写入路径：Einstein设置（
```
EinsteinGPTPlatformEnabled
```
）、
```
RecruitmentAgentEnabled
```
以及Omni-Channel（
```
OmniChannelSettings
```
——渠道部署必需）。→
```
references/platform-enablement.md
```

3 — Permissions & sharing foundation

3 — 权限与共享基础

→

references/permissions.md

Clone + configure the persona permission sets, and assign the builder persona [T1] — the OOTB
```
EducationCloudAiAgentAccess
```
is an empty shell, so clone it and customize its object/field matrix (assign the clone, never per-topic). Assign the Admin/builder persona to the running user before cloning — it grants the EDU field visibility the matrix build needs. Auth/Employee path only: also clone + configure
```
EducationCloudExprcCloudAccess
```
(Run Flows + object settings) for the community persona. The Einstein-user assignment is agent-dependent — Claude creates that user itself and grants it at step 9. The community-user assignment (and Enable Agent Access) is likewise agent-dependent → step 10.
Set OWD to Public Read Only on the 6 admissions objects [T1 · one UI exception].
Do the topic-specific prep — 5 blocks [T1 · two UI exceptions]: Campaign "Recruitment Event" picklist value + "Campus Tours" sharing rule, the Individual Application record type + its
```
ApplicationRecordTypeConfig
```
, and record-type→profile visibility.

→

references/permissions.md

克隆并配置角色权限集，分配构建者角色 [T1] — 原生
```
EducationCloudAiAgentAccess
```
为空壳，因此需克隆并自定义其对象/字段矩阵（分配克隆后的权限集，而非按主题分配）。在克隆前将管理员/构建者角色分配给当前用户——这将授予构建字段矩阵所需的EDU字段可见性。仅授权/员工端路径： 同时克隆并配置
```
EducationCloudExprcCloudAccess
```
（运行流+对象设置）用于社区角色。Einstein用户分配取决于代理类型——Claude会自行创建该用户并在步骤9中授予权限。社区用户分配（及启用代理访问）同样取决于代理类型 → 步骤10。
将6个招生对象的OWD设置为公共只读 [T1 · 一项UI例外]。
完成主题特定准备——5个模块 [T1 · 两项UI例外]：Campaign的“Recruitment Event”选择列表值+“Campus Tours”共享规则、Individual Application记录类型+其
```
ApplicationRecordTypeConfig
```
，以及记录类型→配置文件可见性。

4 — Grounding (two independent mechanisms)

4 — Grounding（两种独立机制）

→

references/grounding.md

Set up Knowledge grounding [T1 · article authoring is human] — check for existing Knowledge articles first and always ask the customer before drafting anything (never auto-create — see
```
references/grounding.md
```
7a), then create the Knowledge-sourced data library. Attaching it to the agent happens at step 9 (a top-level AFScript field, wired into the same draft-only pass — no need to wait for the agent to be committed); the create itself needs no agent. Once wired, newly published articles are picked up automatically — no re-wire per article.
Wire Data Cloud grounding — 3 grounded objects, 2 search-index/retriever builds (Learning Program; Academic Term shares the PTAT build) [T1 data spine · T3 index/retriever/prompt build].

→

references/grounding.md

设置知识库grounding [T1 · 文章创作由人工完成] — 始终先检查现有知识库文章，且在起草任何内容前询问客户（绝不自动创建——见
```
references/grounding.md
```
第7a节），然后创建基于知识库的数据库。将其附加到代理的操作在步骤9中完成（作为顶级AFScript字段，在同一次草稿传递中连接——无需等待代理提交）；创建操作本身无需依赖代理。连接完成后，新发布的文章会自动被识别——无需为每篇文章重新连接。
连接Data Cloud grounding——3个grounded对象，2个搜索索引/检索器构建（Learning Program；Academic Term共享PTAT构建）[T1 数据核心 · T3 索引/检索器/提示构建]。

5 — Agent, subagents & flows

5 — 代理、子代理与流

Create the agent(s) — headless, draft only [T1] — fetch the real base template (Service: "Agentforce Service Agent", Employee: "Agentforce Employee Agent"), and in one combined pass: resolve
```
NEW_AGENT_USER
```
by creating the ASA's Einstein Agent User + granting it full perm/license parity (ASA only), strip the 7 default topics incl. the default Escalation topic (ASA only), author a handoff-only Escalation subagent (both paths — no Create Inquiry yet), and wire the step-7 knowledge library (both paths). Stop at
```
compile
```
— do not
publish
; UI fallback available at T3. →
```
references/agent-and-subagents.md
```
- If step 8's Data Cloud data spine was deferred while streams were still provisioning, check back on it now. If it's still provisioning, check again at the end of each subsequent step (9a, 10, 11, 12) — it must be finished, including the T3 index/retriever/prompt-template build, before step 13's final verify. See
```
references/grounding.md
```
  Mechanism 2 step 3.
- 9a — The customer's one Builder session [T3 · Asset Library + Builder UI] — open the draft agent and: add the 4 packaged SRA subagents (Admissions and Enrollments FAQ; Admissions Application; Campus Tours, Visits, and Events Registration; Request for Information) from the Asset Library so the correct action
```
source
```
  /
```
target
```
  is set (not hand-authorable; watch for
```
TransferCreditEquivalency
```
  in that list — Transfer Credit Agent's, not SRA's); delete the Create Admissions Application action (non-functional — confirm with the customer first); add Create Inquiry to the Escalation subagent via Builder's action picker per the Required Inputs choice, or skip it for handoff-only (left out at step 9 — its input mapping isn't safe to hand-author blind). Then Save, then Commit Version — once; nothing from step 9/9a is queryable before that. →
```
references/agent-and-subagents.md
```
AEA/Employee-only: enable community access [T1 write] — skip entirely on an ASA/Service-only build; the ASA path has nothing left here (topic cleanup, escalation authoring, knowledge, running-user grants all happen in step 9). Set Enable Agent Access → the AEA agent on the
```
SRA_Exprc_Cloud_Access
```
clone (built at step 4), then query existing community users and ask before assigning the clone + sibling PSs to them. →
```
references/agent-and-subagents.md
```
&
```
references/permissions.md
```
Clone and configure the 6 admissions flows — unauthenticated/Service path only [T1]. Two waves: clone + activate the wave-1 flows first — the 2 reusable subflows plus the 1 standalone flow (
```
GetPlnCampaigns
```
, which has no dependencies) — then clone the 3 consumers and re-point them at the active subflow clones. Skip entirely if building only the Employee agent. →
```
references/flows.md
```

创建代理——无头模式，仅草稿状态 [T1] — 获取真实基础模板（服务端："Agentforce Service Agent"，员工端："Agentforce Employee Agent"），并在一次合并操作中：通过创建ASA的Einstein Agent User并授予其完整权限/许可证对等性来解析
```
NEW_AGENT_USER
```
（仅ASA），移除7个默认主题包括默认升级主题（仅ASA），编写仅转接的升级子代理（两种路径——暂不添加创建咨询记录功能），并连接步骤7中的知识库（两种路径）。在
```
compile
```
步骤停止——请勿执行
publish
；T3提供UI备选方案。→
```
references/agent-and-subagents.md
```
- 如果步骤8的Data Cloud数据核心因数据流仍在配置而延迟，请现在检查其状态。 如果仍在配置，在后续每个步骤（9a、10、11、12）结束时再次检查——必须在步骤13的最终验证前完成，包括T3的索引/检索器/提示模板构建。见
```
references/grounding.md
```
  机制2步骤3。
- 9a — 客户专属构建会话 [T3 · 资源库+构建者UI] — 打开草稿代理并：从资源库添加4个打包的SRA子代理（招生与入学常见问题；入学申请；校园参观、访问及活动注册；信息咨询），以设置正确的操作
```
source
```
  /
```
target
```
  （无法手动编写；注意列表中的
```
TransferCreditEquivalency
```
  ——属于Transfer Credit Agent，而非SRA）；删除创建入学申请操作（无法正常工作——请先与客户确认）；根据必要输入中的选择，通过构建者的操作选择器为升级子代理添加创建咨询记录功能，或跳过该功能以仅保留转接（步骤9中未包含——其输入映射无法安全手动编写）。然后保存，然后提交版本——仅执行一次；步骤9/9a中的内容在提交前无法查询。→
```
references/agent-and-subagents.md
```
仅AEA/员工端：启用社区访问 [T1 写入] — 若仅构建ASA/服务端代理则完全跳过此步骤；ASA路径在此处无剩余操作（主题清理、升级创作、知识库、运行用户授权均在步骤9中完成）。在克隆的
```
SRA_Exprc_Cloud_Access
```
（步骤4中构建）上设置启用代理访问→AEA代理，然后查询现有社区用户并在分配克隆的权限集及关联权限集前询问用户。→
```
references/agent-and-subagents.md
```
&
```
references/permissions.md
```
克隆并配置6个招生流——仅未授权/服务端路径 [T1]。分两波进行：首先克隆并激活第一波流——2个可重用子流+1个独立流（
```
GetPlnCampaigns
```
，无依赖），然后克隆3个消费流并将其重新指向已激活的子流克隆。若仅构建员工端代理则完全跳过此步骤。→
```
references/flows.md
```

6 — Deploy to channels & route

6 — 部署到渠道并路由

→

references/routing.md

Deploy each agent to its channel + stand up Omni-Channel routing [T1 routing objects · T3 messaging deployment & site] — read what exists first; front-load Experience Cloud site creation for any agent that doesn't already have one (the slowest part of this stack), then build the routing config → queue → inbound flow → channel stack while it provisions, then come back to the site to add the component and publish. One agent per channel = separate sites. Auth/Employee path: also enable user verification inline (two checkboxes, channel + site component; the unauthenticated/Service path gets neither).
Final structural verification [verify] — run the queryable roll-up (agent active, all subagents present, flows active, channel + site up), then summarize which tier each step landed on and list anything left manual. Finish here — do not wait on any manual action. The conversational smoke test (messaging the agent so subagents respond, grounding answers, actions produce records) needs a live channel session that can't be driven headlessly; hand the user that short checklist to run themselves and don't poll for its results.

→

references/routing.md

将每个代理部署到对应渠道并搭建Omni-Channel路由 [T1 路由对象 · T3 消息部署及站点] — 先读取现有内容；为任何尚未拥有Experience Cloud站点的代理优先创建站点（此为整个流程中最慢的部分），然后在站点配置期间构建路由配置→队列→入站流→渠道栈，之后返回站点添加组件并发布。一个代理对应一个渠道=独立站点。授权/员工端路径： 同时启用内联用户验证（两个复选框，渠道+站点组件；未授权/服务端路径无需启用）。
最终结构验证 [验证] — 运行可查询的汇总检查（代理已激活、所有子代理已存在、流已激活、渠道+站点已上线），然后总结每个步骤使用的层级，并列出所有仍需手动完成的项目。在此结束——无需等待任何手动操作。 对话式冒烟测试（向代理发送消息以验证子代理响应、grounding答案、操作生成记录）需要实时渠道会话，无法无头驱动；请向用户提供该简短检查清单供其自行执行，无需轮询结果。

Rules / Constraints

规则/约束

Constraint	Rationale
Never promise a rollback you haven't confirmed	Reversibility differs per toggle — see `references/platform-enablement.md` ; warn before any flip
Knowledge articles must be Published and contain no non-public data	The FAQ action is public; draft articles make the agent answer "no information"
Always confirm before any create/update/delete; run every step and its verify yourself — never delegate any part of this workflow to a separate helper process	See Talking to the user — the confirmation model depends on one continuous conversation; a delegated helper can prompt the customer on its own. polling isn't delegation
Do not deploy or push metadata packages	This skill configures a live org; package deployment belongs to a separate lifecycle skill

约束	理由
绝不承诺未确认可回滚的操作	每个开关的可逆性不同——见 `references/platform-enablement.md` ；切换前需发出警告
知识库文章必须已发布且不含非公开数据	FAQ操作为公开操作；草稿文章会导致代理回复“无相关信息”
执行任何创建/更新/删除操作前均需确认；自行完成每个步骤及其验证——绝不将工作流的任何部分委托给单独的辅助流程	见与用户沟通部分——确认模式依赖于连续对话；委托的辅助流程可能会自行提示客户。轮询不属于委托
请勿部署或推送元数据包	本技能用于配置实时组织；包部署属于单独的生命周期技能

Gotchas

常见问题

Issue	Resolution
Org can't run SRA (agent endpoints 501 / `BotDefinition` not queryable, or `RecruitmentAgentEnabled` toggle absent/not-editable)	Preflight STOP check — catch at Step 1, not the Step-9 wall. Traces to one of three missing grants: Agentforce provisioning, the Einstein-for-EDU license, or the `StudentRecruitmentAgent256` Gater. Detect which and request it; don't retry lower tiers. See `references/prerequisites.md`
Messaging channel created headlessly but the agent isn't reachable at runtime	The channel record is tier 1, but the ESD cascade behind it is UI-only — hand the customer the UI deployment path in `references/routing.md`
Cloned consumer flows fail at runtime	Wave-2 consumers need subflow replacement + `DefaultUserOwnerId` , not just a clone — see `references/flows.md`
Subagent action target `compile` s clean but won't `publish`	`compile` is syntax-only and echoes back any target; only `validate` / `publish` check existence. Never hand-author targets — add subagents from the Asset Library so the correct `source` / `target` is injected. See `references/agent-and-subagents.md`
Only Create Admissions Application fails validate	The lone `api://` action; broken by a platform issue everywhere, not fixable from this org. Delete it at step 9a rather than working around it — every other action still publishes. See `references/agent-and-subagents.md`
Agent answers "no information"	Two causes: (1) Knowledge articles still Draft — publish them (tier-1 API-able), or (2) the data library isn't attached — check the AFScript's `knowledge.rag_feature_config_id` is `ARFPC_<libraryId>` , not empty. Check both
EDU objects (e.g. Academic Interest) show 0 fields in Object Manager / the step-4 field-matrix build finds nothing	Ordering issue — the admin lacks the builder EDU-access sets. Assign Education Cloud Full Access + Einstein for Education Cloud Access first, before the field-matrix clone — fields are license-gated until then. See `references/permissions.md`
OWD or `ApplicationRecordTypeConfig` verify silently returns 0 rows	API-name traps: OWD's 6th object is `ProgramTermApplnTimeline` (truncated, not `...ApplicationTimeline` ); perm-set uses `PreliminaryApplicationRef` . `RecordTypeName` takes the record type's LABEL, not DeveloperName/Id. See `references/permissions.md`
`/headless/metadata` returns `400 UNSUPPORTED_OPERATION` or `500 METADATA_CRUD_ERROR`	Drop to tier 2/3, don't retry — but first rule out a wrong-surface or missing-perm error, not an allowlist gap. See `references/execution-model.md` ; the `setup/org/preferences` `ROUTE_NOT_FOUND` case: `references/platform-enablement.md`
`/query` returns `404` and looks like a platform outage	Check the call shape first — often self-inflicted: SOQL appended as `?q=...` instead of `queryParams: {"q": "<SOQL>"}` . A real outage is transient and all-versions-at-once. See `references/execution-model.md`
An earlier step genuinely needed `sf` /UI, and later steps keep using it too, out of habit	The tier ladder resets every step — re-attempt T1 first on each new action regardless of where the last step landed. See `references/execution-model.md`

问题	解决方案
组织无法运行SRA（代理端点501 / `BotDefinition` 无法查询，或 `RecruitmentAgentEnabled` 开关不存在/不可编辑）	预检STOP检查——在步骤1中捕获，而非步骤9。原因在于缺少以下三项授权之一：Agentforce配置、Einstein-for-EDU许可证，或 `StudentRecruitmentAgent256` Gater。检测缺失项并请求授权；请勿重试更低层级。见 `references/prerequisites.md`
无头创建的消息渠道在运行时无法访问代理	渠道记录属于T1，但背后的ESD级联仅支持UI——为客户提供 `references/routing.md` 中的UI部署路径
克隆的消费流在运行时失败	第二波消费流需要替换子流+设置 `DefaultUserOwnerId` ，而非仅克隆——见 `references/flows.md`
子代理操作目标 `compile` 成功但无法 `publish`	`compile` 仅检查语法并返回任何目标；只有 `validate` / `publish` 会检查目标是否存在。切勿手动编写目标——从资源库添加子代理以注入正确的 `source` / `target` 。见 `references/agent-and-subagents.md`
仅创建入学申请操作验证失败	唯一的 `api://` 操作；受平台问题影响，在所有组织中均无法正常工作。在步骤9a中删除该操作，而非尝试解决——其他所有操作仍可发布。见 `references/agent-and-subagents.md`
代理回复“无相关信息”	两种原因：(1) 知识库文章仍为草稿状态——发布文章（可通过T1 API完成），或(2) 数据库未附加——检查AFScript的 `knowledge.rag_feature_config_id` 是否为 `ARFPC_<libraryId>` ，而非空值。请同时检查这两项
EDU对象（例如Academic Interest）在对象管理器中显示0个字段 / 步骤4的字段矩阵构建未找到任何字段	顺序问题——管理员缺少构建者EDU访问权限集。在克隆字段矩阵前，先分配Education Cloud Full Access + Einstein for Education Cloud Access——字段在获得许可证前受权限限制。见 `references/permissions.md`
OWD或 `ApplicationRecordTypeConfig` 验证静默返回0行	API名称陷阱：OWD的第6个对象为 `ProgramTermApplnTimeline` （缩写，而非 `...ApplicationTimeline` ）；权限集使用 `PreliminaryApplicationRef` 。 `RecordTypeName` 使用记录类型的标签，而非开发者名称/ID。见 `references/permissions.md`
`/headless/metadata` 返回 `400 UNSUPPORTED_OPERATION` 或 `500 METADATA_CRUD_ERROR`	降级到T2/T3，请勿重试——但首先排除错误层面或权限缺失问题，而非白名单缺口。见 `references/execution-model.md` ； `setup/org/preferences` 的 `ROUTE_NOT_FOUND` 案例： `references/platform-enablement.md`
`/query` 返回 `404` 且看似平台故障	首先检查调用格式——通常是自身问题：SOQL以 `?q=...` 附加，而非 `queryParams: {"q": "<SOQL>"}` 。真正的故障是暂时的且影响所有版本。见 `references/execution-model.md`
之前的步骤确实需要 `sf` /UI，后续步骤因习惯继续使用	每个步骤的层级阶梯都会重置——无论上一步使用哪个层级，每个新操作都应优先尝试T1。见 `references/execution-model.md`

Output Expectations

输出预期

This skill configures a live org; no repository files. Expected outputs:

Confirmation messages after each step (what was done, and at which tier — headless /
```
sf
```
CLI / manual UI).
A verify query result after every step showing each toggle, perm set, flow, agent, subagent, and channel is in the expected state.
A final summary listing which tier each step landed on, plus any items left pending on the T3-only steps.

本技能用于配置实时组织；无仓库文件。预期输出：

每个步骤后的确认消息（执行的操作及使用的层级——无头 /
```
sf
```
CLI / 手动UI）。
每个步骤后的验证查询结果，显示每个开关、权限集、流、代理、子代理及渠道均处于预期状态。
最终总结，列出每个步骤使用的层级，以及所有T3专属步骤中仍待完成的项目。

Cross-Skill Integration

跨技能集成

Need	Delegate to
Generic Agentforce agent authoring or metadata generation	`agentforce-generate`

需求	委托至
通用Agentforce代理创作或元数据生成	`agentforce-generate`

Reference File Index

参考文件索引

File	When to read
`references/execution-model.md`	Any step — tier-ladder detail: allowlist, route signals, query-routing, API-version policy
`references/prerequisites.md`	Step 1 — edition/license check, the three SRA gates, EDU foundation verify
`references/platform-enablement.md`	Step 3 — per-toggle write paths
`references/permissions.md`	Steps 4–6, 9 & 10 — persona perm model, OWD list, topic-specific prep, agent-dependent grants
`references/grounding.md`	Steps 7–8 — Knowledge article/library flow, Data Cloud grounding builds
`references/agent-and-subagents.md`	Steps 9, 9a & 10 — agent creation, subagent + escalation wiring, the Builder session, AEA community grants
`references/flows.md`	Step 11 — flow inventory, 2-wave clone ordering
`references/routing.md`	Steps 12–13 — channel deploy, Omni-Channel routing, final structural verify

文件	阅读时机
`references/execution-model.md`	任何步骤——层级阶梯详情：白名单、路由信号、查询路由、API版本策略
`references/prerequisites.md`	步骤1——版本/许可证检查、三个SRA关卡、EDU基础验证
`references/platform-enablement.md`	步骤3——每个开关的写入路径
`references/permissions.md`	步骤4–6、9 & 10——角色权限模型、OWD列表、主题特定准备、代理相关授权
`references/grounding.md`	步骤7–8——知识库文章/库流程、Data Cloud grounding构建
`references/agent-and-subagents.md`	步骤9、9a & 10——代理创建、子代理+升级连接、构建者会话、AEA社区授权
`references/flows.md`	步骤11——流清单、两波克隆顺序
`references/routing.md`	步骤12–13——渠道部署、Omni-Channel路由、最终结构验证