Generated banner for Teams App Developer
Generated logo for Teams App Developer

Teams App Developer

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Tool integration
  • Software development
  • MIT
  • Medium risk

From the author

Builds, tests, and deploys Microsoft 365 apps and agents for Teams and Copilot. Includes sub-skills for project creation, local testing, cloud deployment, troubleshooting, and Slack-to-Teams migration. USE FOR: Teams agent, bot, tab, message extension, Declarative Agents, Custom Engine Agents, local testing, Agents Playground, Azure resource provision, remote deployment, Slack to Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion. DO NOT USE FOR: general web development, non-bot/non-Teams projects.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The teams-app-developer skill provides a structured framework for managing the lifecycle of Microsoft 365 agents and Teams applications. It leverages the ATK CLI to handle project scaffolding, local testing via the Agents Playground, cloud provisioning on Azure, and troubleshooting. The skill includes specialized guidance for migrating Slack bots to Teams, including converting Block Kit UI to Adaptive Cards, and provides access to an extensive library of micro-expert documentation for cross-platform development.

What it does

  • Scaffolds new Microsoft 365 agents and Teams applications from templates.
  • Facilitates local testing using the Agents Playground or Teams-specific environments.
  • Automates Azure resource provisioning and cloud deployment workflows.
  • Provides diagnostic procedures for common authentication and configuration errors.
  • Supports migration of Slack bots to the Teams platform.
  • Manages project configuration and environment variables for ATK-based projects.

When to use it

  • When starting a new Teams app, bot, or Declarative Agent project.
  • When you need to test an agent locally before deploying to the cloud.
  • When migrating existing Slack bots to the Microsoft Teams ecosystem.
  • When troubleshooting deployment or authentication issues in a Teams project.
  • When you need to provision Azure infrastructure for a Teams application.

Advantages

  • Streamlines the development lifecycle with standardized CLI commands.
  • Reduces development time by offering a local testing playground.
  • Provides expert-level guidance for complex cross-platform migrations.
  • Ensures consistent configuration management across development environments.
  • Includes robust error-handling protocols for common platform-specific pitfalls.

Usage examples

“Create a new Teams bot project using the default template.”
The agent will initialize a new project folder, configure the necessary YAML files, and guide you through the initial setup using the ATK CLI.
“How do I migrate my Slack bot to Microsoft Teams?”
The agent will initiate the slack-to-teams workflow, providing access to cross-platform bridging experts and guidance on converting UI components.
“My Teams bot is returning a 401 error, how do I fix it?”
The agent will trigger the troubleshooting workflow, checking your environment variables, tunnel status, and authentication configuration.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/teams-app-developer/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip teams-app-developer.zip -d .agents/skills

Documentation by Microsoft

Microsoft 365 Agents Toolkit Skill

Build Microsoft 365 agents and Teams apps using the ATK CLI.

AI Behavior Guidelines

  1. Testing Strategy: Recommend Agents Playground first (faster, no M365 needed). Use Teams workflow only if user explicitly requests it.

  2. Environment Variables: NEVER hardcode secrets or make up placeholder values. Always ask users for real values.

  3. Error Handling: Read error messages carefully. Check env/.env.local, .localConfigs, and atk auth list. Common pitfalls:

    • AADSTS7000229 → aadApp/create missing generateServicePrincipal: true in YAML — add it and re-provision

    • Missing TENANT_ID in .localConfigs → SDK uses wrong token authority → 401 from Bot Connector

    • 401 persists after auth fix → devtunnel URL may be blacklisted — create a fresh tunnel

    • See troubleshoot/troubleshoot.md for full diagnostic steps

  4. Long-Running Commands — WAIT for completion:

    • atk new, atk provision, atk deploy can take several minutes

    • Always wait for completion before running the next step (timeout 120000ms+)

  5. Local Service Startup — Hangs terminal (expected):

    • npm run dev, npm start, python app.py, devtunnel host, etc. will hang — the process keeps running indefinitely

    • ALWAYS run as a background process (isBackground=true) — NEVER use isBackground=false for these commands

    • Do NOT wait for it to "finish" — verify startup by checking output for "listening on port" or tunnel URL

    • If errors appear, read logs, diagnose, fix, restart

    • Use a NEW terminal to launch Agents Playground or open Teams sideloading URL

  6. Monitor App Logs: Periodically check background terminal output for runtime errors. If the app crashes, read the error, fix the root cause, and restart.

  7. Telemetry Tagging: Before running any atk CLI commands, set the session environment variable so all CLI invocations are tagged as skill-initiated:

    export ATK_CLI_SKILL=true

    Run this once at the start of the session. All subsequent atk commands in the same terminal will inherit it.

ATK CLI Setup

atk --version  # Must be > 1.1.5-beta

If ATK is not found or version is too old:

npm i -g @microsoft/m365agentstoolkit-cli@beta

CLI Global Options

OptionMeaningRecommendation
-iInteractive modeAlways use -i false in automation to avoid hanging
-fProject folderDefault to be current directory, used when specifying a custom folder. When scaffolding a new project, this is the parent folder where the project folder will be created under.
-hCommand helpUse atk <command> -h for quick syntax checks

Sub-Skills

Sub-SkillWhen to UseReference
create-projectScaffold new project from template, choose template, atk newcreate-project/create-project.md
test-playgroundTest locally with Agents Playground, agentsplayground, quick testingtest-playground/test-playground.md
test-teamsRun on Teams, devtunnel, sideload, Teams testing, test in Copilottest-teams/test-teams.md
provision-deployProvision Azure resources, deploy to cloud, atk provision, atk deployprovision-deploy/provision-deploy.md
troubleshootFix errors, 401, port conflicts, YAML errors, stale botstroubleshoot/troubleshoot.md
slack-to-teamsMigrate Slack bot to Teams, cross-platform bridging, Block Kit to Adaptive Cardsslack-to-teams/SKILL.md

MANDATORY: Before executing any workflow, read the corresponding sub-skill document.

Shared References

  • manifest-and-yaml.md — Project files, YAML config, env vars, .localConfigs flow

  • commands.md — ATK CLI commands: package, validate, share, collaborate

  • templates.md — Complete template catalog with language support

  • experts/ — 100+ micro-expert files: Teams SDK, Slack SDK, cross-platform bridging, deploy, AI models, security, language conversion

  • docs/ — Platform comparison guides: UI, messaging, identity, infrastructure, feature gaps

Workflow Chains

Match user intent to the smallest valid workflow.

User IntentWorkflow (read in order)
Build new app from scratchcreate-project → test-playground
Test existing project locallytest-playground (recommended) or test-teams
Deploy to Azureprovision-deploy
Fix broken bottroubleshoot → re-test
Migrate Slack bot to Teamsslack-to-teams

MANDATORY: Before executing any slack-to-teams workflow, read slack-to-teams/SKILL.md first. The sub-skill contains a routed expert system with 100+ micro-expert files for cross-platform bot development.

ATK Project Context Resolution

Resolve config values only when missing. If a value is already known in the session, reuse it.

Step 1: Detect ATK Project

If m365agentstoolkit*.yml exists in the current folder, treat it as an ATK project and parse configuration.

Step 2: Resolve Common Configuration

Resolve variables referenced in m365agentstoolkit*.yml. Common variables: AZURE_OPENAI_API_KEY AZURE_OPENAI_ENDPOINT AZURE_OPENAI_DEPLOYMENT_NAME

Step 3: Collect Missing Values

If required values are missing, ask the user for only the missing ones.

Refer to manifest-and-yaml.md for full config-file details.

Files

experts/slack/bolt-python.md

bolt-python

purpose

Slack Bolt for Python SDK patterns — translating TypeScript Bolt concepts to Python equivalents using slack_bolt.

rules

  1. Import the sync App from slack_bolt or the async App from slack_bolt.async_app. Use AsyncApp for FastAPI or any async framework; use sync App for Flask or Django. slack.dev/bolt-python/concepts

  2. Initialize the App with token and signing_secret, or let Bolt auto-load from SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET environment variables. Unlike TS Bolt, Python Bolt reads env vars automatically when no args are passed. slack.dev/bolt-python/tutorial/getting-started

  3. Register listeners using decorator syntax: @app.message("pattern"), @app.command("/cmd"), @app.action("action_id"), @app.shortcut("callback_id"), @app.view("callback_id"), @app.event("event_type"), @app.options("action_id"). This replaces the TS method-call pattern. slack.dev/bolt-python/concepts

  4. Python Bolt uses argument injection — handlers declare only the parameters they need (ack, say, respond, client, body, event, command, action, shortcut, view, context, logger). Bolt inspects the function signature and injects matching values. This replaces the TS destructured context object. slack.dev/bolt-python/concepts/listener-functions

  5. Use ack() the same way as TS. For view submissions, pass response_action="errors" and errors={"block_id": "message"} as keyword arguments instead of the TS object form ack({ response_action: 'errors', errors }). slack.dev/bolt-python/concepts/acknowledge

  6. Use client (a WebClient instance from slack_sdk) for API calls. Method names use snake_case: client.chat_postMessage(), client.views_open(), client.users_info(), client.files_upload_v2(). This maps directly from the TS camelCase equivalents. slack.dev/python-slack-sdk/web

  7. Pass keyword arguments to API methods, not request configurators. TS uses client.chat.postMessage({ channel, text }). Python uses client.chat_postMessage(channel=channel, text=text). No nested method namespaces — methods are flat on the client. slack.dev/python-slack-sdk/web

  8. For Socket Mode, use SocketModeHandler from slack_bolt.adapter.socket_mode. Pass the App and app_token. Call handler.start() to block. This replaces the TS socketMode: true constructor option. slack.dev/bolt-python/concepts/socket-mode

  9. For Flask, wrap the App with SlackRequestHandler from slack_bolt.adapter.flask. For FastAPI, use AsyncSlackRequestHandler from slack_bolt.adapter.fastapi with AsyncApp. Django, Bottle, Sanic, Tornado, Starlette, and ASGI adapters also exist. slack.dev/bolt-python/concepts/adapters

  10. Use regex patterns with re.compile(): @app.message(re.compile(r"^hello")). Same capability as TS RegExp patterns but uses Python's re module. slack.dev/bolt-python/concepts/message-listening

  11. Access event data through the injected event or body dict — these are plain Python dicts, not typed objects. Use event["user"], body["trigger_id"], view["state"]["values"]. No TypeScript interfaces — rely on Slack API documentation for field shapes. api.slack.com/events

  12. For middleware, use @app.middleware decorator or pass middleware=[fn] to individual listeners. Middleware functions receive injected args including next (or next_ to avoid shadowing the builtin). Call next() to continue the chain. slack.dev/bolt-python/concepts/middleware

  13. Both sync and async Apps support the same listener types. Async handlers must use async def and await all utility calls (await ack(), await say(), await client.chat_postMessage()). Sync handlers use regular def and direct calls. slack.dev/bolt-python/concepts/async

patterns

Basic app with message, command, and action handlers
import os
import re
from slack_bolt import App

app = App(
    token=os.environ["SLACK_BOT_TOKEN"],
    signing_secret=os.environ["SLACK_SIGNING_SECRET"],
)

@app.message(re.compile(r"^hello"))
def handle_hello(message, say):
    say(f"Hey <@{message['user']}>!")

@app.command("/status")
def handle_status(ack, command, respond):
    ack("Checking status...")
    status = get_system_status()
    respond(response_type="in_channel", text=f"Status: {status}")

@app.action("approve_button")
def handle_approve(ack, body, client):
    ack()
    client.chat_update(
        channel=body["channel"]["id"],
        ts=body["message"]["ts"],
        text=f"Approved by <@{body['user']['id']}>",
    )

if __name__ == "__main__":
    app.start(port=3000)
Async app with FastAPI
import os
from slack_bolt.async_app import AsyncApp
from slack_bolt.adapter.fastapi import AsyncSlackRequestHandler
from fastapi import FastAPI, Request

app = AsyncApp(
    token=os.environ["SLACK_BOT_TOKEN"],
    signing_secret=os.environ["SLACK_SIGNING_SECRET"],
)

@app.command("/ticket")
async def handle_ticket(ack, command, client):
    await ack()
    await client.views_open(
        trigger_id=command["trigger_id"],
        view={
            "type": "modal",
            "callback_id": "ticket_modal",
            "title": {"type": "plain_text", "text": "Create Ticket"},
            "submit": {"type": "plain_text", "text": "Create"},
            "blocks": [
                {
                    "type": "input",
                    "block_id": "title_block",
                    "label": {"type": "plain_text", "text": "Title"},
                    "element": {
                        "type": "plain_text_input",
                        "action_id": "title_input",
                    },
                }
            ],
        },
    )

@app.view("ticket_modal")
async def handle_submission(ack, view, client):
    title = view["state"]["values"]["title_block"]["title_input"]["value"]
    if len(title) < 3:
        await ack(response_action="errors", errors={"title_block": "Too short"})
        return
    await ack()

fastapi_app = FastAPI()
handler = AsyncSlackRequestHandler(app)

@fastapi_app.post("/slack/events")
async def slack_events(req: Request):
    return await handler.handle(req)
Socket Mode
import os
from slack_bolt import App
from slack_bolt.adapter.socket_mode import SocketModeHandler

app = App(token=os.environ["SLACK_BOT_TOKEN"])

@app.event("app_mention")
def handle_mention(event, say):
    say(f"You mentioned me! <@{event['user']}>")

if __name__ == "__main__":
    handler = SocketModeHandler(app, os.environ["SLACK_APP_TOKEN"])
    handler.start()

pitfalls

  • Using next instead of next_ in middleware: next shadows Python's builtin. Use next_ as the parameter name to avoid confusion. Both work for injection.

  • Forgetting await in async handlers: Unlike sync App where say("text") works directly, async App requires await say("text"). Missing await silently drops the call.

  • Dict access vs typed objects: Python payloads are plain dicts. event["user"] not event.user. KeyError on missing fields — use .get("key") for optional fields.

  • Method name casing: Python SDK uses snake_case for API methods (chat_postMessage not chatPostMessage, views_open not viewsOpen). The TS camelCase habit causes AttributeError.

  • Flask vs FastAPI mismatch: Using sync App with FastAPI's async handler or AsyncApp with Flask causes runtime errors. Match sync/async consistently.

references

instructions

This expert covers Slack Bolt for Python — the Python equivalent of @slack/bolt. Use it when building Slack apps in Python (Tier 2 or standalone), translating TypeScript Bolt patterns to Python, or setting up Python web framework adapters (Flask, FastAPI, Django). All TS Bolt experts (runtime.bolt-foundations-ts.md, runtime.ack-rules-ts.md, etc.) provide the architectural patterns — this expert provides the Python API mappings.

Pair with: runtime.bolt-foundations-ts.md for conceptual architecture (translate to Python). bolt-oauth-distribution-ts.md for OAuth concepts (translate to Python). bridge/python-cross-platform.md for unified Python server with both Slack and Teams.

research

Deep Research prompt:

"Write a micro expert mapping Slack Bolt TypeScript patterns to Python equivalents using slack_bolt. Cover App initialization (sync vs async), decorator-based listener registration (@app.message, @app.command, @app.action, @app.shortcut, @app.view, @app.event), argument injection (ack, say, respond, client, body, context, logger), WebClient snake_case methods (chat_postMessage, views_open), Socket Mode setup (SocketModeHandler), web framework adapters (Flask SlackRequestHandler, FastAPI AsyncSlackRequestHandler), middleware patterns, regex matching with re.compile(), and key differences from TS (dict access, no types, sync/async split). Source from bolt-python source code and slack.dev docs."

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an API key, Needs Python, Needs Node.js

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network
  • Downloads piped into a shell

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/plugins/microsoft-365-agents-toolkit/skills/teams-app-developer · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download teams-app-developer.zip