service-itsm-agentic-setup-agentforce-studio-validate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Validate Agentforce for IT Service Prerequisites

验证Agentforce for IT Service前置条件

Readiness check for Agentforce for IT Service, for either the Fulfiller or the Employee agent path. Before an ITSM agent can be created, the org must have the right Salesforce Go feature toggles turned on (the ones on the Agentforce for IT Service setup page). This skill reads those toggles through the Salesforce CLI (
sf
) — a single authenticated Connect API call via

sf api request rest

— and a helper script classifies the chosen agent path into a READY / NOT-READY verdict.

This is the read-only step in a three-skill flow. It never enables anything; turning toggles on is a separate write-capable skill:

Step	Skill	What it does
1. Validate (this skill)	`service-itsm-agentic-setup-agentforce-studio-validate`	Read the toggles → READY / NOT-READY (no writes)
2. Configure	`service-itsm-agentic-setup-agentforce-studio-configure`	Turn the disabled toggles ON
3. Create agent	`service-itsm-agentic-setup-fulfiller-agent-configure`	Create + activate the Fulfiller agent

On NOT-READY this skill names each disabled toggle and hands off to

service-itsm-agentic-setup-agentforce-studio-configure

to enable them — it does not POST an enable itself.

The feature toggles and their real

featureApiName

Go-page toggle	featureApiName	Required for
Turn on Agentforce Studio	`sales-cloud-agent-studio`	both paths (shared)
Agentforce for IT Service (parent umbrella)	`service-cloud-agentforce-for-itsm`	both paths (shared)
IT Service Fulfiller	`service-cloud-it-fulfiller-agent`	fulfiller
IT Service Employee	`service-cloud-requestor-agent`	employee
Specialized Agent Templates for Employee	`service-cloud-it-service-employee-agent`	employee

All are Connect API features (

/connect/setup/discovery/...

) — the read goes through

sf api request rest

, no Headless360 dispatcher required. The classification is deterministic and lives in

scripts/classify-readiness.mjs

(invoked via

Bash

), not in prose.

面向Fulfiller或Employee代理路径的Agentforce for IT Service就绪性检查。在创建ITSM代理之前，组织必须开启正确的Salesforce Go功能开关（即Agentforce for IT Service设置页面上的开关）。本技能通过Salesforce CLI（
sf
）读取这些开关——通过
sf api request rest
进行一次已认证的Connect API调用——然后辅助脚本将所选代理路径归类为READY / NOT-READY判定结果。

这是三步技能流程中的只读步骤。它绝不会启用任何功能；开启开关是另一项具备写入权限的技能：

步骤	技能	功能
1. 验证（本技能）	`service-itsm-agentic-setup-agentforce-studio-validate`	读取开关 → READY / NOT-READY（无写入操作）
2. 配置	`service-itsm-agentic-setup-agentforce-studio-configure`	将禁用的开关开启
3. 创建代理	`service-itsm-agentic-setup-fulfiller-agent-configure`	创建并激活Fulfiller代理

当判定为NOT-READY时，本技能会列出每个禁用的开关，并将任务移交给

service-itsm-agentic-setup-agentforce-studio-configure

来启用它们——它不会自行发送启用请求。

功能开关及其对应的实际

featureApiName

：

Go页面开关	featureApiName	适用场景
开启Agentforce Studio	`sales-cloud-agent-studio`	两种路径（共用）
Agentforce for IT Service（父级总开关）	`service-cloud-agentforce-for-itsm`	两种路径（共用）
IT Service Fulfiller	`service-cloud-it-fulfiller-agent`	fulfiller路径
IT Service Employee	`service-cloud-requestor-agent`	employee路径
面向Employee的Specialized Agent Templates	`service-cloud-it-service-employee-agent`	employee路径

所有这些都是Connect API功能（

/connect/setup/discovery/...

）——读取操作通过

sf api request rest

完成，无需Headless360调度器。归类逻辑是确定性的，定义在

scripts/classify-readiness.mjs

中（通过

Bash

调用），而非自然语言描述。

Scope

范围

In scope: Reading the Agentforce-for-IT-Service Go feature toggles via
```
connect/setup/discovery/features/status
```
; classifying the fulfiller or employee path into a per-feature + overall READY / NOT-READY verdict via a helper script; on NOT-READY, naming each disabled toggle and handing off to
```
service-itsm-agentic-setup-agentforce-studio-configure
```
to enable it.
Out of scope: Enabling / turning on any toggle — that write is owned by
```
service-itsm-agentic-setup-agentforce-studio-configure
```
(this skill is read-only and never POSTs an enable); creating, committing, or activating an agent (handled by
```
service-itsm-agentic-setup-fulfiller-agent-configure
```
); the org-wide multi-agent orchestration toggle (that is a Headless360-only pref, not an ITSM Connect feature, and is not one of the setup-page toggles); assigning permission sets; CMDB CRUD.

范围内：通过
```
connect/setup/discovery/features/status
```
读取Agentforce-for-IT-Service的Go功能开关；通过辅助脚本将fulfiller或employee路径归类为逐功能及整体的READY / NOT-READY判定结果；当判定为NOT-READY时，列出每个禁用的开关并移交任务给
```
service-itsm-agentic-setup-agentforce-studio-configure
```
来启用它们。
范围外：启用任何开关——写入操作由
```
service-itsm-agentic-setup-agentforce-studio-configure
```
负责（本技能为只读，绝不会发送启用请求）；创建、提交或激活代理（由
```
service-itsm-agentic-setup-fulfiller-agent-configure
```
处理）；组织级多代理编排开关（这是仅Headless360可用的偏好设置，不属于ITSM Connect功能，也不是设置页面上的开关）；分配权限集；CMDB增删改查操作。

Which path?

选择哪种路径？

Determine whether the user is setting up the fulfiller agent (the IT-fulfiller-facing agent) or an employee agent (the employee-facing / NGA agent). If it is not clear from the request, ask (

AskUserQuestion

). The path selects which toggles are required:

fulfiller →

sales-cloud-agent-studio

service-cloud-agentforce-for-itsm

service-cloud-it-fulfiller-agent

employee →

sales-cloud-agent-studio

service-cloud-agentforce-for-itsm

service-cloud-requestor-agent

service-cloud-it-service-employee-agent

确定用户是要设置fulfiller代理（面向IT履行人员的代理）还是employee代理（面向员工的/NGA代理）。如果请求中未明确说明，请询问用户（

AskUserQuestion

）。路径选择决定了需要哪些开关：

fulfiller路径 →

sales-cloud-agent-studio

service-cloud-agentforce-for-itsm

service-cloud-it-fulfiller-agent

employee路径 →

sales-cloud-agent-studio

service-cloud-agentforce-for-itsm

service-cloud-requestor-agent

service-cloud-it-service-employee-agent

Preconditions

前置条件

Before the skill can read anything, the CLI and target org must be configured. If any of these are unmet,

sf

surfaces an auth error or a

; do not fabricate state — surface the raw error and stop.

sf
CLI installed and authenticated to the target org (
```
sf org display -o <alias>
```
shows Connected). All calls use
```
--target-org <alias>
```
; never extract or pass the access token by hand.
API v67.0+: the
```
connect/setup/discovery
```
feature APIs are available at v67.0. The version is pinned in the URL path; do not hand-edit it below the minimum.
node
≥ 18 on PATH (runs the classifier script).

If a precondition fails,

sf

returns one of:

Auth error /
```
401 Unauthorized
```
→ session expired or wrong alias; re-run
```
sf org login web
```
.
```
403 Forbidden
```
→ the user/org lacks the required access (missing Agentforce license).
```
404 Not Found
```
→ the feature-discovery surface is not wired on this org tier — the classifier maps a missing/error body to CANNOT-CONFIRM, not a hard failure.

在技能能够读取任何内容之前，必须配置好CLI和目标组织。如果以下任何一项未满足，

sf

会返回认证错误或

；请勿编造状态——直接显示原始错误并终止操作。

sf
CLI已安装并已认证到目标组织（
```
sf org display -o <alias>
```
显示已连接）。所有调用均使用
```
--target-org <alias>
```
；切勿手动提取或传递访问令牌。
API v67.0+：
```
connect/setup/discovery
```
功能API在v67.0及以上版本可用。版本已固定在URL路径中；请勿手动将其修改为低于最低版本。
PATH中存在
node
≥ 18（用于运行归类脚本）。

如果前置条件未满足，

sf

会返回以下错误之一：

认证错误 /
```
401 Unauthorized
```
→ 会话过期或别名错误；重新运行
```
sf org login web
```
。
```
403 Forbidden
```
→ 用户/组织缺少必要的访问权限（缺少Agentforce许可证）。
```
404 Not Found
```
→ 该组织层级未接入功能发现接口——归类脚本会将缺失/错误响应映射为CANNOT-CONFIRM，而非严重失败。

Operations at a glance

操作概览

Operation Command Returns

Read feature toggles

Operation	Command	Returns
Read feature toggles	`sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" --method POST --body '{"featureApiNames":[...]}' --target-org <alias>`	`{items:[{apiName,status,enableBlockedReasons[],dependencyStatuses[]}]}` — `status` is `ENABLED` / `NOT_ENABLED` per toggle.

sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" --method POST --body '{"featureApiNames":[...]}' --target-org <alias>

{items:[{apiName,status,enableBlockedReasons[],dependencyStatuses[]}]}

—

status

ENABLED

NOT_ENABLED

per toggle.

This skill makes only the read above — it is read-only. Enabling a toggle (

.../feature/{apiName}/enable

) is out of scope: hand off to

service-itsm-agentic-setup-agentforce-studio-configure

sf api request rest

prints the raw response body (JSON) to stdout — capture it to a file and hand it to the classifier. Full command shapes and the error taxonomy live in

references/cli-invocation.md

Never extract the access token. Use
sf api request rest
directly — it uses the CLI's stored session for the target org. Do not pull the
accessToken
out of
sf org display
and hand-build an HTTP request with it; that bypasses the CLI session and leaks a bearer token into shell context.

操作命令返回结果

读取功能开关

操作	命令	返回结果
读取功能开关	`sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" --method POST --body '{"featureApiNames":[...]}' --target-org <alias>`	`{items:[{apiName,status,enableBlockedReasons[],dependencyStatuses[]}]}` —— `status` 为每个开关的 `ENABLED` / `NOT_ENABLED` 状态。

sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" --method POST --body '{"featureApiNames":[...]}' --target-org <alias>

{items:[{apiName,status,enableBlockedReasons[],dependencyStatuses[]}]}

——

status

为每个开关的

ENABLED

NOT_ENABLED

状态。

本技能仅执行上述读取操作——它是只读的。启用开关（

.../feature/{apiName}/enable

）属于范围外操作：移交任务给

service-itsm-agentic-setup-agentforce-studio-configure

。

sf api request rest

会将原始响应体（JSON）打印到标准输出——将其捕获到文件中并传递给归类脚本。完整的命令格式和错误分类请参考

references/cli-invocation.md

。

切勿提取访问令牌。直接使用
sf api request rest
——它会使用CLI为目标组织存储的会话。请勿从
sf org display
中提取
accessToken
并手动构建HTTP请求；这会绕过CLI会话并将Bearer令牌泄露到Shell环境中。

Architecture — How the check works

架构——检查工作原理

Step	What happens	Tool used
Pick path	Determine fulfiller vs employee (ask if unclear)	`AskUserQuestion`
Read toggles	POST the feature-status batch for all toggles the path needs, capture to a file	`Bash` ( `sf api request rest` )
Classify	Run `scripts/classify-readiness.mjs <file> <agentType> [exitStatus]` → per-feature + overall verdict	`Bash` ( `node` )
Report	Render the classifier's verdict into the Output Format	—
Hand off	On NOT-READY, name each disabled toggle and hand off to `service-itsm-agentic-setup-agentforce-studio-configure` to enable it	—

The skill is read-only — it never enables a toggle.

