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/mcp.expose-chatprompt-tools-ts.md

mcp.expose-chatprompt-tools-ts

purpose

Bridging ChatPrompt functions to MCP tools via mcpPlugin.use(prompt) for external discoverability.

rules

  1. Call mcpPlugin.use(prompt) to expose all functions defined on a ChatPrompt instance as MCP tools. Each .function() on the prompt becomes a discoverable, callable MCP tool. github.com/microsoft/teams.ts

  2. The mcpPlugin.use(prompt) call must happen after all .function() definitions on the prompt. Functions added after .use() are not automatically exposed. github.com/microsoft/teams.ts

  3. Function names on the ChatPrompt become MCP tool names. Function descriptions become MCP tool descriptions. JSON Schema parameter definitions are translated to the MCP tool schema. github.com/microsoft/teams.ts

  4. You can combine mcpPlugin.use(prompt) with direct .tool() definitions on the same McpPlugin. Both sets of tools are exposed at the /mcp endpoint. Ensure names are unique across both. github.com/microsoft/teams.ts

  5. Use mcpPlugin.use(prompt) when you want external systems to call the same tools your LLM uses internally. Use direct .tool() when you need MCP-specific features like authInfo or custom return formats that differ from function calling. github.com/microsoft/teams.ts

  6. Functions exposed via .use(prompt) do not have MCP tool hints (readOnlyHint, idempotentHint). If you need hints, define the tool directly with .tool() instead of relying on the bridge. github.com/microsoft/teams.ts

  7. The prompt's function handler receives only the typed parameters object, not the MCP authInfo context. If you need caller validation, define the tool directly with .tool() which provides authInfo. github.com/microsoft/teams.ts

  8. Install the same packages required for both MCP server and AI: @microsoft/teams.mcp, @modelcontextprotocol/sdk, zod, @microsoft/teams.ai, and @microsoft/teams.openai. github.com/microsoft/teams.ts

patterns

Exposing all ChatPrompt functions as MCP tools
import { App } from '@microsoft/teams.apps';
import { ChatPrompt } from '@microsoft/teams.ai';
import { OpenAIChatModel } from '@microsoft/teams.openai';
import { McpPlugin } from '@microsoft/teams.mcp';
import { ConsoleLogger } from '@microsoft/teams.common';
import { DevtoolsPlugin } from '@microsoft/teams.dev';

const model = new OpenAIChatModel({
  apiKey: process.env.OPENAI_API_KEY,
  model: 'gpt-4o',
});

const prompt = new ChatPrompt({
  model,
  instructions: 'You are a helpful assistant with weather and time tools.',
})
  .function('getTime', 'Get the current date and time', () => {
    return new Date().toISOString();
  })
  .function(
    'getWeather',
    'Get weather for a location',
    {
      type: 'object',
      properties: {
        city: { type: 'string', description: 'City name' },
      },
      required: ['city'],
    },
    async ({ city }: { city: string }) => {
      // Simulated weather lookup
      return { city, temperature: '72F', condition: 'sunny' };
    }
  );

const mcpPlugin = new McpPlugin({
  name: 'weather-mcp',
  description: 'Weather and time tools',
});

// Bridge: expose all prompt functions as MCP tools
mcpPlugin.use(prompt);

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

app.on('message', async ({ send, activity }) => {
  const result = await prompt.send(activity.text);
  if (result.content) await send(result.content);
});

app.start(3978);
// MCP tools "getTime" and "getWeather" available at http://localhost:3978/mcp
Combining bridged functions with direct MCP tools
import { App } from '@microsoft/teams.apps';
import { ChatPrompt } from '@microsoft/teams.ai';
import { OpenAIChatModel } from '@microsoft/teams.openai';
import { McpPlugin } from '@microsoft/teams.mcp';
import { DevtoolsPlugin } from '@microsoft/teams.dev';
import { z } from 'zod';

const model = new OpenAIChatModel({
  apiKey: process.env.OPENAI_API_KEY,
  model: 'gpt-4o',
});

// Functions used by the LLM internally
const prompt = new ChatPrompt({
  model,
  instructions: 'You are a helpful assistant.',
})
  .function('searchDocs', 'Search documentation', {
    type: 'object',
    properties: {
      query: { type: 'string', description: 'Search query' },
    },
    required: ['query'],
  }, async ({ query }: { query: string }) => {
    return [{ title: 'Getting Started', snippet: 'How to set up...' }];
  });

