New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Service Itsm Teams Coordinate

by forcedotcom in forcedotcom/sf-skills

End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the…

Apache-2.0Auto-check passedSales & Support

Install Service Itsm Teams Coordinate

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

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills service-itsm-teams-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-teams-coordinate .claude/skills/service-itsm-teams-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-teams-coordinate
GitHub stars
1.1k
Token cost
~3.1k tokens
SKILL.md length
1,605 words
Files
2
Skills in repo
252
Repo updated
First seen
Licence
Apache-2.0

At a glance

End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the…

  • Works in 8 steps: Enable the Teams for Employee Service Go… → Microsoft Entra app + Named Credentials… → Set up IT Desk (fulfiller side) ⟶ HALT 2 → …
  • The user asks to set up Microsoft Teams for ITSM end to end
  • SKILL.md covers Goal, Core operating rule — run…, The flow (run in this order) and After each stage, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Service Itsm Teams Coordinate is an agent skill from forcedotcom/sf-skills. End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the Microsoft Entra app, populate Named Credentials, configure the IT Desk and IT Service checklists, turn on Swarming, and optionally embed the Agentforce agent) in one continuous pass, stopping only at the points a human must act. Use when the user asks to set up Microsoft Teams for ITSM end to end, 'set up teams for it…

Its SKILL.md is about 3.1k 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, covering CRM management and End-to-end testing. It works with Salesforce, Microsoft Teams and Microsoft Entra ID. 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 Microsoft Teams for ITSM end to end
  • Set up teams for it service
  • Do the whole teams itsm setup
  • Configure microsoft teams for employee service

Example prompts

  • “set up teams for it service”
  • “do the whole teams itsm setup”
  • “configure microsoft teams for employee service”
  • “/service-itsm-teams-coordinate”

Requirements

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

Workflow steps

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

  1. Enable the Teams for Employee Service Go feature
  2. Microsoft Entra app + Named Credentials ⟶ HALT 1
  3. Set up IT Desk (fulfiller side) ⟶ HALT 2
  4. Set up IT Service (employee side) ⟶ HALT 3
  5. Ask the user to verify login
  6. Tell the user the IT Desk "Ask Agentforce" agent works automatically
  7. Offer the IT Service Agentforce agent ⟶ BRANCH
  8. Build the IT Service embedded agent (only if the user said yes)

What it can do on your machine

Read from SKILL.md and the folder at commit 4bbae5c. 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:

    • Read
    • 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 Teams Coordinate loads about 3.1k tokens when it runs. Until then it costs about 242 tokens; SKILL.md has 1,605 words of instructions outside code blocks.

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

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 4bbae5c, republished under its Apache-2.0 licence (© forcedotcom). 1,605 words, ~3,082 tokens.

Download SKILL.mdSave it as .claude/skills/service-itsm-teams-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-teams-coordinate
description
End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the Microsoft Entra app, populate Named Credentials, configure the IT Desk and IT Service checklists, turn on Swarming, and optionally embed the Agentforce agent) in one continuous pass, stopping only at the points a human must act. Use when the user asks to set up Microsoft Teams for ITSM end to end, 'set up teams for it service', 'do the whole teams itsm setup', 'configure microsoft teams for employee service', or wants a guided Teams ITSM walkthrough. Delegates each stage to a specialized child skill while driving the sequence itself. DO NOT TRIGGER when the user asks to enable Teams alone, configure just the IT Desk or IT Service checklist alone, or enable Swarming alone — delegate directly to the specific child skill in those cases.
allowed-tools
Read, AskUserQuestion
metadata.version
2.0
metadata.domains
Service
metadata.relatedSkills
service-itsm-swarming-configure, service-itsm-teams-configure, service-itsm-teams-debug, service-itsm-teams-employee-agent-configure…

Microsoft Teams for ITSM — End-to-End Setup Autopilot

Drive the complete Microsoft Teams for Employee Service (ITSM) setup as one continuous flow. Delegate each stage to its specialized child skill, but own the sequence yourself and keep going through every stage without stopping to ask permission between stages. Halt only at the points where a human genuinely must act — nowhere else.

Goal

