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.message-extensions-ts.md

ui.message-extensions-ts

purpose

Search-based and action-based message extensions (compose extensions) for Teams bots using the Teams AI Library v2.

rules

  1. Configure message extensions in appPackage/manifest.json under the composeExtensions array. Each extension has a botId, commands array, and each command specifies type (query for search, action for task module). learn.microsoft.com -- Message extensions

  2. Handle search queries with app.on('message.ext.query', handler). The handler receives the query text in activity.value.parameters[0].value and must return a response with composeExtension.type: 'result' containing an attachments array. learn.microsoft.com -- Search extensions

  3. Set attachmentLayout to 'list' for vertical result layout or 'grid' for a tile grid. Use 'list' for text-heavy results and 'grid' for image-heavy results. learn.microsoft.com -- Respond to search

  4. Each attachment in the results array needs both a content (the full Adaptive Card inserted into the compose box) and a preview (a smaller Thumbnail Card shown in the search results list). The preview uses contentType: 'application/vnd.microsoft.card.thumbnail'. learn.microsoft.com -- Respond to search

  5. Handle action-based extensions with two routes: app.on('message.ext.open', handler) for displaying the task module form (composeExtension/fetchTask) and app.on('message.ext.submit', handler) for processing the submitted data (composeExtension/submitAction). learn.microsoft.com -- Action extensions

  6. The message.ext.open handler returns a task module response identical to dialog.open: { status: 200, body: { task: { type: 'continue', value: { title, card } } } }. learn.microsoft.com -- Action extensions

  7. The message.ext.submit handler receives form data in activity.value.data and can return a card to insert into the compose box or perform a server-side action. learn.microsoft.com -- Action extensions

  8. Manifest command parameters define the search fields displayed in the Teams UI. Each parameter has name, title, and optionally description and inputType. The first parameter is the default search field. learn.microsoft.com -- Define search command

  9. Search result counts should be limited (10-15 items) because Teams truncates long result lists. Always handle empty query strings gracefully by returning popular or recent results. learn.microsoft.com -- Search extensions

  10. Handle link unfurling with app.on('message.ext.query-link', handler). This fires when a user pastes a URL matching a domain in the manifest's messageHandlers. Return a card attachment to preview the link. learn.microsoft.com -- Link unfurling

patterns

Search-based message extension
import { App } from '@microsoft/teams.apps';
import { ConsoleLogger } from '@microsoft/teams.common';
import { DevtoolsPlugin } from '@microsoft/teams.dev';

// Manifest excerpt (appPackage/manifest.json):
// {
//   "composeExtensions": [{
//     "botId": "${{BOT_ID}}",
//     "commands": [{
//       "id": "searchCmd",
//       "type": "query",
//       "title": "Search Products",
//       "parameters": [{ "name": "query", "title": "Search query" }]
//     }]
//   }]
// }

interface Product {
  id: string;
  title: string;
  description: string;
  price: number;
  imageUrl: string;
}

async function searchProducts(query: string): Promise<Product[]> {
  // Replace with your actual search logic
  const products: Product[] = [
    { id: '1', title: 'Widget Pro', description: 'A premium widget', price: 29.99, imageUrl: 'https://example.com/widget.png' },
    { id: '2', title: 'Gadget Plus', description: 'An advanced gadget', price: 49.99, imageUrl: 'https://example.com/gadget.png' },
  ];
  return products.filter(p =>
    p.title.toLowerCase().includes(query.toLowerCase())
  );
}

const app = new App({
  logger: new ConsoleLogger('ext-bot'),
  plugins: [new DevtoolsPlugin()],
});