const mcpPlugin = new McpPlugin({
  name: 'hybrid-server',
  description: 'Documentation search and admin tools',
});

// Expose LLM functions as MCP tools (searchDocs)
mcpPlugin.use(prompt);

// Add MCP-only tools with authInfo and hints
mcpPlugin.tool(
  'adminReset',
  'Reset a user session (admin only)',
  {
    userId: z.string().describe('User ID to reset'),
  },
  // No readOnlyHint -- this is a mutating operation
  async ({ userId }, { authInfo }) => {
    if (!authInfo) {
      return { content: [{ type: 'text', text: 'Unauthorized' }] };
    }
    // Perform reset...
    return {
      content: [{ type: 'text', text: `Session reset for ${userId}` }],
    };
  }
);

const app = new App({
  plugins: [new DevtoolsPlugin(), mcpPlugin],
});

app.start(3978);
// MCP exposes both "searchDocs" (from prompt) and "adminReset" (direct)
When to use .use(prompt) vs direct .tool()
import { ChatPrompt } from '@microsoft/teams.ai';
import { McpPlugin } from '@microsoft/teams.mcp';
import { z } from 'zod';

// Use mcpPlugin.use(prompt) when:
// - You want external MCP clients to call the same functions your LLM uses
// - The functions are stateless and do not need caller identity
// - You want to avoid duplicating function definitions

// Use direct .tool() when:
// - You need authInfo to validate the caller
// - You need tool hints (readOnlyHint, idempotentHint)
// - The tool is MCP-only and should NOT be available to the LLM
// - The return format differs from function calling (MCP content array)

const prompt = new ChatPrompt({ model: myModel, instructions: '...' })
  .function('safeRead', 'Read data (no auth needed)', async () => 'data');

const mcpPlugin = new McpPlugin({ name: 'example', description: 'Example' });

// Bridge safe functions
mcpPlugin.use(prompt);

// Define sensitive tools directly with auth
mcpPlugin.tool(
  'deleteRecord',
  'Delete a record (requires auth)',
  { recordId: z.string().describe('Record ID') },
  async ({ recordId }, { authInfo }) => {
    if (!authInfo) {
      return { content: [{ type: 'text', text: 'Unauthorized' }] };
    }
    return { content: [{ type: 'text', text: `Deleted ${recordId}` }] };
  }
);

pitfalls

  • Calling .use(prompt) before defining functions: Functions added to the prompt after mcpPlugin.use(prompt) may not be exposed. Define all .function() calls first, then call .use().

  • Tool name collisions: If a prompt function has the same name as a direct .tool() definition, behavior is undefined. Ensure unique names across both sources.

  • Expecting authInfo in bridged functions: Functions exposed via .use(prompt) do not receive MCP's authInfo. If you need caller validation, define the tool directly with .tool().

  • Missing tool hints on bridged functions: The .use(prompt) bridge does not set readOnlyHint or idempotentHint. MCP clients will assume the default (potential side effects). Use direct .tool() for hinted tools.

  • Exposing dangerous functions: Every function on the prompt becomes externally callable via MCP. Review all prompt functions before calling .use() to ensure none should be internal-only.

  • Forgetting to add McpPlugin to App: Even with .use(prompt) configured, the MCP endpoint is not registered unless the plugin is in the App's plugins array.

references

instructions

This expert covers bridging ChatPrompt function-calling tools to MCP tools using mcpPlugin.use(prompt) in the Teams AI Library v2 (@microsoft/teams.ts). Use it when you need to:

  • Expose existing ChatPrompt .function() definitions as externally discoverable MCP tools

  • Understand when to use mcpPlugin.use(prompt) vs defining tools directly with .tool()

  • Combine bridged prompt functions with direct MCP tool definitions on the same plugin

  • Understand the limitations of the bridge (no authInfo, no tool hints)

Pair with mcp.server-basics-ts.md for direct tool definition patterns and mcp.security-ts.md for securing exposed tools. Pair with mcp.server-basics-ts.md for McpPlugin setup, and ai.function-calling-implementation-ts.md for the ChatPrompt functions being bridged.

research

Deep Research prompt:

"Write a micro expert on bridging ChatPrompt functions to MCP tools via mcpPlugin.use(prompt) in Teams SDK v2 (TypeScript). Cover how the bridge works, what gets translated (names, descriptions, schemas), limitations (no authInfo, no hints), when to use .use(prompt) vs direct .tool(), combining both approaches, and security considerations. Include 2-3 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