Official agent skill

Teams Dev

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.

OfficialMITAuto-check passedBackend & APIs

Install Teams Dev

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a claude-code

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

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev --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/microsoft/teams-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .claude/skills/teams-dev && 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/

Paste into Claude Code

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .claude/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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

$skill-installer install https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev

Type 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.

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/teams-sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .agents/skills/teams-dev && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .agents/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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.

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/teams-sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .cursor/skills/teams-dev && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .cursor/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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

$ gemini skills install https://github.com/microsoft/teams-sdk.git --path plugins/teams-sdk/skills/teams-dev

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/teams-sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .gemini/skills/teams-dev && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .gemini/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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.

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev

Installs 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).

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/teams-sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .github/skills/teams-dev && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .github/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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.

skills CLI

$ npx skills add microsoft/teams-sdk --skill teams-dev -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microsoft/teams-sdk teams-dev --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/teams-sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/teams-sdk/skills/teams-dev .opencode/skills/teams-dev && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "teams-dev" agent skill from https://github.com/microsoft/teams-sdk/tree/main/plugins/teams-sdk/skills/teams-dev into .opencode/skills/teams-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teams-dev", 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: teams-dev
GitHub stars: 728
Token cost: ~1.2k tokens
SKILL.md length: 447 words
Files: 6 (incl. references)
Skills in repo: 1
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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.

The user mentions Microsoft Teams in a development context — whether theyre building
SKILL.md covers Workflow Routing, Common Operations and Resources
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Just asking questions

What it does

Teams Dev is an agent skill from microsoft/teams-sdk, published by the product's own GitHub organization. Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, and general Teams platform queries. If the word "Teams" appears, err on the side of invoking this skill.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/guide-create-bot-app.md`, `references/guide-create-bot-infra.md` and `references/guide-integrate-existing-server.md`).

It sits in Backend & APIs, covering Authentication. It works with Microsoft Teams and TypeScript. The repository describes itself as: SDK focused on building AI based applications and extensions for Microsoft Teams and other Bot Framework channels. The licence is MIT.

When your agent uses it

The user mentions Microsoft Teams in a development context — whether theyre building
Just asking questions

Example prompts

“/teams-dev”

Requirements

Python 3

What it can do on your machine

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

Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- microsoft.github.io
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

Teams Dev loads about 1.2k tokens when it runs, and up to ~7.8k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 447 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~104
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~7.8k

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 microsoft/teams-sdk at commit 3da478f, republished under its MIT licence (© microsoft). 447 words, ~1,202 tokens.

Download SKILL.mdSave it as .claude/skills/teams-dev/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: teams-dev
description: Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, and general Teams platform queries. If the word "Teams" appears, err on the side of invoking this skill.
teams_cli_version: 3.0.*

Teams Bot Development & Infrastructure

This skill helps you create and manage Microsoft Teams bots using the Teams Developer CLI. Covers both bot application development (creating bot code) and infrastructure management (bot registration, SSO, credentials).

IMPORTANT: Use information and guidance provided within this skill and its reference guides. You may also use external public documentation only when it is explicitly linked from this skill or those guides. Do NOT perform arbitrary web searches or rely on unlisted external sources.

Workflow Routing

Based on the user's request, route to the appropriate guide or handle directly:

Complex Workflows (Use References)

Creating bot application code:

Read and follow the Bot Application Development guide
This covers: Scaffolding a new bot project with teams project new (TypeScript/C#/Python, templates, connecting to infrastructure)

Integrating Teams into an existing server:

Read and follow the Integrate Existing Server guide
This covers: Adding Teams bot functionality to an existing server using built-in adapters (ExpressAdapter for TypeScript, FastAPIAdapter for Python) or a custom adapter for any framework

Setting up bot infrastructure (Teams-managed bot & credentials):

Read and follow the Bot Infrastructure Setup guide
This covers: Prerequisites → Create Teams-managed bot → Save credentials → Verify

Setting up SSO authentication:

Read and follow the SSO Setup guide
This covers: Bot migration → AAD app configuration → OAuth connection → Manifest update → Verification
Prerequisites: Existing bot (teamsAppId, botId), az CLI authenticated

Troubleshooting errors:

Read the Troubleshooting guide
Covers: Sideloading issues, auth errors, SSO problems, migration issues

Simple Operations (Handle Directly)

For simple queries and updates, handle directly using the commands below:

List all apps:

bash

teams app list

View app details:

bash

teams app get <teamsAppId> --json

Check authentication status:

bash

teams status

Update CLI to latest version:

bash

teams self-update

Common Operations

Show full SKILL.md (181 more words)Show less

Update Bot Endpoint

Use case: Endpoint URL changed (new ngrok/devtunnels session)

Command:

bash

teams app update <teamsAppId> --endpoint "https://new-endpoint-url/api/messages"

When to use:

Ngrok URL changed (new session)
Devtunnels URL changed
Switching between different local development tunnels

Note: If the endpoint domain changed (not just the path), the CLI automatically updates validDomains in the manifest. This requires the user to reinstall the app in Teams for the change to take effect.

Update Teams Developer CLI

Use case: Update the Teams Developer CLI to the latest version (recommended to stay current with new features and bug fixes)

Command:

bash

teams self-update

When to use:

Periodically update to get latest features
After bug reports or known issues
When new CLI features are announced

Expected: CLI downloads and installs the latest version

View App Details

Command:

bash

teams app get <teamsAppId> --json

Use case: Check current bot configuration, verify settings

List All Apps

Command:

bash

teams app list

Use case: See all Teams apps you've created

Resources

Teams SDK Documentation (llms.txt — optimized for LLM consumption):

TypeScript: https://microsoft.github.io/teams-sdk/llms_docs/llms_typescript.txt
Python: https://microsoft.github.io/teams-sdk/llms_docs/llms_python.txt
C#: https://microsoft.github.io/teams-sdk/llms_docs/llms_csharp.txt
Full TypeScript docs: https://microsoft.github.io/teams-sdk/llms_docs/llms_typescript_full.txt
Full Python docs: https://microsoft.github.io/teams-sdk/llms_docs/llms_python_full.txt
Full C# docs: https://microsoft.github.io/teams-sdk/llms_docs/llms_csharp_full.txt

Development Tunnels: See the Bot Infrastructure Setup guide for devtunnel setup instructions.

Files

SKILL.md and 5 other files (references) in plugins/teams-sdk/skills/teams-dev of microsoft/teams-sdk.

SKILL.md
references/guide-create-bot-app.md
references/guide-create-bot-infra.md
references/guide-integrate-existing-server.md
references/guide-setup-sso.md
references/troubleshooting.md

Open the folder on GitHubat commit 3da478f

Compare with similar skills

Teams Dev 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.

Teams Dev compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Teams Dev this skillmicrosoft/teams-sdk	728	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Better Auth Best Practiceslatitude-dev/latitude-llm	4.7k	7 repos	~1.6k	Automated safety check: Pass	MIT	yesterday
Gemini Live API Devgoogle-gemini/gemini-skills	4.3k	—	~4.6k	Automated safety check: Pass	Apache-2.0	today
Slackclishaharia-lab/slackcli	227	—	~1.6k	Automated safety check: Pass	MIT	3 days ago
Cdesktopcdesktop-ai/cdesktop	157	—	~697	Automated safety check: Pass	Apache-2.0	4 mo ago
Sasjs Adaptersasjs/core	132	—	~2.6k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
4.7k GitHub starsUsed in 7 repos~1.6k tokens
Backend & APIsAuto-check passed
Gemini Live API Dev
google-gemini/gemini-skills
Official
A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.
4.3k GitHub stars~4.6k tokensUpdated today
Backend & APIsAuto-check passed
Slackcli
shaharia-lab/slackcli
Read, send, search, and manage Slack workspaces with the slackcli binary.
227 GitHub stars~1.6k tokensUpdated 3 days ago
Backend & APIsAuto-check passed
Cdesktop
cdesktop-ai/cdesktop
Operate the cdesktop coding-session environment — agent teams, session management, file conventions.
157 GitHub stars~697 tokensUpdated 4 mo ago
Backend & APIsAuto-check passed
Sasjs Adapter
sasjs/core
Frontend/Node integration with SAS backends using @sasjs/adapter - configuring the SASjs class, the exact request() inputs and response shape, authentication, file upload, and session management.
132 GitHub stars~2.6k tokensUpdated 2 days ago
Backend & APIsAuto-check passed
NestJS Expert
Jeffallan/claude-skills
Scaffolds NestJS modules, controllers, services, DTOs and guards for TypeScript backends, with validation, JWT and Passport auth, Swagger docs and unit and E2E tests.
12k GitHub stars~2k tokensUpdated 4 days ago
Backend & APIsAuto-check passed

Works with

Questions about Teams Dev

What does Teams Dev do?

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. Teams Dev is an agent skill from microsoft/teams-sdk, published by the product's own GitHub organization. Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions.

When should I use Teams Dev?

Teams Dev fits situations like: the user mentions Microsoft Teams in a development context — whether theyre building; just asking questions.

How do I install Teams Dev in Claude Code?

Run `npx skills add microsoft/teams-sdk --skill teams-dev -a claude-code`. Or copy the skill folder (plugins/teams-sdk/skills/teams-dev in microsoft/teams-sdk) into .claude/skills/teams-dev in your project. Claude Code loads it when a task matches its description.

How do I install Teams Dev in Codex?

Run `npx skills add microsoft/teams-sdk --skill teams-dev -a codex`. Or copy the skill folder (plugins/teams-sdk/skills/teams-dev in microsoft/teams-sdk) into .agents/skills/teams-dev in your project. Codex loads it when a task matches its description.

Can I use Teams Dev 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 microsoft/teams-sdk --skill teams-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/teams-dev, .gemini/skills/teams-dev, .github/skills/teams-dev and .opencode/skills/teams-dev in your project.

What does Teams Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Teams Dev is instructions for the agent only. Our summary lists: Python 3.

Does Teams Dev access the network?

SKILL.md names 1 domain. As links in the text: microsoft.github.io. This is read from the text; nothing was executed.

Is Teams Dev 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 Teams Dev use?

Teams Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Teams Dev use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 6.6k tokens, read only when the agent opens those files.

What are the alternatives to Teams Dev?

Skills that share tags, products or a category with Teams Dev: Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars), Gemini Live API Dev (google-gemini/gemini-skills, 4.3k stars), Slackcli (shaharia-lab/slackcli, 227 stars) and Cdesktop (cdesktop-ai/cdesktop, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Teams Dev?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/teams-sdk, which has 728 GitHub stars. The repository was last updated on October 6, 2026.

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

Install Teams Dev

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Teams Bot Development & Infrastructure

Workflow Routing

Complex Workflows (Use References)

Simple Operations (Handle Directly)

Common Operations

Update Bot Endpoint

Update Teams Developer CLI

View App Details

List All Apps

Resources

Files

Compare with similar skills

Similar skills

Better Auth Best Practices

Gemini Live API Dev

Slackcli

Cdesktop

Sasjs Adapter

NestJS Expert

Related

Questions about Teams Dev