Teams Dev
microsoft/teams-sdk
A skill your agent uses whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions.
Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation.
Install Service Itsm Teams Debug
$ npx skills add forcedotcom/sf-skills --skill service-itsm-teams-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-teams-debug --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-teams-debug .claude/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .claude/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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-teams-debugType 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-teams-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-teams-debug --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-teams-debug .agents/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .agents/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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-teams-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-teams-debug --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-teams-debug .cursor/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .cursor/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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-teams-debug--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-teams-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills service-itsm-teams-debug --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-teams-debug .gemini/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .gemini/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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-teams-debugInstalls 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-teams-debug -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-teams-debug .github/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .github/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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-teams-debug -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-teams-debug --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-teams-debug .opencode/skills/service-itsm-teams-debug && 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-teams-debug" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/service-itsm-teams-debug into .opencode/skills/service-itsm-teams-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "service-itsm-teams-debug", 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.
Facts
- Skill name
service-itsm-teams-debug- GitHub stars
- 1.1k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 896 words
- Files
- 3 (incl. references)
- Skills in repo
- 251
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation.
- Works in 4 steps: Identify the problem and collect inputs → Route to the checklist → Run the checks → …
- First-time enablement (service-itsm-teams-configure / -itservice-configure / -itdesk-configure)
- SKILL.md covers Scope, Step 1 — Identify the problem…, Step 2 — Route to the checklist and Step 3 — Run the checks, plus 3 more sections
- Reaches cdn.scs.static.lightning.force.com and teams.cloud.microsoft
What it does
Service Itsm Teams Debug is an agent skill from forcedotcom/sf-skills. Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation. Use this for: 'IT Desk login not working in Teams', 'UEL/CCP user can't log in to IT Service', 'Teams feature not showing / not enabled', 'CI Hub / Service Catalog / My Assets tab not loading', 'Teams Agentforce agent not responding', 'Teams swarming not working', 'Teams SSO failing', or any request to troubleshoot a Teams ITSM setup. Routes the…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/configuration-checklists.md` and `references/report-generation.md`).
It sits in Backend & APIs, covering Authentication. It works with Microsoft Teams and Salesforce. 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
- First-time enablement (service-itsm-teams-configure / -itservice-configure / -itdesk-configure)
- Building the embedded agent from scratch (service-itsm-teams-employee-agent-configure)
Example prompts
- “IT Desk login not working in Teams”
- “UEL/CCP user can”
- “Teams feature not showing / not enabled”
- “/service-itsm-teams-debug”
Requirements
- Pre-approved tools (allowed-tools): Read, AskUserQuestion, mcp__headless-360__discover, mcp__headless-360__describe, mcp__headless-360__dispatch, mcp__headless-360__dispatch_readonly
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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:
ReadAskUserQuestionmcp__headless-360__discovermcp__headless-360__describemcp__headless-360__dispatchmcp__headless-360__dispatch_readonly
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
Hosts in commands or code, which the agent is likely to contact:
cdn.scs.static.lightning.force.comteams.cloud.microsoft
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 Debug loads about 2.3k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 251 tokens; SKILL.md has 896 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.
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). 896 words, ~2,276 tokens.
Download SKILL.mdSave it as
.claude/skills/service-itsm-teams-debug/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- service-itsm-teams-debug
- description
- Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation. Use this for: 'IT Desk login not working in Teams', 'UEL/CCP user can't log in to IT Service', 'Teams feature not showing / not enabled', 'CI Hub / Service Catalog / My Assets tab not loading', 'Teams Agentforce agent not responding', 'Teams swarming not working', 'Teams SSO failing', or any request to troubleshoot a Teams ITSM setup. Routes the problem to the right checklist (login, feature enablement, tab loading, Agentforce, swarming, SSO) and checks the exact CORS, External Client App, feature toggle, PSL, profile, auth-provider, named-credential, and messaging-channel settings each requires. DO NOT TRIGGER for first-time enablement (service-itsm-teams-configure / -itservice-configure / -itdesk-configure) or building the embedded agent from scratch (service-itsm-teams-employee-agent-configure).
- allowed-tools
- Read, AskUserQuestion, mcp__headless-360__discover, mcp__headless-360__describe, mcp__headless-360__dispatch, mcp__headless-360__dispatch_readonly
- metadata.version
- 1.0
- metadata.domains
- Service
- metadata.minApiVersion
- 62.0
- metadata.relatedSkills
- service-itsm-channels-coordinate, service-itsm-teams-configure, service-itsm-teams-employee-agent-configure, service-itsm-teams-itdesk-configure…
Troubleshoot Microsoft Teams for Employee Service (ITSM)
When someone reports a Microsoft Teams for Employee Service failure — can't log in, a tab won't load, the feature isn't showing, the Agentforce agent won't reply, swarming or SSO is broken — this skill connects to the org, runs the pass/fail checklist for that specific problem, and reports each setting's actual value plus the exact Setup path to fix any that are wrong. It replaces "check every setting by hand" with a targeted, verified diagnosis.
Every read dispatches through headless-360 (dispatch_readonly for queries, dispatch only
for the optional swarming-token clear). No org password is needed.
Scope
- In scope: Diagnosing an already-attempted Teams ITSM setup that is failing. Routing the reported symptom to the right checklist and checking the exact settings it requires (CORS, External Client App, feature toggles, PSLs, profile session settings, auth provider, named credentials, messaging channel, Agentforce agent).
- Out of scope: First-time enablement (use
service-itsm-teams-configure/-itservice-configure/-itdesk-configure), building the embedded agent from scratch (useservice-itsm-teams-employee-agent-configure), and non-Teams Salesforce debugging.
Read-only by default. Every check is a
dispatch_readonlyquery — running the full checklist changes nothing. The only state-changing action is the optional swarming OAuth-token clear at the very end, and only with explicit user confirmation.
Step 1 — Identify the problem and collect inputs
Ask the user for their problem description if not already given. Match it to a checklist using
the Feature Map in references/configuration-checklists.md.
Some problems need extra inputs — ask for them up front:
| Problem type | Extra input to collect |
|---|---|
| Generic "login" (no app named) | Ask which app — IT Desk or IT Service |
| IT Desk login | End-user's Salesforce username (the person who can't log in) |
| IT Service login | CCP or UEL user?, then that end-user's Salesforce username |
| Agentforce not replying | Employee Experience Site URL |
| Swarming | End-user's username; Azure AD Tenant ID (optional — enables the Azure app check) |
| SSO | Azure AD Tenant ID (optional); optionally which app + end-user username |
Do not run the agent-specific checks until you have the mandatory inputs for that checklist
(e.g. don't skip asking for the end-user username on a login issue — the per-user checks are
MANUAL_CHECK_REQUIRED without it).
Step 2 — Route to the checklist
Pick the checklist from the Feature Map, then run its checks in order from
references/configuration-checklists.md:
| Symptom | Checklist |
|---|---|
| IT Desk login | LOGIN_DESK |
| IT Service login — UEL user | LOGIN_SERVICE_UEL |
| IT Service login — CCP user | LOGIN_SERVICE_CCP |
| Generic login (app unknown) | LOGIN (then ask which app) |
| Feature not showing / not enabled | MSTEAMS_CORE |
| Tab won't load (CI Hub, Service Catalog, Employee Enablement, My Assets) | TAB_LOADING |
| Lightning app not embedding / blank tab | LIGHTNING_OUT |
| Agentforce agent not replying | AGENTFORCE |
| Swarming | SWARMING |
| Single Sign-On | SSO (+ the app-specific login checklist if an app is named) |
When an app is named for an SSO issue, run both the SSO checklist and the matching login
checklist (LOGIN_DESK / LOGIN_SERVICE_CCP / LOGIN_SERVICE_UEL) — skip duplicate checks.
Step 3 — Run the checks
Execute each check's query via dispatch_readonly (queries and API fields are spelled out in the
reference). Record for each check: a status and the configured value actually read from
the org.
| Status | Render as | Meaning |
|---|---|---|
OK | OK | Correctly configured |
MISCONFIGURED / MISSING / DISABLED / ERROR | FAIL | Needs fixing — include the exact Setup path from the reference |
MANUAL_CHECK_REQUIRED | MANUAL | Needs manual verification (or a missing optional input like Tenant ID/username) — never render this as FAIL |
Show full SKILL.md (352 more words)Show less
Step 4 — Report
Render a table with all four columns — #, Check, Status, Configured Value (never
omit the configured value), plus an Action Required note carrying the remediation for any
failed check. End with a one-line summary: N passed | N failed | N require manual verification.
- All passed: tell the user the Salesforce backend is correctly configured; if the problem persists, reload the Teams app (⋯ on the IT Desk/IT Service app → Reload app).
- Any failed: don't add the reload note — the per-check
Action Requiredsteps are the fix.
The full report-rendering rules, special-case notes, the example report layout, and the optional
swarming OAuth-token clear are in
references/report-generation.md.
Gotchas (verified)
| Issue | Detail |
|---|---|
The Teams ECA DeveloperName is ServiceCloudTeamsEca | The External Client App the login checks look for is ServiceCloudTeamsEca. (A per-org packaged instance may surface under a related name such as ServiceCloudMSTeamsEca; match on the ECA that backs the Teams login, and treat a missing app as "turn the feature off and on again.") |
| "Allow OAuth for employees" is Metadata-API-only for reading, and Setup-UI-only to change | Read via SOAP listMetadata(ProfileSessionSetting) → readMetadata on the fullName containing unified; field allowOauthForEmployees (true=enabled, false=disabled, absent=never configured). It is not on Profile describe and not REST/Tooling-queryable. To set it, use Setup → Profiles → (employee profile) → Session Settings. UEL users only. |
CORS check reads IsOauthCorsPolicyEnabled, allowed origins read CorsWhitelistEntry.UrlPattern | Both https://cdn.scs.static.lightning.force.com and https://teams.cloud.microsoft must be present. |
| Feature toggles are read via the FulfillerApp permissions Connect API | GET /connect/it-service/permissions/FulfillerApp returns the org/user feature flags; a FUNCTIONALITY_NOT_ENABLED error means the IServiceItsmTeamsFamily family is off at the org level. |
| Agentforce user-verification fields need SOAP v62+ | MessagingChannel.embeddedConfig (authMode, messagingAuthorizations.*) is silently omitted by SOAP v60 — use v62+. |
| Version prefix required | headless-360 dispatch/dispatch_readonly don't resolve API versions — always pass the full /services/data/vXX.0/... prefix. |
Related Skills
| Skill | When to use instead |
|---|---|
service-itsm-teams-configure | First-time enablement of the base Teams Go page toggle, Azure/Entra app, Named Credential, extension registration |
service-itsm-teams-itservice-configure | Completing the IT Service (employee) enablement checklist |
service-itsm-teams-itdesk-configure | Completing the IT Desk (fulfiller) enablement checklist + Swarming collaboration tool |
service-itsm-teams-employee-agent-configure | Building the embedded Agentforce agent from scratch so it replies in Teams |
service-itsm-channels-coordinate | Top-level menu across Teams, Slack, Swarming, Notifications, Portal |
© 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 2 other files (references) in skills/service-itsm-teams-debug of forcedotcom/sf-skills.
- SKILL.md
- references/configuration-checklists.md
- references/report-generation.md
Open the folder on GitHubat commit e5164d9
Compare with similar skills
Service Itsm Teams Debug 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 Teams Debug this skillforcedotcom/sf-skills | 1.1k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Teams Devmicrosoft/teams-sdk | 729 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sap Btp Build Work Zone Advancedsecondsky/sap-skills | 462 | — | ~3.3k | Automated safety check: Pass | GPL-3.0 | |
| Sf Connected AppsJaganpro/sf-skills | 424 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Salesforce Enterprise Rbacjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Sap Btp Build Work Zone Advanced
secondsky/sap-skills
Develops and administers SAP Build Work Zone, advanced edition digital workplace solutions.
Sf Connected Apps
Jaganpro/sf-skills
Salesforce Connected Apps and OAuth configuration with 120-point scoring.
Salesforce Enterprise Rbac
jeremylongshore/tons-of-skills-marketplace
Review and govern Salesforce enterprise access across profiles, permission sets and groups, sharing, field access, OAuth apps, SSO, and privileged roles.
Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
More from forcedotcom/sf-skills
All 251 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Service Itsm Teams Debug
What does Service Itsm Teams Debug do?
Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation. Service Itsm Teams Debug is an agent skill from forcedotcom/sf-skills. Debug and diagnose Microsoft Teams for Employee Service (ITSM) configuration failures — run a pass/fail validation checklist against the org and report exact remediation.
When should I use Service Itsm Teams Debug?
Service Itsm Teams Debug fits situations like: first-time enablement (service-itsm-teams-configure / -itservice-configure / -itdesk-configure); building the embedded agent from scratch (service-itsm-teams-employee-agent-configure).
How do I install Service Itsm Teams Debug in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill service-itsm-teams-debug -a claude-code`. Or copy the skill folder (skills/service-itsm-teams-debug in forcedotcom/sf-skills) into .claude/skills/service-itsm-teams-debug in your project. Claude Code loads it when a task matches its description.
How do I install Service Itsm Teams Debug in Codex?
Run `npx skills add forcedotcom/sf-skills --skill service-itsm-teams-debug -a codex`. Or copy the skill folder (skills/service-itsm-teams-debug in forcedotcom/sf-skills) into .agents/skills/service-itsm-teams-debug in your project. Codex loads it when a task matches its description.
Can I use Service Itsm Teams Debug 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-debug -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-debug, .gemini/skills/service-itsm-teams-debug, .github/skills/service-itsm-teams-debug and .opencode/skills/service-itsm-teams-debug in your project.
What does Service Itsm Teams Debug need to run?
SKILL.md names no scripts, command-line tools or credentials: Service Itsm Teams Debug is instructions for the agent only. Its frontmatter pre-approves these tools: Read, AskUserQuestion, mcp__headless-360__discover, mcp__headless-360__describe, mcp__headless-360__dispatch, mcp__headless-360__dispatch_readonly.
Does Service Itsm Teams Debug access the network?
SKILL.md names 2 domains. In commands or code: cdn.scs.static.lightning.force.com and teams.cloud.microsoft; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Service Itsm Teams Debug 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 Debug use?
Service Itsm Teams Debug 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 Debug use?
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.8k tokens, read only when the agent opens those files.
What are the alternatives to Service Itsm Teams Debug?
Skills that share tags, products or a category with Service Itsm Teams Debug: Teams Dev (microsoft/teams-sdk, 729 stars), Sap Btp Build Work Zone Advanced (secondsky/sap-skills, 462 stars), Sf Connected Apps (Jaganpro/sf-skills, 424 stars) and Salesforce Enterprise Rbac (jeremylongshore/tons-of-skills-marketplace, 2.8k 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 Debug?
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.