Take the user from nothing to a working Teams ITSM integration (IT Desk + IT Service, Swarming, and — if they want it — the embedded Agentforce agent) in a single guided run. The child skills carry the verified API detail; this skill is the conductor that runs them in order and manages the handoffs.

Core operating rule — run continuously, halt only where required

Do everything with no midway stop unless the user must supply something or perform an off-platform action. Do not re-present a menu between stages, do not ask "shall I continue?" after each stage, and do not ask the user to click Setup toggles this skill's children can do via API. Move straight from one stage to the next, reporting progress as you go.

There are exactly three mandatory halts and one branch in the whole flow:

  • HALT 1 — Azure/Entra app (Stage 2): you give the user the app-registration instructions and wait for them to register the app and provide the credentials. No Salesforce API can do this. The Client ID and Tenant ID are non-secret identifiers and may be given in chat; the Client Secret is a confidential credential — NEVER ask for it in the conversation. The agent gives the user one exact copy-paste command that writes the secret to a gitignored secret file (! umask 077; printf '%s' 'PASTE-SECRET' > <secret-file> && echo written) and reads it from that file. Keep the leading ! — it runs the line in this session's Bash so the file persists. The agent never prints, echoes, or logs the value.
  • HALT 2 — IT Desk app install (Stage 3): you give the Microsoft Marketplace link and wait for the user to reply "installed". No API installs a Teams app into a tenant catalog.
  • HALT 3 — IT Service app install (Stage 4): same as HALT 2, for the IT Service app.
  • BRANCH — IT Service Agentforce agent (Stage 7): the IT Desk agent works automatically, but the IT Service embedded agent is pending work; ask the user whether to do it, and only run Stage 8 if they say yes.

If the user goes silent at a halt, stop and wait — do not fabricate the value or skip ahead. Every other transition is automatic.

Within each stage, execute one operation at a time. The child skills make real, state-changing API calls; run a single operation, confirm it succeeded, then proceed — never batch state-changing calls into one parallel block. "No midway stop" means no permission gate between stages, not firing writes in parallel.

The flow (run in this order)

Stage 1 — Enable the Teams for Employee Service Go feature

Invoke service-itsm-teams-configure for the feature-enable half only (its Steps 1–3): enable service-cloud-itsm-teams-integration and confirm ITSMTeamsEnabled reads true. Report progress, then continue straight into Stage 2 — do not stop here.

Stage 2 — Microsoft Entra app + Named Credentials ⟶ HALT 1

Still within service-itsm-teams-configure (its Step 4a): give the user the exact Azure/Entra app-registration clicks including the Microsoft Graph permissions it lists, and HALT until they provide the credentials. The Client ID and Tenant ID are non-secret identifiers — accept them in chat. The Client Secret is confidential: never request it in the conversation. Give the user one exact copy-paste command that writes it to a gitignored secret file (! umask 077; printf '%s' 'PASTE-SECRET' > <secret-file> && echo written) and read it from that file. Keep the leading ! — it runs the line in this session's Bash so the file persists. Never print or echo it. The moment the identifiers are given and the secret is in the file:

  • Write those values into the MSTeamsSetupClientCredentialsEC Named Credential and the microsoft_auth_provider Auth Provider yourself, via API — nothing manual (the child skill's Step 5 and its azure-credential-population reference carry the exact API bodies). Read the secret from the file at call time — do not inline the raw value into any logged text.
  • Give the user the static Grant Admin Consent link and register the preferred site (child Step 5). Then continue to Stage 3 automatically.
Stage 3 — Set up IT Desk (fulfiller side) ⟶ HALT 2

Invoke service-itsm-teams-itdesk-configure. Drive its whole checklist:

  • Turn on the OrgHasITSMFulfillerTeams org preference (via API).
  • Manage User Access — assign the fulfiller permission sets to the confirmed user(s): TeamsForITSrvcsUser + MicrosoftGraphAccess, plus the API Enabled login permission set (commonly Teams_Employee_ApiAccess) — required for login, not optional.
  • Turn on Swarming — this stage includes service-itsm-swarming-configure (enables service-cloud-swarming and sets SWARM_COLLABORATION_TOOL = "Teams").
  • Give the IT Desk Microsoft Marketplace link + help doc, tell the user the Azure account email must match the Salesforce user's email/Username (SSO resolves MS UPN → Username), and HALT until the user replies "installed." Then continue to Stage 4.
Stage 4 — Set up IT Service (employee side) ⟶ HALT 3

Invoke service-itsm-teams-itservice-configure. Drive its whole checklist:

  • Turn on the OrgHasEmployeeServiceTeams org preference (via API).
  • Manage User Access — assign the employee permission set to the confirmed UEL user(s): TeamsForEmployeeUser (the dialog assigns only this one — not MicrosoftGraphAccess), plus the API Enabled login permission set the child's login prerequisites require.
  • Select the Digital Experience Site (SLACK_PREFERRED_SITE) via API.
  • Give the IT Service Microsoft Marketplace link + help doc, repeat the email-must-match note, and HALT until the user replies "installed." Then continue to Stage 5.
Stage 5 — Ask the user to verify login

Ask the user to open the IT Desk app in Teams and sign in with the fulfiller credentials, and the IT Service app with the UEL/employee credentials, and confirm both load. If either fails, route to service-itsm-teams-debug for the pass/fail login diagnostic before proceeding.

Show full SKILL.md (643 more words)Show less
Stage 6 — Tell the user the IT Desk "Ask Agentforce" agent works automatically

Once IT Desk login is confirmed, tell the user that IT Desk's Ask Agentforce works automatically — no further setup is needed on the fulfiller side.

Stage 7 — Offer the IT Service Agentforce agent ⟶ BRANCH

Tell the user the IT Service side has pending work: the embedded Agentforce agent ("Ask AI Agent") does not reply until its messaging channel + Key Set + Embedded Service Deployment are built. Ask whether they want to set it up now (use AskUserQuestion). If no, go to the completion summary. If yes, run Stage 8.

Stage 8 — Build the IT Service embedded agent (only if the user said yes)

Invoke service-itsm-teams-employee-agent-configure. It builds — 100% via API — the Web messaging channel with User Verification ON + a JWKS_URL Key Set, the Teams_AgentForce Embedded Service Deployment (publish), the routing flow, and the Agent Access permission set on the portal user. Then tell the user to retest from a brand-new Teams chat to confirm the agent replies.

After each stage

  • Report the child's ACTUAL verdict — never assume "Done." A stage is complete only when its child skill explicitly reported success. If a child reports blocked (most commonly Stage 2 while the Entra app is unregistered, or a halt awaiting "installed"), keep that stage Blocked/waiting and hold at the halt — do not mark it done and do not skip ahead.
  • Do not re-present a menu. State what just finished and what you're doing next, then do it.
  • Keep the report tight — summarize, don't transcribe. Report each stage as a one-line status in the stage-progress table plus at most a short sentence of context; do not paste the child skill's API request/response bodies, tool-call logs, or step-by-step internals into the report — that detail lives in the child skill, and re-narrating it here is the single biggest source of a bloated, low-signal report. The reader needs what happened and what's next, not a replay of every call.

Completion summary

When the flow ends (Stage 7 "no", or Stage 8 done, or a hard block the user chose not to resolve), summarize each stage's real status. Header: all stages complete → Complete; any stage still blocked/waiting → Incomplete (action required) with the exact next step; otherwise Finished.

Rules

  • ALWAYS show "(via service-itsm-teams-coordinate)" in the setup header.
  • Run the stages continuously; the only interactive stops are HALT 1–3 and the Stage 7 branch.
  • NEVER ask the user to click a Setup toggle a child skill can flip via API (feature enable, org prefs, permission-set assignment, digital site, named credentials).
  • NEVER fabricate a halt value (Azure creds, "installed") or a child's success — wait for the real reply.
  • Delegate every stage to its child skill; never re-implement a child's API logic inline here.
  • Track progress across the conversation — do not re-run a completed stage.
  • Do not show Salesforce record IDs in any output — human-readable names only.
  • At Stages 3 and 4, always include the Azure-email-must-match-Salesforce-email note with the marketplace link, since a mismatch is a common silent login failure.

Verification checklist

Before emitting any progress message or summary, confirm:

  • The header line ends with (via service-itsm-teams-coordinate).
  • The flow is running continuously — no permission gate was inserted between stages beyond the three defined halts and the Stage 7 branch.
  • Each stage's status reflects the child's actual verdict (In progress, Blocked/waiting, or Done) — not a hard-coded default.
  • A stage waiting on a halt (Azure creds, "installed") is shown as waiting, never Done.
  • Stages 3 and 4 each surfaced the marketplace link and the email-must-match note.
  • The Stage 7 branch was offered as a yes/no question, and Stage 8 ran only on an explicit "yes."
  • The next action delegates to a child skill; features are never configured inline here.
  • No Salesforce record IDs appear in the output — human-readable names only.

Reference File Index

FileWhen to read
examples/output-templates.mdProgress and completion-summary text blocks

© 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-teams-coordinate of forcedotcom/sf-skills.

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

Open the folder on GitHubat commit 4bbae5c

Compare with similar skills

Service Itsm Teams 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 Teams Coordinate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Service Itsm Teams Coordinate this skillforcedotcom/sf-skills1.1k—~3.1kAutomated safety check: PassApache-2.0
Sf ApexJaganpro/sf-skills424—~2kAutomated safety check: PassMIT
Sf DebugJaganpro/sf-skills424—~1.3kAutomated safety check: PassMIT
Pipeline Reviewgooseworks-ai/goose-skills1.2k1 repos~6.9kAutomated safety check: PassMIT
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT
Sf DatacloudJaganpro/sf-skills424—~2.7kAutomated safety check: PassMIT

Similar skills

  • Sf Apex

    Jaganpro/sf-skills

    Generates and reviews Salesforce Apex code with 150-point scoring.

    424 GitHub stars~2k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Sf Debug

    Jaganpro/sf-skills

    Salesforce debug log analysis and troubleshooting with 100-point scoring.

    424 GitHub stars~1.3k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Pipeline Review

    gooseworks-ai/goose-skills

    Pipeline analysis composite. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~6.9k tokens
    Sales & SupportAuto-check passed

  • Soql Lib Query Builder

    beyond-the-cloud-dev/soql-lib

    Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).

    154 GitHub stars~4.3k tokensUpdated 7 days ago
    Sales & SupportAuto-check passed

  • Sf Datacloud

    Jaganpro/sf-skills

    Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.

    424 GitHub stars~2.7k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Soql Lib Selector

    beyond-the-cloud-dev/soql-lib

    Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.

    154 GitHub stars~2k tokensUpdated 7 days ago
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 252 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

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated yesterday
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    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

