forcedotcom/sf-skills / plugins/builder/service-itsm/skills/service-itsm-agentic-setup-fulfiller-agent-configure
service-itsm-agentic-setup-fulfiller-agent-configure
UnverifiedCreate and activate the IT Service Fulfiller agent as a Next-Gen Authoring (NGA) native agent from the shipped ITSM Fulfiller template's Agent Script, using the Salesforce CLI (sf): read the template, check idempotency, create the NGA bundle then publish and activate it, then verify it is live. Idempotent per developer name. The Fulfiller agent is the IT-technician-facing assistant for incident triage, case summarization, field updates, and related-record automations. Use when asked to create the Fulfiller agent, set up the IT Service Fulfiller agent, provision the fulfiller assistant, or activate the Fulfiller agent. Triggers: create fulfiller agent, set up fulfiller agent, provision fulfiller agent, activate fulfiller agent. DO NOT TRIGGER: checking org prerequisites (service-itsm-agentic-setup-agentforce-studio-validate), or CMDB CRUD.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 34.0 KB |
| references/action-availability.md | markdown | 6.2 KB |
| references/cli-invocation.md | markdown | 21.3 KB |
| references/error-taxonomy.md | markdown | 4.1 KB |
| references/reactivation.md | markdown | 4.0 KB |
| references/report-format.md | markdown | 4.2 KB |
| references/workflow-detail.md | markdown | 16.7 KB |
| scripts/build-create-body.mjsexecutable | script | 5.2 KB |
| scripts/classify-action-availability.mjsexecutable | script | 12.3 KB |
| scripts/classify-activate-result.mjsexecutable | script | 5.5 KB |
| scripts/classify-agent-existence.mjsexecutable | script | 13.6 KB |
| scripts/classify-preflight.mjsexecutable | script | 10.3 KB |
| scripts/create-scratch-dir.mjsexecutable | script | 2.3 KB |
| scripts/render-report.mjsexecutable | script | 11.8 KB |
| scripts/strip-release-management.mjsexecutable | script | 8.8 KB |
references/report-format.md
View on GitHub# Report Format — Fulfiller Agent Create & Activate
The report layout is generated deterministically by `scripts/render-report.mjs` — the single source of report text for both the chat-turn response and the harness's `${outputDir}/report.md` file, so the two never diverge. Never hand-compose the layout, field placement, stage rows, or next-step wording in prose (authoring standard A9); always shell out to the helper.
## Rendered shape
```text
# Fulfiller Agent — Create & Activate
IT Service Fulfiller Agent Creation (via service-itsm-agentic-setup-fulfiller-agent-configure)
Org: <org-alias> (API v67.0)
Agent: <developerName> ("<label>") — NGA-native bundle
Stage 2 — install & activate the agent from its template:
| Stage | Status |
| --- | --- |
| Preflight | Studio hasAccess=<true/false/cannot-confirm>; template agentScript present=<yes/no>; verdict=<READY/NOT-READY/CANNOT-CONFIRM> |
| Enumerate | target agent exists before write=<yes/no>; latest version status=<Active/Inactive/n/a>; verdict=<exists:...> |
| Confirm-to-write | user-confirmed=<true/false/pending> |
| Create bundle | <succeeded (created) / ALREADY-CREATED / skipped (reactivation path) / pending confirmation / skipped / FAILED> |
| Publish | <succeeded / skipped / pending confirmation / FAILED> |
| Activate | <succeeded (created) / succeeded (reactivated existing) / skipped / pending confirmation / FAILED> |
| Verify | <BotDefinition present: yes/no; latest version Active: yes/no / skipped / pending> |
Verdict: CREATED | ALREADY-CREATED | ACTIVATED | PENDING CONFIRMATION | DECLINED | FAILED
Reason: <plain-language explanation naming the atomicity constraint, the idempotency decision, and any decline/skip reasoning — the caller populates this before invoking the helper, so it can be as rubric-facing as the situation warrants without repeating raw API calls>
Next steps:
- <helper-generated line keyed off the verdict>
```
The helper enforces a validated verdict set and picks the `Next steps` line from the verdict, so the file never drifts from that shape.
**No internal record IDs in the report.** The stage rows carry status only — the bundle version `id`, `publishedBotId`/`BotDefinition`, and `BotVersion` are captured solely to drive the publish/activate/verify calls and are meaningless to an admin, so they are never displayed. The helper renders status-only rows and defensively scrubs any ID that a caller passes inside a stage-status string, so a report can never leak one regardless of the phase-state input. Do not add IDs back in turn-side narration either (never "Bundle created (version id …)" / "Published (BotDefinition …)").
## Checkpoint writes (harness / non-interactive runs)
When `${outputDir}` is provided (via the harness's generated-file location directive), invoke the helper at three checkpoints so a report always exists even when a run parks at a confirmation gate:
1. **Before Phase 3's confirmation gate** — verdict `PENDING CONFIRMATION` with Preflight + Enumerate rows populated; the helper marks Confirm-to-write / Create / Publish / Activate as `pending confirmation` and Verify as `skipped`. On the user's "no" at the gate, re-render with verdict `DECLINED` and a one-line `reason` naming the decline (the helper flips write rows to `skipped`).
2. **After Phase 6 (or the Phase-2b reactivation activation)** — verdict is still not the final verdict yet; the helper is re-invoked with the create-succeeded (or reactivation-succeeded) state and Verify `pending`.
3. **After Phase 8** — verdict `CREATED` / `ALREADY-CREATED` / `ACTIVATED` / `FAILED` with all rows filled in.
Each invocation overwrites `${outputDir}/report.md`, so the last state on disk is always the most complete. Skip these writes when running interactively for a user in a chat surface — write only when `${outputDir}` was passed as an explicit destination.
## Interactive runs
When talking to the user in a chat surface, the assistant may still add turn-side narrative context above or below the helper output (raw command traces, error diagnostics, remediation walkthroughs, "why this is blocking" prose) — the *report* is what the helper emits, the *turn* can be as rich as the situation warrants. Only the report file has the strict shape.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |