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/incident-dashboards.md
View on GitHub# Feature: Incident Dashboards (delegated to two SORs, one per persona)
How the orchestrator runs the **Incident Dashboards** feature over `itsm-incident-dashboard-enablement`
(Incident Manager) and `itsm-incident-fulfiller-dashboard-enablement` (Incident Fulfiller). Each 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 the dashboards.
1. Unless the user already said, ask which (`AskUserQuestion`): the **Incident Manager** dashboards (the
Incident Manager dashboards and the Home page dashboards — `itsm-incident-dashboard-enablement`), the
**Incident Fulfiller** dashboards (the fulfiller work view and the fulfiller Home page —
`itsm-incident-fulfiller-dashboard-enablement`), or both. `discover` and `describe` each chosen SOR
(e.g. "turn on incident manager dashboards", "turn on incident fulfiller dashboards").
2. Each SOR turns on two org preferences, one at a time. `check-dashboard-preference` first confirms that
Dynamic Dashboards for IT Service (`service-cloud-itsm-dashboard`) reads exactly `ENABLED`; it turns on
with IT Service Enablement, so never enable it or ask about it, and any other result stops the feature.
Then read each preference, skip any already on, ask the SOR's question before each write that turns one
on (`update-dashboard-preference`), and read each back (`verify-dashboard-preference`). Turn on only the
persona the user chose.
3. After both preferences of a SOR are handled, run its `verify-dashboards-materialized` query. The
dashboards deploy asynchronously, so report the titles it finds; if they are still missing after its
retries, say the preference is set but the dashboards are not confirmed to exist, give the user the same
query, and point them to All Dashboards (App Launcher → Dashboards). A user sees the dashboards only
with the ITSM console-view permission (a separate grant). If the write returns a dynamic-dashboard limit
error, report it: freeing a slot (converting a dynamic dashboard to static, or deleting an unused one) is
a manual admin step — never retry or remediate it here.
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 |