步骤	操作内容	使用工具
选择路径	确定是fulfiller还是employee路径（若不明确则询问）	`AskUserQuestion`
读取开关	批量POST所选路径所需的所有开关状态，将结果捕获到文件中	`Bash` （ `sf api request rest` ）
归类	运行 `scripts/classify-readiness.mjs <file> <agentType> [exitStatus]` → 逐功能及整体判定结果	`Bash` （ `node` ）
报告	将归类脚本的判定结果转换为输出格式	—
移交任务	当判定为NOT-READY时，列出每个禁用的开关并移交任务给 `service-itsm-agentic-setup-agentforce-studio-configure` 来启用它们	—

本技能为只读——它绝不会启用任何开关。

Workflow

工作流程

Substitute

<alias>

with the target org alias (ask the user, or use the default org from

sf config

<agentType>

fulfiller

employee

将

<alias>

替换为目标组织别名（询问用户，或使用

sf config

中的默认组织）。

<agentType>

为

fulfiller

或

employee

。

Phase 1 — Read the feature toggles

阶段1 —— 读取功能开关

POST the feature-status batch for every toggle the chosen path needs (safe to always request all five — the classifier only judges the ones the path requires), capturing stdout to a file. Do not add

--json

bash

sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" \
  --method POST \
  --body '{"featureApiNames":["sales-cloud-agent-studio","service-cloud-agentforce-for-itsm","service-cloud-it-fulfiller-agent","service-cloud-requestor-agent","service-cloud-it-service-employee-agent"]}' \
  --target-org <alias> > /tmp/features-status.json 2>/tmp/features-status.err
echo $? > /tmp/features-status.exit

Capture the command's exit status (

$?

) so the classifier can tell a confirmed 404 (gate not wired) apart from an auth/permission/transport failure. Do not swallow the exit with

|| true

— pass it to the classifier in Phase 2.

批量POST所选路径所需的所有开关状态（可以安全地直接请求全部五个——归类脚本只会判定路径所需的开关），将标准输出捕获到文件中。请勿添加

--json

参数：

bash

sf api request rest "/services/data/v67.0/connect/setup/discovery/features/status" \
  --method POST \
  --body '{"featureApiNames":["sales-cloud-agent-studio","service-cloud-agentforce-for-itsm","service-cloud-it-fulfiller-agent","service-cloud-requestor-agent","service-cloud-it-service-employee-agent"]}' \
  --target-org <alias> > /tmp/features-status.json 2>/tmp/features-status.err
echo $? > /tmp/features-status.exit

捕获命令的退出状态（

$?

），以便归类脚本区分已确认的404（接口未接入）与认证/权限/传输失败。请勿使用

|| true

忽略退出状态——将其传递给阶段2的归类脚本。

Phase 2 — Classify (helper script)

阶段2 —— 归类（辅助脚本）

Run the classifier over the captured file, the chosen agent type, and the captured exit status. Use the skill's absolute directory for the script path:
bash
```
node "<skill_dir>/scripts/classify-readiness.mjs" /tmp/features-status.json <agentType> "$(cat /tmp/features-status.exit)"
```
It prints
```
{ agentType, readState, features, verdict, notEnabled, enableable, reasons, rawError }
```
where each feature is
```
PASS | FAIL | CANNOT-CONFIRM | ERROR
```
and
```
verdict
```
is
```
READY | NOT-READY | CANNOT-CONFIRM | ERROR
```
. This is the authoritative verdict — do not re-derive it from the raw response in prose.
```
notEnabled
```
lists every disabled required toggle;
```
enableable
```
is the subset with no
```
enableBlockedReasons
```
— the ones the configure skill can turn on straight away (the rest are blocked by an unmet dependency or a purchase/licensing gate).

使用捕获的文件、所选代理类型以及捕获的退出状态运行归类脚本。使用技能的绝对目录作为脚本路径：
bash
```
node "<skill_dir>/scripts/classify-readiness.mjs" /tmp/features-status.json <agentType> "$(cat /tmp/features-status.exit)"
```
它会输出
```
{ agentType, readState, features, verdict, notEnabled, enableable, reasons, rawError }
```
，其中每个功能的状态为
```
PASS | FAIL | CANNOT-CONFIRM | ERROR
```
，
```
verdict
```
为
```
READY | NOT-READY | CANNOT-CONFIRM | ERROR
```
。这是权威的判定结果——请勿从原始响应中自行推导。
```
notEnabled
```
列出所有禁用的必需开关；
```
enableable
```
是其中没有
```
enableBlockedReasons
```
的子集——即配置技能可以直接开启的开关（其余开关因未满足依赖项或购买/许可限制而被阻止）。

Phase 3 — Report + hand off

阶段3 —— 报告 + 移交任务

Render the classifier output into the Output Format below.
- READY → point the user at
```
service-itsm-agentic-setup-fulfiller-agent-configure
```
  to create the agent (fulfiller path), or
```
service-itsm-agentic-setup-employee-agent-configure
```
  (employee path).
- NOT-READY → name each disabled toggle (from
```
notEnabled
```
  ). For the
```
enableable
```
  subset, hand off to
```
service-itsm-agentic-setup-agentforce-studio-configure
```
  to turn them on (offer via
```
AskUserQuestion
```
  : "N prerequisite toggle(s) are off. Run service-itsm-agentic-setup-agentforce-studio-configure to enable them?" → on Yes, delegate; on No, stop and report). For any disabled-but-blocked toggle (in
```
notEnabled
```
  but not
```
enableable
```
  ), report its
```
enableBlockedReasons
```
  verbatim — it cannot be enabled until the blocker clears. This skill does not POST an enable itself.
- CANNOT-CONFIRM → state which toggle(s) had no status and that the feature-discovery surface may not be wired on this org tier.
- ERROR → the read failed (auth / permission / transport, or an unexpected body — see
```
rawError
```
  ). Surface the raw response and stop; do not treat it as a mere wiring gap.

将归类脚本的输出转换为以下输出格式。
- READY → 引导用户使用
```
service-itsm-agentic-setup-fulfiller-agent-configure
```
  创建代理（fulfiller路径），或使用
```
service-itsm-agentic-setup-employee-agent-configure
```
  （employee路径）。
- NOT-READY → 列出每个禁用的开关（来自
```
notEnabled
```
  ）。对于
```
enableable
```
  子集，移交任务给
```
service-itsm-agentic-setup-agentforce-studio-configure
```
  来开启它们（通过
```
AskUserQuestion
```
  询问："有N个前置条件开关处于关闭状态。是否运行service-itsm-agentic-setup-agentforce-studio-configure来启用它们？" → 如果用户选择是，则委托执行；如果选择否，则终止操作并报告）。对于任何已禁用但被阻止的开关（属于
```
notEnabled
```
  但不属于
```
enableable
```
  ），直接报告其
```
enableBlockedReasons
```
  ——在阻止因素消除之前无法启用。本技能不会自行发送启用请求。
- CANNOT-CONFIRM → 说明哪些开关未返回状态，并指出该组织层级可能未接入功能发现接口。
- ERROR → 读取操作失败（认证/权限/传输错误，或意外响应体——请查看
```
rawError
```
  ）。显示原始响应并终止操作；请勿将其视为单纯的接口未接入问题。

Phase 4 — (After enable) re-validate

阶段4 —— （启用后）重新验证

If the user ran
```
service-itsm-agentic-setup-agentforce-studio-configure
```
to enable the toggles, re-run Phase 1 + Phase 2 here to confirm the verdict flips to READY, then report. This skill's own role remains read-only throughout.

如果用户已运行
```
service-itsm-agentic-setup-agentforce-studio-configure
```
启用开关，请在此处重新运行阶段1 + 阶段2以确认判定结果变为READY，然后进行报告。本技能始终保持只读角色。

Rules / Constraints

规则 / 约束

