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…
Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .claude/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .agents/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .agents/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .cursor/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .cursor/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/service-itsm-agentic-setup-cmdb-coordinate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .gemini/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .gemini/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .github/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .github/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-coordinate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-agentic-setup-cmdb-coordinate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/service-itsm-agentic-setup-cmdb-coordinate .opencode/skills/service-itsm-agentic-setup-cmdb-coordinate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "service-itsm-agentic-setup-cmdb-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-agentic-setup-cmdb-coordinate into .opencode/skills/service-itsm-agentic-setup-cmdb-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-agentic-setup-cmdb-coordinate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
service-itsm-agentic-setup-cmdb-coordinateOrchestrator 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. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
AskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 1,098 words, ~3,030 tokens.
.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.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.
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.
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:
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.
Before presenting options, scan chat history for:
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.
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.
Show the ordered layers and their status:
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):| # | Layer | What it does | Status |
|---|---|---|---|
| 0 | License check | Confirm this org is licensed for CMDB (set by edition/license — can't be turned on) | Pending |
| 1–2 | Provision & enable CMDB | Set up the CMDB tenant, then turn on the CMDB feature so it's available to use | Pending |
| 3 | Assign user access | Grant CMDB access to the chosen users | Pending |
| 4 | Install content bundle | Install the CMDB Foundation (base) content | Pending |
| 5 | Enable Asset Discovery | Turn 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 |
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.
| Layer | Child 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.
ENABLED, tenant PROVISIONED, assignment
confirmed, bundle install initiated). If it failed, stop and surface the failure — do not advance.When all available layers are done (or the user stops), present a final summary:
CMDB Setup — Complete (via service-itsm-agentic-setup-cmdb-coordinate)
Target org: <org>| # | Layer | Status |
|---|---|---|
| 0 | License check | Done |
| 1–2 | Provision & enable CMDB | Done |
| 3 | User access | Done |
| 4 | Content bundle (base) | Done |
| 5 | Asset Discovery + access | Done |
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.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.
ITSrvcsCnfgMgmnt), STOP entirely and explain that this is a
license/edition prerequisite that no API can grantservice-itsm-agentic-setup-cmdb-discovery-configure,
which reads the feature status first and stops only on a genuine blocker (e.g. tenant not provisioned)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.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
SKILL.md and 1 other file in skills/service-itsm-agentic-setup-cmdb-coordinate of forcedotcom/sf-skills.
Open the folder on GitHubat commit e5164d9
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Service Itsm Agentic Setup Cmdb Coordinate this skillforcedotcom/sf-skills | 1.1k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Churn Riskindranilbanerjee/digital-marketing-pro | 855 | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Lead Importindranilbanerjee/digital-marketing-pro | 855 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Pipeline Updateindranilbanerjee/digital-marketing-pro | 855 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Zsxqunnoo/zsxq-skill | 304 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Agentforce GenerateSalesforceAIResearch/agentforce-adlc | 114 | 1 repos | ~7.4k | Automated safety check: Pass | Custom licence |
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…
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…
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…
unnoo/zsxq-skill
知识星球 CLI(zsxq-cli)与底层接口完整操作指南,涵盖星球和内容管理、Skill Pay 微信支付场景。当用户提到知识星球、zsxq、小密圈、星球、登录/认证、发帖、评论、回答、编辑、删除主题、定时发布/定时任务/定时回答、投票、问答主题、markdown 正文、AI…
SalesforceAIResearch/agentforce-adlc
Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script.
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Works with
Categories
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.