Works with

Categories

Questions about Service Itsm Teams Coordinate

What does Service Itsm Teams Coordinate do?

End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the…. Service Itsm Teams Coordinate is an agent skill from forcedotcom/sf-skills. End-to-end autopilot orchestrator for setting up Microsoft Teams integration in Salesforce Service Cloud ITSM — runs the whole flow (enable the Teams for Employee Service Go feature, register the Microsoft Entra app, populate Named Credentials, configure the IT Desk and IT Service checklists, turn on Swarming, and optionally embed the Agentforce agent) in one continuous pass, stopping only at the points a human must act.

When should I use Service Itsm Teams Coordinate?

Service Itsm Teams Coordinate fits situations like: the user asks to set up Microsoft Teams for ITSM end to end; set up teams for it service; do the whole teams itsm setup; configure microsoft teams for employee service.

How do I install Service Itsm Teams Coordinate in Claude Code?

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

How do I install Service Itsm Teams Coordinate in Codex?

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

Can I use Service Itsm Teams 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-teams-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-teams-coordinate, .gemini/skills/service-itsm-teams-coordinate, .github/skills/service-itsm-teams-coordinate and .opencode/skills/service-itsm-teams-coordinate in your project.

What does Service Itsm Teams Coordinate need to run?

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

Does Service Itsm Teams 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 Teams 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 Teams Coordinate use?

Service Itsm Teams 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 Teams Coordinate use?

About 3.1k 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 Teams Coordinate?

Skills that share tags, products or a category with Service Itsm Teams Coordinate: Sf Apex (Jaganpro/sf-skills, 424 stars), Sf Debug (Jaganpro/sf-skills, 424 stars), Pipeline Review (gooseworks-ai/goose-skills, 1.2k 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.

Who maintains Service Itsm Teams Coordinate?

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.