Constraint	Rationale
This skill is read-only — it never POSTs a feature enable	Turning toggles on is a separate write-capable skill ( `service-itsm-agentic-setup-agentforce-studio-configure` ); keeping the two apart keeps the `validate` verb honest and avoids two skills owning the same write
On NOT-READY, hand off to `service-itsm-agentic-setup-agentforce-studio-configure` for enablement	That skill owns the `.../feature/{apiName}/enable` write path (idempotent, dependency-ordered); this skill only names what is off
The read goes through `sf api request rest` ; never extract the access token or hand-build a raw HTTP request	`sf api request rest` uses the CLI's stored session for `--target-org` ; extracting the token leaks a bearer token into shell context
Classification lives in `scripts/classify-readiness.mjs` , invoked via `Bash` — not in prose	The verdict is a deterministic decision table over fixed feature statuses; a script is reliable, prose interpretation is not (authoring standard A9)
The required-toggle set depends on the agent path	Fulfiller and Employee agents gate on different template toggles; the classifier encodes both paths
These are Connect API features — use SF CLI, not Headless360	A Connect/Tooling equivalent exists, so SF CLI is preferred (avoids the Headless360HostedMcpServer org-perm gate)
`enableBlockedReasons` non-empty ⇒ toggle is not in `enableable` — report the blocker	A blocked toggle can't be turned on even by the configure skill until the unmet dependency / purchase gate clears
Do not pass `--json` to `sf api request rest`	It is unsupported on some Connect endpoints; the raw stdout body is already JSON

约束	理由
本技能为只读——绝不会发送功能启用请求	开启开关是另一项具备写入权限的技能（ `service-itsm-agentic-setup-agentforce-studio-configure` ）；将两者分离可确保 `validate` 的语义准确，并避免两个技能负责相同的写入操作
当判定为NOT-READY时，移交任务给 `service-itsm-agentic-setup-agentforce-studio-configure` 来启用开关	该技能负责 `.../feature/{apiName}/enable` 写入路径（幂等、按依赖顺序执行）；本技能仅列出哪些开关处于关闭状态
读取操作通过 `sf api request rest` 完成；切勿提取访问令牌或手动构建原始HTTP请求	`sf api request rest` 使用CLI为 `--target-org` 存储的会话；提取令牌会将Bearer令牌泄露到Shell环境中
归类逻辑定义在 `scripts/classify-readiness.mjs` 中，通过 `Bash` 调用——而非自然语言描述	判定结果是基于固定功能状态的确定性决策表；脚本更可靠，自然语言解释不可靠（创作标准A9）
必需开关集取决于代理路径	Fulfiller和Employee代理依赖不同的模板开关；归类脚本已编码两种路径的逻辑
这些是Connect API功能——使用SF CLI，而非Headless360	存在Connect/Tooling等效接口，因此优先使用SF CLI（避免Headless360HostedMcpServer组织权限限制）
`enableBlockedReasons` 非空 ⇒ 开关不属于 `enableable` ——报告阻止因素	被阻止的开关即使通过配置技能也无法开启，直到未满足的依赖项/购买限制消除
请勿向 `sf api request rest` 传递 `--json` 参数	部分Connect端点不支持该参数；原始标准输出体已经是JSON格式

Verification Checklist

验证检查清单

The agent path (fulfiller / employee) was determined (asked if unclear).
The feature-status POST was run via
```
sf api request rest
```
and its body captured to a file.
```
scripts/classify-readiness.mjs
```
was invoked with the file, the agent type, and the captured exit status, and its
```
{verdict, notEnabled, enableable, rawError}
```
output recorded.
The verdict (READY / NOT-READY / CANNOT-CONFIRM / ERROR) was reported verbatim from the classifier; on NOT-READY each disabled toggle was named, with the enable route only for the
```
enableable
```
subset and
```
enableBlockedReasons
```
reported for the rest; on ERROR the raw response was surfaced and the skill stopped.
No feature was enabled by this skill (it is read-only); on NOT-READY the disabled toggles were named and the hand-off to
```
service-itsm-agentic-setup-agentforce-studio-configure
```
was offered, and the access token was never extracted.

已确定代理路径（fulfiller / employee）（若不明确则已询问用户）。
已通过
```
sf api request rest
```
运行功能状态POST请求，并将响应体捕获到文件中。
已使用捕获的文件、代理类型以及捕获的退出状态调用
```
scripts/classify-readiness.mjs
```
，并记录其
```
{verdict, notEnabled, enableable, rawError}
```
输出。
已直接报告归类脚本返回的判定结果（READY / NOT-READY / CANNOT-CONFIRM / ERROR）；当判定为NOT-READY时，已列出每个禁用的开关，仅为
```
enableable
```
子集提供启用路径，并为其余开关报告
```
enableBlockedReasons
```
；当判定为ERROR时，已显示原始响应并终止技能。
本技能未启用任何功能（只读）；当判定为NOT-READY时，已列出禁用的开关并提供移交任务给
```
service-itsm-agentic-setup-agentforce-studio-configure
```
的选项，且从未提取访问令牌。

Output Format

输出格式

Present the readiness report as:

text

Agentforce for IT Service — Prerequisite Check (via service-itsm-agentic-setup-agentforce-studio-validate)

Org:          <org-alias> (API v67.0)
Agent path:   fulfiller | employee

  [PASS|FAIL] Agentforce Studio ......................... ENABLED | NOT_ENABLED (sales-cloud-agent-studio)
  [PASS|FAIL] Agentforce for IT Service (parent) ........ ENABLED | NOT_ENABLED (service-cloud-agentforce-for-itsm)
  [PASS|FAIL] <path-specific toggle(s)> ................. ENABLED | NOT_ENABLED (<featureApiName>)

Verdict: READY  |  NOT-READY  |  CANNOT-CONFIRM  |  ERROR

Next steps:
  - <If READY: "Org satisfies the prerequisites for the <path> agent. Create it via service-itsm-agentic-setup-fulfiller-agent-configure (fulfiller) / the employee-agent skill.">
  - <If NOT-READY: list each disabled toggle; for the enableable ones, hand off to service-itsm-agentic-setup-agentforce-studio-configure to turn them on; for blocked ones, report the enableBlockedReasons.>
  - <If CANNOT-CONFIRM: state which toggle(s) returned no status and that the feature-discovery surface may not be wired on this org.>

This skill is read-only — no org state is written. The only file it produces is the temporary response capture handed to the classifier.

按以下格式呈现就绪性报告：

text

Agentforce for IT Service — 前置条件检查（通过service-itsm-agentic-setup-agentforce-studio-validate）

组织:          <org-alias>（API v67.0）
代理路径:   fulfiller | employee

  [PASS|FAIL] Agentforce Studio ......................... ENABLED | NOT_ENABLED (sales-cloud-agent-studio)
  [PASS|FAIL] Agentforce for IT Service（父级） ........ ENABLED | NOT_ENABLED (service-cloud-agentforce-for-itsm)
  [PASS|FAIL] <路径专属开关> ................. ENABLED | NOT_ENABLED (<featureApiName>)

判定结果: READY  |  NOT-READY  |  CANNOT-CONFIRM  |  ERROR

下一步操作:
  - <如果为READY: "组织已满足<路径>代理的前置条件。通过service-itsm-agentic-setup-fulfiller-agent-configure（fulfiller路径）/ employee代理技能创建代理。">
  - <如果为NOT-READY: 列出每个禁用的开关；对于可启用的开关，移交任务给service-itsm-agentic-setup-agentforce-studio-configure来开启；对于被阻止的开关，报告enableBlockedReasons。>
  - <如果为CANNOT-CONFIRM: 说明哪些开关未返回状态，并指出该组织可能未接入功能发现接口。>

本技能为只读——不会修改任何组织状态。它仅生成传递给归类脚本的临时响应捕获文件。

Reference File Index

参考文件索引

File	When to read
`references/cli-invocation.md`	Every phase — exact `sf api request rest` read call shape, the feature-status route, the read-only / hand-off rule, the never-extract-token rule, the classifier contract, and the error taxonomy

文件	阅读时机
`references/cli-invocation.md`	所有阶段——精确的 `sf api request rest` 读取命令格式、功能状态接口、只读/移交规则、禁止提取令牌规则、归类脚本约定以及错误分类