app.on('message.ext.query', async ({ activity }) => {
  const query = activity.value.parameters?.[0]?.value || '';
  const results = await searchProducts(query);

  return {
    status: 200,
    body: {
      composeExtension: {
        type: 'result',
        attachmentLayout: 'list',
        attachments: results.map(item => ({
          // Full card inserted into compose box when selected
          contentType: 'application/vnd.microsoft.card.adaptive',
          content: {
            type: 'AdaptiveCard',
            version: '1.5',
            body: [
              { type: 'TextBlock', text: item.title, weight: 'Bolder', size: 'Large' },
              { type: 'TextBlock', text: item.description, wrap: true },
              { type: 'TextBlock', text: `Price: $${item.price}`, weight: 'Bolder' },
            ],
          },
          // Preview card shown in search results list
          preview: {
            contentType: 'application/vnd.microsoft.card.thumbnail',
            content: {
              title: item.title,
              text: `$${item.price} - ${item.description}`,
              images: [{ url: item.imageUrl }],
            },
          },
        })),
      },
    },
  };
});

app.start(3978);
Action-based message extension with task module
import { App } from '@microsoft/teams.apps';
import { ConsoleLogger } from '@microsoft/teams.common';
import { DevtoolsPlugin } from '@microsoft/teams.dev';

// Manifest excerpt (appPackage/manifest.json):
// {
//   "composeExtensions": [{
//     "botId": "${{BOT_ID}}",
//     "commands": [{
//       "id": "createItem",
//       "type": "action",
//       "title": "Create Item",
//       "fetchTask": true
//     }]
//   }]
// }

const app = new App({
  logger: new ConsoleLogger('action-ext-bot'),
  plugins: [new DevtoolsPlugin()],
});

// Open a task module form when the action is triggered
app.on('message.ext.open', async () => {
  return {
    status: 200,
    body: {
      task: {
        type: 'continue',
        value: {
          title: 'Create New Item',
          width: 'medium',
          height: 'medium',
          card: {
            contentType: 'application/vnd.microsoft.card.adaptive',
            content: {
              type: 'AdaptiveCard',
              version: '1.5',
              body: [
                {
                  type: 'TextBlock',
                  text: 'Create a new item',
                  weight: 'Bolder',
                  size: 'Large',
                },
                {
                  type: 'Input.Text',
                  id: 'title',
                  label: 'Title',
                  isRequired: true,
                  errorMessage: 'Title is required',
                },
                {
                  type: 'Input.Text',
                  id: 'description',
                  label: 'Description',
                  isMultiline: true,
                },
                {
                  type: 'Input.ChoiceSet',
                  id: 'priority',
                  label: 'Priority',
                  value: 'medium',
                  choices: [
                    { title: 'Low', value: 'low' },
                    { title: 'Medium', value: 'medium' },
                    { title: 'High', value: 'high' },
                  ],
                },
              ],
              actions: [
                { type: 'Action.Submit', title: 'Create' },
              ],
            },
          },
        },
      },
    },
  };
});

// Process the submitted form data
app.on('message.ext.submit', async ({ activity, send }) => {
  const data = activity.value.data;
  const { title, description, priority } = data;

  // Create the item in your backend
  const itemId = `ITEM-${Date.now()}`;

  await send(`Created item "${title}" (${priority} priority) - ID: ${itemId}`);
});

app.start(3978);
Combined search and action extensions
import { App } from '@microsoft/teams.apps';

// Manifest excerpt (appPackage/manifest.json):
// {
//   "composeExtensions": [{
//     "botId": "${{BOT_ID}}",
//     "commands": [
//       {
//         "id": "searchItems",
//         "type": "query",
//         "title": "Search Items",
//         "parameters": [{ "name": "query", "title": "Search" }]
//       },
//       {
//         "id": "createItem",
//         "type": "action",
//         "title": "Create Item",
//         "fetchTask": true
//       }
//     ]
//   }]
// }

const app = new App();

// Search extension handler
app.on('message.ext.query', async ({ activity }) => {
  const query = activity.value.parameters?.[0]?.value || '';
  const commandId = activity.value.commandId;

  // You can route by commandId if multiple search commands exist
  const items = [
    { id: '1', title: 'Task Alpha', status: 'open' },
    { id: '2', title: 'Task Beta', status: 'closed' },
  ].filter(i => i.title.toLowerCase().includes(query.toLowerCase()));

  return {
    status: 200,
    body: {
      composeExtension: {
        type: 'result',
        attachmentLayout: 'list',
        attachments: items.map(item => ({
          contentType: 'application/vnd.microsoft.card.adaptive',
          content: {
            type: 'AdaptiveCard',
            version: '1.5',
            body: [
              { type: 'TextBlock', text: item.title, weight: 'Bolder' },
              { type: 'TextBlock', text: `Status: ${item.status}` },
            ],
          },
          preview: {
            contentType: 'application/vnd.microsoft.card.thumbnail',
            content: {
              title: item.title,
              text: `Status: ${item.status}`,
            },
          },
        })),
      },
    },
  };
});

// Action extension: open form
app.on('message.ext.open', async () => {
  return {
    status: 200,
    body: {
      task: {
        type: 'continue',
        value: {
          title: 'Create Item',
          card: {
            contentType: 'application/vnd.microsoft.card.adaptive',
            content: {
              type: 'AdaptiveCard',
              version: '1.5',
              body: [
                { type: 'Input.Text', id: 'title', label: 'Title', isRequired: true },
                { type: 'Input.Text', id: 'notes', label: 'Notes', isMultiline: true },
              ],
              actions: [
                { type: 'Action.Submit', title: 'Create' },
              ],
            },
          },
        },
      },
    },
  };
});

// Action extension: process submission
app.on('message.ext.submit', async ({ activity, send }) => {
  const { title, notes } = activity.value.data;
  await send(`Created: ${title}${notes ? ` - ${notes}` : ''}`);
});

app.start(3978);

pitfalls

  • Missing manifest composeExtensions: Message extensions require the composeExtensions array in the manifest. Without it, the extension does not appear in the Teams compose box. Update the manifest and re-sideload after changes.

  • Empty query handling: Users often open the search extension without typing. Handle empty or blank query strings by returning popular/recent results instead of an empty list.

  • Missing preview card: Each search result attachment must include a preview with contentType: 'application/vnd.microsoft.card.thumbnail'. Without it, the result appears blank in the search results list.

  • Wrong route handler: Search uses message.ext.query (not message.ext.open). Action uses message.ext.open + message.ext.submit. Mixing them up results in handlers never firing.

  • Too many results: Teams limits the number of displayed results. Return 10-15 items maximum. Longer lists are silently truncated.

  • Attachment layout mismatch: Using 'grid' layout requires images in the preview. Using 'grid' with text-only thumbnails produces a poor visual experience. Match layout to content type.

  • Not setting fetchTask: true for action commands: In the manifest, action commands must have "fetchTask": true for the message.ext.open handler to fire. Without it, Teams does not invoke the task module.

  • Preview vs content confusion: The preview is what users see in the results dropdown. The content is what gets inserted when they select it. A missing or incorrect content card means the wrong card (or nothing) is inserted.

references

instructions

This expert covers search-based and action-based message extensions (compose extensions) in Microsoft Teams bots built with the Teams AI Library v2 (@microsoft/teams.ts) in TypeScript. Use it when you need to:

  • Configure composeExtensions in the manifest with search (query) or action commands

  • Handle search queries with app.on('message.ext.query', ...) and return result attachments with previews

  • Handle action extensions with app.on('message.ext.open', ...) for task modules and app.on('message.ext.submit', ...) for processing

  • Build thumbnail preview cards for search results

  • Choose between 'list' and 'grid' attachment layouts

  • Combine search and action commands in a single extension

Pair with ui.adaptive-cards-ts.md for card construction and ui.dialogs-task-modules-ts.md for task module patterns used in action extensions. Pair with runtime.manifest-ts.md for composeExtensions manifest configuration, and ui.adaptive-cards-ts.md for building card attachments returned by extensions.

research

Deep Research prompt:

"Write a micro expert on Message Extensions in Teams (TypeScript). Cover manifest composeExtensions configuration, search-based query flow (message.ext.query handler, parameters, result attachments with preview), action-based flow (message.ext.open for task module, message.ext.submit for processing), attachment layouts (list/grid), thumbnail preview cards, link unfurling, and common pitfalls. Include 2-3 canonical TypeScript code examples."

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