Skip to content

forcedotcom/sf-skills / skills/service-itsm-agentic-setup-cmdb-coordinate

service-itsm-agentic-setup-cmdb-coordinate

Verified

Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org. Use when the user asks to set up CMDB, enable Configuration Management Database, configure the ITSM CMDB, onboard CMDB from scratch, wants a guided walkthrough of CMDB enablement, or asks what CMDB setup steps are available. Triggers on: set up CMDB, enable CMDB, configure CMDB, CMDB onboarding, Configuration Management Database setup, ITSM CMDB walkthrough. DO NOT TRIGGER when: the user asks about a specific CMDB sub-step directly (e.g. only installing a bundle, only assigning permission sets), CMDB record CRUD (creating CIs, relationships), Discovery/Service Graph Connector configuration, or general ITSM queries without CMDB setup intent.

FileKindSize
SKILL.mdskill md11.9 KB
examples/output-templates.mdmarkdown4.8 KB

examples/output-templates.md

View on GitHub
# Output Templates — service-itsm-agentic-setup-cmdb-coordinate

Emit one of these text blocks at the corresponding step in the workflow. Only features with a
working child skill appear — hide placeholder rows.

## Feature menu (Behavior step 2)

```text
CMDB Setup (via service-itsm-agentic-setup-cmdb-coordinate)

Here are the features available for CMDB. Select one or more to configure:

┌───┬───────────────────────────────┬──────────────────────────────────────────────────┬──────────┐
│ # │ Feature                       │ Description                                      │ Status   │
├───┼───────────────────────────────┼──────────────────────────────────────────────────┼──────────┤
│ 1 │ CMDB feature enablement       │ Verify org SKU, provision the CMDB tenant, and   │ Not done │
│   │                               │ turn on the service-cloud-cmdb feature           │          │
│ 2 │ CMDB Foundation bundle        │ Install the CMDB Foundation base content bundle  │ Not done │
│   │                               │ (CI types, layouts, sample records)              │          │
│ 3 │ User CMDB access              │ Assign CMDB permission sets and permission-set   │ Not done │
│   │                               │ licenses to a specific user                      │          │
└───┴───────────────────────────────┴──────────────────────────────────────────────────┴──────────┘

Reply with the numbers of the features you want to set up (one or more, e.g. `1` or `1, 2, 3`).
```

## Post-feature progress (Behavior step 4)

Example after CMDB feature enablement completes:

```text
CMDB feature — enabled successfully
(via service-itsm-agentic-setup-cmdb-configure)

┌───┬───────────────────────────────┬──────────┐
│ # │ Feature                       │ Status   │
├───┼───────────────────────────────┼──────────┤
│ 1 │ CMDB feature enablement       │ Done     │
│ 2 │ CMDB Foundation bundle        │ Not done │
│ 3 │ User CMDB access              │ Not done │
└───┴───────────────────────────────┴──────────┘

CMDB is enabled. Next up: install the CMDB Foundation base content bundle so
the org has CI types, page layouts, and sample records to work with.
```

## Completion summary (Behavior step 5)

The completion summary fires either (a) after every feature completes, or (b) when the user says
they are finished — even if some features are still `Not done`. When rendering:

- Substitute each feature's row with its actual tracked status: `Done`, `In progress`, or `Not done`.
  Do NOT hard-code `Done`.
- Choose the header line based on whether every feature is `Done`:
  - All features `Done` → `CMDB Setup — Complete`
  - Any feature still `Not done` or `In progress` → `CMDB Setup — Finished`
- Choose the closing line based on state:
  - All `Done` → `Your CMDB setup is complete.`
  - Otherwise → `You have finished the features you selected. The remaining features can be resumed later by re-invoking this orchestrator.`

Example — user finished after enabling the feature and installing the bundle (User CMDB access stayed `Not done`):

```text
CMDB Setup — Finished
(via service-itsm-agentic-setup-cmdb-coordinate)

┌───────────────────────────────┬──────────┐
│ Feature                       │ Status   │
├───────────────────────────────┼──────────┤
│ CMDB feature enablement       │ Done     │
│ CMDB Foundation bundle        │ Done     │
│ User CMDB access              │ Not done │
└───────────────────────────────┴──────────┘

You have finished the features you selected. The remaining features can be
resumed later by re-invoking this orchestrator.
```
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall