Integrations
butterbase-ai/butterbase-skills
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…
Top-level interactive coordinator for Employee Service (ITSM) channel setup.
$ npx skills add forcedotcom/sf-skills --skill service-itsm-channels-coordinate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-channels-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-channels-coordinate .claude/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .claude/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-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-channels-coordinate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-channels-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-channels-coordinate .agents/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .agents/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-coordinate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-channels-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-channels-coordinate .cursor/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .cursor/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-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-channels-coordinate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-channels-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-channels-coordinate .gemini/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .gemini/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-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-channels-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-channels-coordinate .github/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .github/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-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-channels-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-channels-coordinate .opencode/skills/service-itsm-channels-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-channels-coordinate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-channels-coordinate into .opencode/skills/service-itsm-channels-coordinate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-channels-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-channels-coordinateTop-level interactive coordinator for Employee Service (ITSM) channel setup.
Service Itsm Channels Coordinate is an agent skill from forcedotcom/sf-skills. Top-level interactive coordinator for Employee Service (ITSM) channel setup. Presents menu of channel setup options (Portal, Teams, Slack) and delegates to the corresponding skill. Use this for: 'setup ITSM channels', 'configure employee service channels', 'set up service cloud communication channels', 'I want to configure ITSM integrations', or any general request for ITSM channel/integration setup where the user hasn't specified exactly which channel they want. DO NOT TRIGGER for requests that already name a…
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support. It works with Slack, Salesforce and Microsoft Teams. 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 4bbae5c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From 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 Channels Coordinate loads about 3.2k tokens when it runs. Until then it costs about 184 tokens; SKILL.md has 1,313 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 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 1,313 words, ~3,216 tokens.
.claude/skills/service-itsm-channels-coordinate/SKILL.md (or your agent's skills folder).Interactive coordinator that presents a menu of ITSM channel setup options and delegates to the appropriate child skill based on user selection.
This coordinator can invoke three distinct channel setup skills:
Skill: experience-portal-create
What it does:
Prerequisites:
Use when: User wants to create a portal for employee self-service.
Skill: service-itsm-teams-configure
What it does:
service-cloud-itsm-teams-integration Salesforce Go feature via headless-360's
feature-enablement Connect API — the only verified path that flips ITSMTeamsEnabled (direct
PATCH of the org preference is blocked with 401)OrgHasITSMFulfillerTeams / OrgHasEmployeeServiceTeams preferencesITSMTeamsEnabled afterward and reports the remaining manual (Microsoft-side) stepsPrerequisites:
Use when: User wants Microsoft Teams integration for IT Service Desk or Employee Service apps.
Teams sub-skills service-itsm-teams-configure delegates to (surface these if the user asks for
a specific half): service-itsm-teams-itdesk-configure (fulfiller/IT Desk checklist),
service-itsm-teams-itservice-configure (employee/IT Service checklist),
service-itsm-teams-employee-agent-configure (embedded "Ask AI Agent"), and
service-itsm-teams-debug (diagnose a failing Teams setup — login, tab loading, agent, swarming, SSO).
Swarming (collaborative problem-solving) is configured inside the Teams setup flow, not as a
separate top-level channel option.
Skill: the installed Slack ITSM setup skill — resolve it from the skills catalog at delegation time by name pattern (see Choice 3 in the workflow); do not hardcode a single skill name.
What it does:
Prerequisites:
Use when: User wants Slack integration for ITSM.
Always present the menu before proceeding:
I can help you set up ITSM channels. Which channel would you like to configure?
**Choose one:**
1. **Portal Setup**
- Create Digital Experience portal for employee self-service
- Choose portal type during setup
- Prerequisites: Vary by portal type
2. **Microsoft Teams Setup**
- Enable Teams integration master toggle
- Provision authentication infrastructure
- Prerequisites: Teams ITSM licenses required
3. **Slack Setup**
- Enable Slack integration for ITSM
- Configure Slack workspace connection
- Prerequisites: Slack workspace with admin access
Please respond with the number (1, 2, or 3) of your choice.Do NOT proceed until the user provides a choice.
Based on user's choice, check prerequisites before delegating to child skills:
If prerequisites fail:
Delegation:
Invoke the experience-portal-create skill.The portal creation skill will handle all clarifying questions (portal type, name, URL prefix, etc.).
After delegation: "Success: Portal setup delegated to experience-portal-create skill. Follow the prompts to complete portal creation."
Delegation:
Invoke the service-itsm-teams-configure skill.On success: "Success: Microsoft Teams integration master toggle is enabled. Background provisioning in progress (2-5 minutes).
Next steps:
On failure: "Failed: Teams integration failed: [error details]
Resolution:
Resolve the delegation target deterministically from the skills catalog, then invoke the result. Do not decide by prose guesswork — look the skill up:
1. Query the installed skills catalog for a Slack ITSM setup skill, in priority order:
a. any skill whose name matches ^service-itsm-slack-.*-configure$ (preferred)
b. any skill whose name matches ^(setup|service)-.*slack.*(configure|enable)$
2. If the lookup returns a skill → invoke that exact skill and stop.
3. If the lookup returns nothing → fall through to the manual instructions below.Manual instructions (only if the catalog lookup returned no Slack skill): "No Slack ITSM setup skill is installed in this environment. To configure Slack manually:
User requests ITSM channel setup
↓
Present menu (3 options)
↓
User selects option (1-3)
↓
Validate prerequisites (optional)
↓
├─ Choice 1: Invoke experience-portal-create
├─ Choice 2: Invoke service-itsm-teams-configure
└─ Choice 3: Resolve the Slack skill from the catalog, then invoke it (or manual instructions)
↓
Report outcome to user
↓
Suggest next steps| Constraint | Rationale |
|---|---|
| Always present options before proceeding | User may not know what's possible or what their org supports |
| Validate prerequisites before delegating | Catch licensing/feature gaps early before invoking child skills |
| Notifications are not a menu option | ITSM notification preferences are a separate concern; route those requests to the dedicated notification-preferences skill, not through this coordinator |
| Swarming is configured inside Teams, not a top-level channel | Swarming requires Teams; it is handled within the Teams setup flow (service-itsm-teams-configure), so it is not offered as a separate menu option |
| Do not retry failed delegations | Child skills handle their own retries; surfacing error to user for decision |
| Partial success is acceptable | If Teams succeeds but Slack fails, user can retry Slack separately |
"Please choose a valid option: 1, 2, or 3."
"I've detected that your org is missing [specific requirement].
I recommend choosing [alternative option] instead, which works with your current org configuration."
"The [child skill name] encountered an error: [error message]
[Provide specific resolution steps based on error]"
"Let me help you decide:
Do you want a portal for employee self-service?
Do you want to enable a communication channel?
After completing channel setup via this coordinator:
To modify later:
Making the embedded Agentforce agent actually reply inside the Teams custom client ("Salesforce Employee Assist" / "Ask AI Agent") is the hardest, most under-documented part of Teams ITSM. It is now a dedicated skill:
→ service-itsm-teams-employee-agent-configure
The verified architecture is a Web Enhanced-messaging channel with User Verification OFF
(auth mode false) — the Teams client uses the scrt2 unauthenticated token endpoint — the
Teams_AgentForce custom-client Embedded Service Deployment, an Omni-Flow routing flow
targeting a real, Active Agentforce Employee Agent, and an Agent Access permission set
enabling that agent for the portal user. That skill also covers the key diagnostic: "agent joins
then leaves without replying" has two fixable causes — auth mode left ON (→ /eventrouter/v1/sse
401) and the portal user missing Agent Access — not an unfixable agent-runtime failure.
This coordinator:
Child skills used:
experience-portal-create — Connect APIservice-itsm-teams-configure — headless-360 (Salesforce Go feature-enablement Connect API)This is an interactive coordinator — it MUST present the menu and wait for user choice before executing anything.
Always delegate to child skills — this coordinator doesn't implement channel-specific logic; it only routes to the appropriate skill.
Some skills may not exist yet — if a skill is not found, provide manual setup instructions so the user isn't blocked.
Notifications are handled elsewhere — ITSM notification preferences are not a channel-menu option; route those requests to the dedicated notification-preferences skill.
Swarming lives inside Teams — Swarming is not a standalone menu option; it is configured within the Teams setup flow (service-itsm-teams-configure), since it requires Teams.
Prerequisites vary by channel — each channel has different licensing and feature requirements.
No retry logic — this coordinator doesn't retry failed operations. Surface the error and let user decide next steps.
Educational role — help users understand what each channel does and which prerequisites they need.
© 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
Just SKILL.md in skills/service-itsm-channels-coordinate of forcedotcom/sf-skills.
Open the folder on GitHubat commit 4bbae5c
Service Itsm Channels 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 Channels Coordinate this skillforcedotcom/sf-skills | 1.1k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Integrationsbutterbase-ai/butterbase-skills | 534 | — | ~832 | Automated safety check: Pass | MIT | |
| Airbyte AgentKilo-Org/kilo-marketplace | 190 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Services Extension Consumptionforcedotcom/salesforcedx-vscode | 1k | — | ~5k | Automated safety check: Pass | BSD-3-Clause | |
| Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib | 154 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Sf DatacloudJaganpro/sf-skills | 424 | — | ~2.7k | Automated safety check: Pass | MIT |
butterbase-ai/butterbase-skills
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…
Kilo-Org/kilo-marketplace
Drive the airbyte-agent CLI to manage Airbyte connectors, workspaces, and organizations.
forcedotcom/salesforcedx-vscode
Consume the salesforcedx-vscode-services extension API. An agent skill from forcedotcom/salesforcedx-vscode.
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
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
Top-level interactive coordinator for Employee Service (ITSM) channel setup. Service Itsm Channels Coordinate is an agent skill from forcedotcom/sf-skills. Top-level interactive coordinator for Employee Service (ITSM) channel setup.
Service Itsm Channels Coordinate fits situations like: requests that already name a specific channel; child skill (e.g.
Run `npx skills add forcedotcom/sf-skills --skill service-itsm-channels-coordinate -a claude-code`. Or copy the skill folder (skills/service-itsm-channels-coordinate in forcedotcom/sf-skills) into .claude/skills/service-itsm-channels-coordinate in your project. Claude Code loads it when a task matches its description.
Run `npx skills add forcedotcom/sf-skills --skill service-itsm-channels-coordinate -a codex`. Or copy the skill folder (skills/service-itsm-channels-coordinate in forcedotcom/sf-skills) into .agents/skills/service-itsm-channels-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-channels-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-channels-coordinate, .gemini/skills/service-itsm-channels-coordinate, .github/skills/service-itsm-channels-coordinate and .opencode/skills/service-itsm-channels-coordinate in your project.
SKILL.md names no scripts, command-line tools or credentials: Service Itsm Channels Coordinate is instructions for the agent only.
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 Channels 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 3.2k tokens (SKILL.md is roughly 13k 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 Channels Coordinate: Integrations (butterbase-ai/butterbase-skills, 534 stars), Airbyte Agent (Kilo-Org/kilo-marketplace, 190 stars), Services Extension Consumption (forcedotcom/salesforcedx-vscode, 1k stars) and Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 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,067 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 9, 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.