• 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.

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

sf

401

403

404

1. 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.
2. 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.

3. node

   ≥ 18 on PATH (runs the classifier script).

sf

• 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.

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

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.

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.

1. 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).

1. 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.

1. 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.

• 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.