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/teams/ui.adaptive-cards-ts.md

ui.adaptive-cards-ts

purpose

Adaptive Cards construction, sending as attachments, handling Action.Submit via card.action handlers, and Teams-specific constraints.

rules

  1. Always set "type": "AdaptiveCard" and "$schema": "http://adaptivecards.io/schemas/adaptive-card.json" at the card root; Teams requires "version": "1.5" or lower (1.6+ features are silently ignored). adaptivecards.io/designer

  2. Wrap every card in a CardFactory.adaptiveCard(cardJson) attachment -- never send raw JSON as message text. The attachment contentType is "application/vnd.microsoft.card.adaptive". learn.microsoft.com -- Cards reference

  3. Register card action handlers with app.adaptiveCards.actionSubmit(actionVerb, handler) where actionVerb matches the data.verb (or data.action) string you embed in the card's Action.Submit. The handler receives (ctx, state, data) where data is the merged activity.value object. github.com/microsoft/teams-ai

  4. Every Action.Submit must include a data object with a routing identifier (e.g., { "verb": "approve", ...inputValues }). Without it, Teams merges only input field values into activity.value and there is no way to distinguish which button was pressed.

  5. Input element id values become keys in activity.value. For example, Input.Text with "id": "comment" yields activity.value.comment. Keep IDs short and unique within a card.

  6. To update an existing message (e.g., replacing a card after action), return an updated card from the handler or call await ctx.updateActivity({ ...activity, attachments: [newCard] }). To send a new message instead, call await ctx.sendActivity(MessageFactory.attachment(newCard)).

  7. Teams Adaptive Cards do NOT support Action.Http, Action.ToggleVisibility (partial -- works for simple show/hide but not nested), backgroundImage on mobile, Media element playback, or hostConfig overrides. Always test on desktop + mobile. learn.microsoft.com -- Cards reference

  8. Card payload size must be under 28 KB (after JSON serialization). Larger cards are rejected silently. learn.microsoft.com -- Card size limit

  9. For Action.Execute (Universal Actions), the handler is app.adaptiveCards.actionExecute(verb, handler) and the return must be an Adaptive Card (used for automatic card refresh / user-specific views). Prefer Action.Submit for standard form flows; use Action.Execute only when you need per-user card refresh. learn.microsoft.com -- Universal Actions

  10. Always validate activity.value server-side -- clients can tamper with the JSON payload. Use a schema validator (e.g., zod) before trusting input data.

patterns

Confirm / Cancel card with action routing
import { App, TurnState } from "@microsoft/teams-ai";
import { CardFactory, MessageFactory } from "botbuilder";

// -- Card JSON ---------------------------------------------------------------
const confirmCard = {
  type: "AdaptiveCard",
  $schema: "http://adaptivecards.io/schemas/adaptive-card.json",
  version: "1.5",
  body: [
    {
      type: "TextBlock",
      text: "Delete this item?",
      weight: "Bolder",
      size: "Medium",
    },
    {
      type: "TextBlock",
      text: "This action cannot be undone.",
      wrap: true,
      isSubtle: true,
    },
  ],
  actions: [
    {
      type: "Action.Submit",
      title: "Confirm",
      style: "destructive",
      data: { verb: "deleteConfirm", itemId: "abc-123" },
    },
    {
      type: "Action.Submit",
      title: "Cancel",
      data: { verb: "deleteCancel", itemId: "abc-123" },
    },
  ],
};

// -- Handlers ----------------------------------------------------------------
export function registerConfirmHandlers(app: App<TurnState>): void {
  app.adaptiveCards.actionSubmit("deleteConfirm", async (ctx, _state, data) => {
    const itemId = (data as Record<string, string>).itemId;
    // ... perform deletion logic ...
    // Replace the card with a confirmation message
    const doneCard = CardFactory.adaptiveCard({
      type: "AdaptiveCard",
      version: "1.5",
      body: [{ type: "TextBlock", text: `Item ${itemId} deleted.` }],
    });
    await ctx.updateActivity({
      type: "message",
      id: ctx.activity.replyToId,
      attachments: [doneCard],
    });
    return undefined;
  });

  app.adaptiveCards.actionSubmit("deleteCancel", async (ctx) => {
    const cancelCard = CardFactory.adaptiveCard({
      type: "AdaptiveCard",
      version: "1.5",
      body: [{ type: "TextBlock", text: "Deletion cancelled." }],
    });
    await ctx.updateActivity({
      type: "message",
      id: ctx.activity.replyToId,
      attachments: [cancelCard],
    });
    return undefined;
  });
}
Form submission with input extraction
import { App, TurnState } from "@microsoft/teams-ai";
import { CardFactory, MessageFactory } from "botbuilder";

const feedbackFormCard = {
  type: "AdaptiveCard",
  $schema: "http://adaptivecards.io/schemas/adaptive-card.json",
  version: "1.5",
  body: [
    { type: "TextBlock", text: "Submit Feedback", weight: "Bolder", size: "Large" },
    {
      type: "Input.Text",
      id: "userName",
      label: "Your name",
      isRequired: true,
      errorMessage: "Name is required",
    },
    {
      type: "Input.ChoiceSet",
      id: "rating",
      label: "Rating",
      style: "compact",
      value: "3",
      choices: [
        { title: "1 - Poor", value: "1" },
        { title: "2 - Fair", value: "2" },
        { title: "3 - Good", value: "3" },
        { title: "4 - Great", value: "4" },
        { title: "5 - Excellent", value: "5" },
      ],
    },
    {
      type: "Input.Text",
      id: "comments",
      label: "Comments",
      isMultiline: true,
      placeholder: "Tell us more...",
    },
    {
      type: "Input.Toggle",
      id: "followUp",
      title: "Contact me for follow-up",
      value: "false",
      valueOn: "true",
      valueOff: "false",
    },
  ],
  actions: [
    {
      type: "Action.Submit",
      title: "Submit",
      data: { verb: "submitFeedback" },
    },
  ],
};

interface FeedbackData {
  verb: string;
  userName: string;
  rating: string;
  comments?: string;
  followUp: string;
}

export function registerFeedbackHandlers(app: App<TurnState>): void {
  app.adaptiveCards.actionSubmit("submitFeedback", async (ctx, _state, data) => {
    const fd = data as FeedbackData;
    // Input values are merged into activity.value alongside the data object
    const msg = `Thanks ${fd.userName}! Rating: ${fd.rating}/5.`;
    await ctx.sendActivity(MessageFactory.text(msg));
    return undefined;
  });
}

// -- Sending the card --------------------------------------------------------
// Inside any handler or proactive flow:
// await ctx.sendActivity(MessageFactory.attachment(
//   CardFactory.adaptiveCard(feedbackFormCard)
// ));
Dynamic choices via Action.Execute refresh
import { App, TurnState } from "@microsoft/teams-ai";
import { CardFactory } from "botbuilder";

// Card with Action.Execute for per-user refresh (Universal Actions)
function buildTicketCard(tickets: { id: string; title: string }[]): object {
  return {
    type: "AdaptiveCard",
    version: "1.4",
    refresh: {
      action: {
        type: "Action.Execute",
        title: "Refresh",
        verb: "refreshTickets",
      },
      userIds: [], // empty = refresh for all users
    },
    body: [
      { type: "TextBlock", text: "Open Tickets", weight: "Bolder" },
      {
        type: "Input.ChoiceSet",
        id: "selectedTicket",
        label: "Pick a ticket",
        choices: tickets.map((t) => ({ title: t.title, value: t.id })),
      },
    ],
    actions: [
      {
        type: "Action.Execute",
        title: "Claim",
        verb: "claimTicket",
        data: {},
      },
    ],
  };
}

export function registerTicketHandlers(app: App<TurnState>): void {
  // Action.Execute handler -- must return an Adaptive Card
  app.adaptiveCards.actionExecute("refreshTickets", async (_ctx, _state) => {
    const tickets = [
      { id: "T-1", title: "Login page broken" },
      { id: "T-2", title: "Report export fails" },
    ]; // replace with real DB call
    return CardFactory.adaptiveCard(buildTicketCard(tickets));
  });

  app.adaptiveCards.actionExecute("claimTicket", async (ctx, _state, data) => {
    const ticketId = (data as Record<string, string>).selectedTicket;
    // ... assign ticket ...
    return CardFactory.adaptiveCard({
      type: "AdaptiveCard",
      version: "1.4",
      body: [{ type: "TextBlock", text: `Ticket ${ticketId} claimed by you.` }],
    });
  });
}

pitfalls

  • Missing verb in data: If Action.Submit has no data object (or no routing key), the actionSubmit handler cannot route by verb. Always include { verb: "myAction" } in the data property.

  • Input IDs collide with data keys: If an Input.Text has id: "verb", it overwrites the data.verb routing key when merged into activity.value. Use prefixes (e.g., input_name) or avoid reserved keys.

  • Updating the wrong activity: ctx.activity.replyToId is the ID of the message containing the card. Use this for updateActivity. Using ctx.activity.id targets the invoke activity itself, not the card message.

  • Card version too high: Teams desktop/mobile silently drops elements from schema versions above what the client supports. Stick to version "1.5" for broadest compatibility. Test version "1.6" features explicitly before shipping.

  • Action.Execute vs Action.Submit: Action.Execute requires the handler to return a card (for automatic replacement). Action.Submit handlers are fire-and-forget from the card's perspective. Mixing them up causes silent failures or empty card replacements.

  • Card not rendering: Forgetting CardFactory.adaptiveCard() and instead passing raw JSON to attachments results in a blank message. Always wrap with CardFactory.

  • ChoiceSet value types: All Input.ChoiceSet values arrive as strings in activity.value, even if they look numeric. Parse explicitly with parseInt() or a validation library.

  • 28 KB limit: Large dynamically generated cards (e.g., long lists) can exceed the Teams payload limit. Paginate or truncate before serializing.

references

instructions

This expert covers building, sending, and handling Adaptive Cards in Microsoft Teams bots using the Teams AI SDK v2 (@microsoft/teams-ai) in TypeScript. Use it when you need to:

  • Construct an Adaptive Card JSON payload (body elements, inputs, actions)

  • Send a card as a bot attachment via CardFactory.adaptiveCard() + MessageFactory.attachment()

  • Handle Action.Submit button presses with app.adaptiveCards.actionSubmit(verb, handler)

  • Handle Action.Execute (Universal Actions) with app.adaptiveCards.actionExecute(verb, handler)

  • Extract user input from activity.value (merged input IDs + action data)

  • Update an existing card message vs. sending a new reply

  • Avoid Teams-specific limitations (version caps, unsupported elements, size limits)

Pair with ui.dialogs-task-modules-ts.md for modal/dialog card flows and runtime.routing-handlers-ts.md for broader handler registration context.

research

Deep Research prompt:

"Write a micro expert on Adaptive Cards in Teams (TypeScript). Cover card anatomy, input elements, Action.Submit payloads, sending attachments, handling app.on('card.action'), extracting action identifiers from activity.value, updating messages vs sending new, and Teams-specific card limitations. Include 2-3 canonical card patterns (confirm/cancel, form submit, dynamic choices)."

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