forcedotcom/sf-skills / skills/service-itsm-agentic-setup-incident-management
service-itsm-agentic-setup-incident-management
VerifiedOrchestrator for Incident Management setup in Service Cloud ITSM: presents the features with live org status, and configures each — Incident preferences, Incident persona PSG assignment, Priority Matrix, SLA & Milestones, Incident dashboards, Email-to-Incident, Major Incident Management (approval group + MIM preferences), Broadcast Communications, Manage Incidents with AI, Service Management Privilege (privilege escalation), and audit tracking. Use for: set up or configure incident management, a walkthrough, what incident features can I configure; the incident preference toggles (default field validations, auto-close child incidents, auto-triage, assign with Einstein, restrict assigned group, rich text descriptions); assigning the Incident Fulfiller or Incident Manager persona PSG. DO NOT TRIGGER for: the master on/off switch alone (use the IncidentMgmt SOR), the Priority Matrix, SLA, or field history tracking alone, the Major Incident Manager PSG, creating/editing PSGs, or Problem/Change/Case Management.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.1 KB |
| examples/output-templates.md | markdown | 8.1 KB |
| references/audit-tracking.md | markdown | 3.3 KB |
| references/broadcast-communications.md | markdown | 1.9 KB |
| references/email-to-incident.md | markdown | 1.8 KB |
| references/incident-dashboards.md | markdown | 2.2 KB |
| references/incident-persona-psg.md | markdown | 2.9 KB |
| references/incident-preferences.md | markdown | 3.1 KB |
| references/major-incident-management.md | markdown | 2.9 KB |
| references/manage-incidents-with-ai.md | markdown | 3.2 KB |
| references/priority-matrix.md | markdown | 2.8 KB |
| references/service-mgmt-privilege.md | markdown | 2.9 KB |
| references/sla-milestones.md | markdown | 9.0 KB |
| references/status-checks.md | markdown | 22.4 KB |
references/broadcast-communications.md
View on GitHub# Feature: Broadcast Communications (delegated to the `service-itsm-broadcast-communications-setup` SOR)
How the orchestrator runs the **Broadcast Communications** feature over the
`service-itsm-broadcast-communications-setup` SOR — never the Service-Foundation `IncidentManagement`
look-alike's broadcast toggles. The SOR's own steps and guidance decide *how*; the orchestrator runs them
itself under its **SOR hand-off protocol** and owns every user-facing gate. This file adds what is specific
to Broadcast Communications.
1. `discover` the SOR by intent (e.g. "set up ITSM broadcast communications") and `describe` the id
`discover` returns. Its own prerequisite checks fall under protocol step 2.
2. **Phase 1 — turn it on, before asking about anything else.** Read the feature (`get-feature-status`).
Already on → Phase 2 with no question. Non-empty `enableBlockedReasons` or `dependencyStatuses` → name
the unmet prerequisite in plain language and stop. Otherwise say it's off and that turning it on **can't
be undone** (Salesforce Go has no way to turn it off), get an explicit yes, run `enable-feature`, and
require `verify-enabled` to read it on. Never turn the feature off, even when asked — offer to turn off a
channel or object, or to revoke sender access, instead.
3. **Phase 2 — configure only what the user picks** (`AskUserQuestion`, multi-select; never everything by
default): **sender access** for the users they name (resolve each name, username, or email to exactly
one user, or ask; the license goes on before the *Broadcast Communication Sender* permission set, a
duplicate is success, and only that permission set is ever assigned), **channels** (Email, In-app,
Slack, Microsoft Teams — Slack delivers only with a connected Slack org), and **objects** (Incident,
Change Request). For each: read, skip it if already set, confirm, write, and read back.
4. This is setup only — it sends no broadcast.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |