teams-dev
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.
Works with
--- 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. license: MIT --- # 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](references/guide-create-bot-app.md)** - 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](references/guide-integrate-existing-server.md)** - 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](references/guide-create-bot-infra.md)** - This covers: Prerequisites → Create Teams-managed bot → Save credentials → Verify **Setting up SSO authentication:** - Read and follow the **[SSO Setup guide](references/guide-setup-sso.md)** - 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](references/troubleshooting.md)** - 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 ### 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](references/guide-create-bot-infra.md) for devtunnel setup instructions.
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

