Agent skill

Service Itsm Agentic Setup Cmdb Coordinate

by forcedotcom in forcedotcom/sf-skills

Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org.

Apache-2.0Auto-check passedSales & Support

Install Service Itsm Agentic Setup Cmdb Coordinate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .claude/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
service-itsm-agentic-setup-cmdb-coordinate
GitHub stars
1.1k
Token cost
~3k tokens
SKILL.md length
1,098 words
Files
2
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org.

  • Works in 6 steps: Extract context from conversation → Confirm the target org → Present the CMDB setup menu → …
  • The user asks to set up CMDB
  • SKILL.md covers Goal, The CMDB prerequisite stack…, Behavior and Feature dependencies &…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Service Itsm Agentic Setup Cmdb Coordinate is an agent skill from forcedotcom/sf-skills. 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…

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `examples/output-templates.md`).

It sits in Sales & Support. It works with Salesforce and Model Context Protocol. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • The user asks to set up CMDB
  • Enable Configuration Management Database
  • Configure the ITSM CMDB
  • Onboard CMDB from scratch

Example prompts

  • “/service-itsm-agentic-setup-cmdb-coordinate”

Requirements

  • Pre-approved tools (allowed-tools): AskUserQuestion

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Extract context from conversation
  2. Confirm the target org
  3. Present the CMDB setup menu
  4. Delegate to child skills
  5. After each layer completes
  6. Completion summary

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Service Itsm Agentic Setup Cmdb Coordinate loads about 3k tokens when it runs. Until then it costs about 209 tokens; SKILL.md has 1,098 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~209
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 1,098 words, ~3,030 tokens.

Download SKILL.mdSave it as .claude/skills/service-itsm-agentic-setup-cmdb-coordinate/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
service-itsm-agentic-setup-cmdb-coordinate
description
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.
allowed-tools
AskUserQuestion
metadata.version
1.1
metadata.domains
Service
metadata.relatedSkills
service-itsm-agentic-setup-cmdb-access-assign, service-itsm-agentic-setup-cmdb-bundle-deploy, service-itsm-agentic-setup-cmdb-configure…

CMDB Setup Orchestrator (Service Cloud ITSM)

Guide the user through enabling the Configuration Management Database (CMDB) in Service Cloud ITSM by presenting the ordered setup layers, delegating each to a specialized child skill, and tracking progress until CMDB is usable end-to-end. Each child skill runs through the Salesforce-hosted Headless-360 MCP server, so the same flow works against production and sandbox — the org is bound to the current MCP session, with no per-user MCP install.

Goal

Act as the top-level coordinator for CMDB enablement. Present the user with the ordered layers, invoke the appropriate child skill for each, verify the layer succeeded before moving on, and after each layer completes return to the menu with updated progress until CMDB is ready or the user stops.

The CMDB prerequisite stack (why order matters)

CMDB is gated by a 4-layer stack. Every CMDB Connect API checks orgHasCMDBEnabled, which is orgHasCMDBPermission && OrgPreferences.CMDBEnabled. Failing the gate returns 403 FUNCTIONALITY_NOT_ENABLED. The layers must be satisfied in order:

text
Layer 0  Org SKU / license      Org perm ITSrvcsCnfgMgmnt must already be granted (edition/
                                license/template). NOT settable by any API — verify only.
Layer 1  Tenant provisioning    CMDB tenant must reach status PROVISIONED (async).
Layer 2  Feature enable         Enable feature service-cloud-itsm-cmdb-integration. This is
                                what internally sets CMDBEnabled and lifts the 403 gate.
Layer 3  User access            Assign the PSL + CMDB permission sets to the user(s).
Layer 4  Content bundles        Install the CMDB Foundation (base) content bundle.
Layer 5  Asset Discovery        Enable feature service-cloud-itsm-discovery-integration and grant
                                Discovery page access (IT Service Discovery Manager permission set).
                                Recommended last, but a direct enable CASCADE-ENABLES the base CMDB
                                feature — it needs only Layer 0 (license) + Layer 1 (provisioned
                                tenant), NOT Layers 2–4 done first. Never claim a direct enable
                                "will fail"; only a genuine blocker (e.g. tenant not provisioned) stops it.

Layer 0 is a hard prerequisite: if the org was not born with the CMDB SKU, no API can grant it and setup cannot proceed. The orchestrator surfaces this clearly and stops.

Behavior

1. Extract context from conversation

Before presenting options, scan chat history for:

  • The target org (alias/username) — required by every child skill
  • Which layers are already done (skip or mark as done)
  • Any constraints the user mentioned (e.g. "just enable it, we'll assign users later")

Derive layer status from the most recent layer activity in the transcript. On a long or resumed conversation (e.g. a headless session continued later), do not treat an earlier-highlighted layer as still current — re-derive which layer is active from the latest child-skill result, and if it is ambiguous, re-confirm with the user before re-presenting the menu.

2. Confirm the target org

CMDB enablement performs writes against a real org (tenant provisioning, feature enable, permission-set assignment, bundle install). Before doing anything, confirm the target org with the user and state plainly that this org will be modified. Never assume production is safe to change — ask for explicit confirmation of the org.

3. Present the CMDB setup menu

Show the ordered layers and their status:

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

Target org: <org>   (all steps below run against this org)

CMDB is set up in ordered layers, each building on the earlier ones (Asset Discovery is the
exception — see its note below):
#LayerWhat it doesStatus
0License checkConfirm this org is licensed for CMDB (set by edition/license — can't be turned on)Pending
1–2Provision & enable CMDBSet up the CMDB tenant, then turn on the CMDB feature so it's available to usePending
3Assign user accessGrant CMDB access to the chosen usersPending
4Install content bundleInstall the CMDB Foundation (base) contentPending
5Enable Asset DiscoveryTurn on asset discovery and grant Discovery page access (recommended last; enabling it directly turns the base CMDB feature on too — needs only the license and a provisioned tenant, not the other layers first)Pending
text
I recommend running these in order. Where would you like to start (or shall I run 1 → 5)?

Render one row per layer with a single-line cell — do not split a layer across stacked rows or wrap a cell onto a second line. Present the combined provision-and-enable step as the single row 1–2. Only show layers that have a corresponding, working child skill. Do NOT show placeholder layers.

4. Delegate to child skills
LayerChild skill
0 (org SKU check) + 1 (tenant provisioning) + 2 (feature enable)service-itsm-agentic-setup-cmdb-configure
3 (user access)service-itsm-agentic-setup-cmdb-access-assign
4 (content bundle)service-itsm-agentic-setup-cmdb-bundle-deploy
5 (asset discovery)service-itsm-agentic-setup-cmdb-discovery-configure

service-itsm-agentic-setup-cmdb-configure owns the Layer 0 gate. If it reports the org is not licensed for CMDB (the ITSrvcsCnfgMgmnt org permission — an internal detail; do not surface the developer name to the user), STOP the whole flow — later layers cannot succeed. Relay its plain-language message and do not attempt Layers 3 or 4.

5. After each layer completes
  1. Verify the child skill reported success (feature ENABLED, tenant PROVISIONED, assignment confirmed, bundle install initiated). If it failed, stop and surface the failure — do not advance.
  2. Update status — mark the completed layer as "Done".
  3. Suggest the next step in dependency order.
  4. Re-present the menu with updated status.
Show full SKILL.md (442 more words)Show less
6. Completion summary

When all available layers are done (or the user stops), present a final summary:

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

Target org: <org>
#LayerStatus
0License checkDone
1–2Provision & enable CMDBDone
3User accessDone
4Content bundle (base)Done
5Asset Discovery + accessDone
text
CMDB is enabled and ready. Users with the assigned permission sets can now work with
Configuration Items. Next, you can model CIs, identification rules, and relationships.

text
0. Org SKU check          (prerequisite — hard stop if missing; no API can grant it)
1. Tenant provisioning    (async infra; must reach PROVISIONED)
2. CMDB feature enable     (sets CMDBEnabled; lifts the 403 gate — bundles/CI APIs stay 403 until this)
3. User access             (PSL + permission sets; without these users can't see CMDB)
4. Content bundle          (CMDB Foundation base; requires Layer 2 — bundle APIs 403 until enabled)
5. Asset Discovery         (enable service-cloud-itsm-discovery-integration and grant Discovery page
                           access via the IT Service Discovery Manager permission set; recommended
                           last, but a direct enable CASCADE-ENABLES the base CMDB feature — needs
                           only Layer 0 license + Layer 1 provisioned tenant, not Layers 2–4; never
                           tell the user a direct enable "will fail")

Layers 1 and 2 are handled together by service-itsm-agentic-setup-cmdb-configure because Layer 2 cannot succeed until Layer 1 reaches PROVISIONED. Present them as one step.


Rules

  • ALWAYS show "(via service-itsm-agentic-setup-cmdb-coordinate)" in the header so the user knows this skill is active
  • ALWAYS confirm the target org before any layer runs, and state that the org will be modified
  • ALWAYS present the menu before acting — do not assume which layer the user wants
  • NEVER run a layer without the user selecting it (or confirming "run all")
  • NEVER advance past a failed layer — stop, explain in plain language, and offer next steps
  • If Layer 0 fails (org lacks ITSrvcsCnfgMgmnt), STOP entirely and explain that this is a license/edition prerequisite that no API can grant
  • If a child skill reports a prerequisite gap or a failure, relay it to the user in friendly, actionable terms — do not bury the error
  • When the user asks to run Layer 5 (Asset Discovery) directly, do NOT warn that it "will fail" or "error out" without the earlier layers, and do NOT push "run the full flow" as a precondition. Enabling Discovery cascade-enables the base CMDB feature; it needs only Layer 0 (license) and a Layer 1 provisioned tenant. Delegate straight to service-itsm-agentic-setup-cmdb-discovery-configure, which reads the feature status first and stops only on a genuine blocker (e.g. tenant not provisioned)
  • Track progress across the conversation — do not re-present completed layers as "Pending". Re-derive the current layer from the latest child-skill activity, not from a previously rendered highlight; on a resumed or long conversation, do not assume the last-highlighted layer is still current — if ambiguous, re-confirm with the user
  • Do NOT expose internal technical jargon in user-facing output. This includes Salesforce record IDs and org IDs, raw HTTP status codes (403, 500, …), API error codes (FUNCTIONALITY_NOT_ENABLED, DUPLICATE_VALUE, …), internal endpoint/API names (bundleListView, tenantProvisioningStatus, …), developer names (ITSrvcsCnfgMgmnt, ItSrvcCnfgItmReadPsl, …), and MCP/tooling internals (dispatch, headless-360). Translate everything to plain, human-readable language — e.g. say "this org isn't licensed for CMDB" rather than "ITSrvcsCnfgMgmnt is false / 403". Child-skill names shown as next-step pointers are fine. Keep all such technical detail in your own reasoning, not on screen.

Adding new layers

When new CMDB child skills are created (e.g. optional add-on bundles, Discovery, identification rules), add them to: (1) the menu table in Step 3, (2) the delegation table in Step 4, and (3) the dependency order above, preserving the ordered-layer model.

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/service-itsm-agentic-setup-cmdb-coordinate of forcedotcom/sf-skills.

  • SKILL.md
  • examples/output-templates.md

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Service Itsm Agentic Setup Cmdb Coordinate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Service Itsm Agentic Setup Cmdb Coordinate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Service Itsm Agentic Setup Cmdb Coordinate this skillforcedotcom/sf-skills1.1k—~3kAutomated safety check: PassApache-2.0
Churn Riskindranilbanerjee/digital-marketing-pro8551 repos~2.4kAutomated safety check: PassMIT
Lead Importindranilbanerjee/digital-marketing-pro8551 repos~3.3kAutomated safety check: PassMIT
Pipeline Updateindranilbanerjee/digital-marketing-pro8551 repos~3.3kAutomated safety check: PassMIT
Zsxqunnoo/zsxq-skill304—~3.8kAutomated safety check: PassMIT
Agentforce GenerateSalesforceAIResearch/agentforce-adlc1141 repos~7.4kAutomated safety check: PassCustom licence

Similar skills

  • Churn Risk

    indranilbanerjee/digital-marketing-pro

    Score customer segments for churn risk from behavioral signals — email engagement decline, purchase recency, usage drops, support sentiment — producing a 0-100 risk scorecard with four tiers…

    855 GitHub starsUsed in 1 repo~2.4k tokens
    Sales & SupportAuto-check passed
  • Lead Import

    indranilbanerjee/digital-marketing-pro

    Import leads into Salesforce, HubSpot, Zoho, or Pipedrive with validation, deduplication against existing CRM records, lead scoring, consent and compliance checks, and source attribution — then push…

    855 GitHub starsUsed in 1 repo~3.3k tokens
    Sales & SupportAuto-check passed
  • Pipeline Update

    indranilbanerjee/digital-marketing-pro

    Update CRM deals — move stages, change values and close dates, attach notes and activities, create follow-up tasks — with validation against pipeline rules, a before-and-after comparison, and…

    855 GitHub starsUsed in 1 repo~3.3k tokens
    Sales & SupportAuto-check passed
  • Zsxq

    unnoo/zsxq-skill

    知识星球 CLI(zsxq-cli)与底层接口完整操作指南,涵盖星球和内容管理、Skill Pay 微信支付场景。当用户提到知识星球、zsxq、小密圈、星球、登录/认证、发帖、评论、回答、编辑、删除主题、定时发布/定时任务/定时回答、投票、问答主题、markdown 正文、AI…

    304 GitHub stars~3.8k tokensUpdated 17 days ago
    Sales & SupportAuto-check passed
  • Agentforce Generate

    SalesforceAIResearch/agentforce-adlc

    Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script.

    114 GitHub starsUsed in 1 repo~7.4k tokens
    Agent WorkflowsAuto-check passed
  • Sales Os

    romangojiberryAI/gojiberryai-sales-os

    A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.

    138 GitHub stars~2k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 251 skills in this repo
  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: notes
  • Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated yesterday
    Auto-check: notes
  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Service Itsm Agentic Setup Cmdb Coordinate

What does Service Itsm Agentic Setup Cmdb Coordinate do?

Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org. Service Itsm Agentic Setup Cmdb Coordinate is an agent skill from forcedotcom/sf-skills. Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org.

When should I use Service Itsm Agentic Setup Cmdb Coordinate?

Service Itsm Agentic Setup Cmdb Coordinate fits situations like: the user asks to set up CMDB; enable Configuration Management Database; configure the ITSM CMDB; onboard CMDB from scratch.

How do I install Service Itsm Agentic Setup Cmdb Coordinate in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a claude-code`. Or copy the skill folder (skills/service-itsm-agentic-setup-cmdb-coordinate in forcedotcom/sf-skills) into .claude/skills/service-itsm-agentic-setup-cmdb-coordinate in your project. Claude Code loads it when a task matches its description.

How do I install Service Itsm Agentic Setup Cmdb Coordinate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a codex`. Or copy the skill folder (skills/service-itsm-agentic-setup-cmdb-coordinate in forcedotcom/sf-skills) into .agents/skills/service-itsm-agentic-setup-cmdb-coordinate in your project. Codex loads it when a task matches its description.

Can I use Service Itsm Agentic Setup Cmdb Coordinate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/service-itsm-agentic-setup-cmdb-coordinate, .gemini/skills/service-itsm-agentic-setup-cmdb-coordinate, .github/skills/service-itsm-agentic-setup-cmdb-coordinate and .opencode/skills/service-itsm-agentic-setup-cmdb-coordinate in your project.

What does Service Itsm Agentic Setup Cmdb Coordinate need to run?

SKILL.md names no scripts, command-line tools or credentials: Service Itsm Agentic Setup Cmdb Coordinate is instructions for the agent only. Its frontmatter pre-approves these tools: AskUserQuestion.

Does Service Itsm Agentic Setup Cmdb Coordinate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Service Itsm Agentic Setup Cmdb Coordinate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Service Itsm Agentic Setup Cmdb Coordinate use?

Service Itsm Agentic Setup Cmdb Coordinate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Service Itsm Agentic Setup Cmdb Coordinate use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Service Itsm Agentic Setup Cmdb Coordinate?

Skills that share tags, products or a category with Service Itsm Agentic Setup Cmdb Coordinate: Churn Risk (indranilbanerjee/digital-marketing-pro, 855 stars), Lead Import (indranilbanerjee/digital-marketing-pro, 855 stars), Pipeline Update (indranilbanerjee/digital-marketing-pro, 855 stars) and Zsxq (unnoo/zsxq-skill, 304 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Service Itsm Agentic Setup Cmdb Coordinate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.