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/bridge/workflow.composable-platform-ts.md

workflow.composable-platform-ts

purpose

Architectural guide for building a composable, reusable workflow operating layer inside Teams — the five-element framework (trigger, state, logic, intelligence, visibility) as a platform pattern, not a point solution.

rules

  1. Every workflow follows the same five-element lifecycle. (1) Trigger — how it starts, (2) State — where records live, (3) Logic — how decisions and automation execute, (4) Intelligence — how AI is layered over state, (5) Visibility — how records remain embedded in channels. Design every workflow as an instantiation of this lifecycle.

  2. Define workflows as configuration, not code. A workflow definition specifies: trigger type + parameters, list schema (columns and types), routing rules (approval chain, auto-assign), query functions (NL schemas), and card templates (active/completed/error). The runtime consumes these definitions generically.

  3. Use a WorkflowDefinition interface as the core abstraction. This interface describes the workflow's schema, triggers, routing, and card templates. The runtime registers handlers dynamically from definitions. New workflows require a new definition object, not new handler code.

  4. Template workflows are reference implementations. Provide polished, out-of-the-box definitions for common scenarios: time-off requests, equipment booking, daily standup, account health. These serve as both usable workflows and examples for customization.

  5. The runtime is a generic workflow engine. A single set of handlers (message, card.action, proactive, webhooks) dispatch to the correct workflow based on the verb/command prefix in the message or action data. The engine creates records, processes actions, and renders cards for any registered workflow.

  6. SharePoint Lists are the default state backend. Each workflow definition maps to a SharePoint list. The engine creates lists on first use, following the schema in the definition. For enterprise needs, swap to Dataverse without changing the workflow definition.

  7. Card templates are parameterized, not hardcoded. Define card templates as functions that take a record and return an Adaptive Card. The workflow definition includes templates for: activeCard, completedCard, listCard, and formCard. The engine calls the right template based on record state.

  8. Query functions are auto-generated from the schema. Given a workflow definition's column schema, generate AI function-calling schemas automatically: each filterable column becomes a parameter. This eliminates writing per-workflow query functions manually.

  9. Extensibility points for ecosystem partners. The composable platform should expose: (a) custom trigger types (plugin new event sources), (b) custom logic steps (plugin business rules), (c) custom card templates (brand and layout), (d) custom state backends (plugin storage). Each point has a defined interface.

  10. Cross-workflow queries are first-class. The engine registers a queryAnyWorkflow function that searches across all registered workflow lists. Users ask "what's overdue?" and get results from PTO, equipment, and standup workflows combined.

  11. Power Automate integration is optional, not required. The composable platform can execute logic in-bot (state machine) or delegate to Power Automate flows. Workflow definitions specify executionMode: "bot" | "powerAutomate" | "hybrid". Bot mode is the default for SMB; Power Automate mode for enterprise.

patterns

WorkflowDefinition interface
interface WorkflowDefinition {
  id: string;                          // Unique workflow identifier
  name: string;                        // Display name
  description: string;                 // Used in command suggestions and AI descriptions
  commandPrefix: string;               // e.g., "/pto", "/book", "/standup"

  // Schema
  columns: ColumnDefinition[];         // Maps to SharePoint List columns
  statusField: string;                 // Which column tracks lifecycle state
  statusValues: {
    active: string[];                  // e.g., ["Pending", "InProgress"]
    completed: string[];               // e.g., ["Approved", "Rejected", "Done"]
  };

  // Triggers
  triggers: TriggerConfig[];

  // Routing
  routing?: {
    type: "none" | "single" | "sequential" | "parallel-any" | "parallel-all";
    approverSource: "fixed" | "manager" | "field";  // Where to find the approver
    approverField?: string;            // Column name if approverSource is "field"
    escalationTimeoutMs?: number;
  };

  // Cards
  cards: {
    active: (record: any) => object;
    completed: (record: any) => object;
    list: (records: any[]) => object;
    form?: () => object;               // For message extension action trigger
  };

  // AI
  queryDescription: string;            // Describes when AI should call the query function
  filterableColumns: string[];         // Columns exposed as AI function parameters
}

interface ColumnDefinition {
  name: string;
  type: "text" | "number" | "dateTime" | "choice" | "personOrGroup" | "boolean";
  choices?: string[];                  // For choice columns
  required?: boolean;
}

interface TriggerConfig {
  type: "command" | "messageExtension" | "scheduled" | "stateChange";
  config: Record<string, any>;         // Trigger-specific configuration
}
Register a workflow from a definition
function registerWorkflow(app: any, engine: WorkflowEngine, definition: WorkflowDefinition) {
  // Command trigger
  const commandTrigger = definition.triggers.find((t) => t.type === "command");
  if (commandTrigger) {
    const regex = new RegExp(`^\\${definition.commandPrefix}\\s*(.*)$`, "i");
    app.message(regex, async (ctx: any) => {
      await engine.handleCommand(ctx, definition);
    });
  }

  // Scheduled trigger
  const scheduledTrigger = definition.triggers.find((t) => t.type === "scheduled");
  if (scheduledTrigger) {
    cron.schedule(scheduledTrigger.config.cron, async () => {
      await engine.handleScheduled(definition);
    });
  }

  // Register AI query function
  engine.registerQueryFunction(definition);
}
Generic workflow engine
class WorkflowEngine {
  private definitions = new Map<string, WorkflowDefinition>();
  private graphClient: Client;
  private siteId: string;
  private lists = new Map<string, string>(); // workflowId -> listId

  async handleCommand(ctx: any, def: WorkflowDefinition) {
    const params = parseCommandParams(ctx.activity.text!, def);
    const record = await this.createRecord(def, {
      ...params,
      requesterId: ctx.activity.from?.aadObjectId,
      requesterName: ctx.activity.from?.name,
      conversationId: ctx.activity.conversation?.id,
      serviceUrl: ctx.activity.serviceUrl,
    });

    const card = def.cards.active(record);
    const response = await ctx.send({
      attachments: [{
        contentType: "application/vnd.microsoft.card.adaptive",
        content: card,
      }],
    });

    // Store activity ID for future updates
    await this.updateRecordField(def, record.id, "CardActivityId", response.id);

    // Start escalation timer if routing is configured
    if (def.routing?.escalationTimeoutMs) {
      this.startEscalation(def, record);
    }
  }

  async handleAction(ctx: any, verb: string, data: any) {
    const def = this.definitions.get(data.workflowId);
    if (!def) return;

    const record = await this.getRecord(def, data.recordId);

    if (verb === "approve" || verb === "reject") {
      return this.processApproval(ctx, def, record, verb, data.comment);
    }

    if (verb.startsWith("refresh")) {
      const card = record.status === "completed"
        ? def.cards.completed(record)
        : def.cards.active(record);
      return {
        status: 200,
        body: {
          statusCode: 200,
          type: "application/vnd.microsoft.card.adaptive",
          value: card,
        },
      };
    }
  }

  registerQueryFunction(def: WorkflowDefinition) {
    // Auto-generate AI function schema from definition
    const parameters: Record<string, any> = {};
    for (const col of def.filterableColumns) {
      const colDef = def.columns.find((c) => c.name === col);
      if (!colDef) continue;

      switch (colDef.type) {
        case "choice":
          parameters[col] = { type: "string", enum: colDef.choices };
          break;
        case "dateTime":
          parameters[col] = { type: "string", description: `Filter by ${col} (ISO date)` };
          break;
        case "personOrGroup":
          parameters[col] = { type: "string", description: `Filter by ${col} name` };
          break;
        default:
          parameters[col] = { type: "string" };
      }
    }

    return {
      name: `query_${def.id}`,
      description: def.queryDescription,
      parameters: { type: "object", properties: parameters },
    };
  }

  private async createRecord(def: WorkflowDefinition, fields: Record<string, any>) {
    const listId = await this.ensureList(def);
    const item = await this.graphClient
      .api(`/sites/${this.siteId}/lists/${listId}/items`)
      .post({ fields });
    return { id: item.id, ...item.fields };
  }

  private async ensureList(def: WorkflowDefinition): Promise<string> {
    if (this.lists.has(def.id)) return this.lists.get(def.id)!;

    // Check if list exists, create if not
    try {
      const existing = await this.graphClient
        .api(`/sites/${this.siteId}/lists`)
        .filter(`displayName eq '${def.name}'`)
        .get();

      if (existing.value.length > 0) {
        this.lists.set(def.id, existing.value[0].id);
        return existing.value[0].id;
      }
    } catch { /* List doesn't exist */ }

    const list = await this.graphClient
      .api(`/sites/${this.siteId}/lists`)
      .post({
        displayName: def.name,
        list: { template: "genericList" },
        columns: def.columns.map(colDefToGraphColumn),
      });

    this.lists.set(def.id, list.id);
    return list.id;
  }
}
Template workflow: Time-Off Request
const ptoWorkflow: WorkflowDefinition = {
  id: "pto",
  name: "PTO Requests",
  description: "Time-off and vacation request workflow",
  commandPrefix: "/pto",
  columns: [
    { name: "Requester", type: "personOrGroup", required: true },
    { name: "StartDate", type: "dateTime", required: true },
    { name: "EndDate", type: "dateTime", required: true },
    { name: "HoursRequested", type: "number" },
    { name: "Status", type: "choice", choices: ["Pending", "Approved", "Rejected"] },
    { name: "ApprovedBy", type: "personOrGroup" },
    { name: "Reason", type: "text" },
  ],
  statusField: "Status",
  statusValues: {
    active: ["Pending"],
    completed: ["Approved", "Rejected"],
  },
  triggers: [
    { type: "command", config: { pattern: "/pto START to END" } },
    { type: "messageExtension", config: { commandId: "createPto" } },
  ],
  routing: {
    type: "single",
    approverSource: "manager",
    escalationTimeoutMs: 48 * 60 * 60 * 1000, // 48 hours
  },
  cards: {
    active: buildPtoActiveCard,
    completed: buildPtoCompletedCard,
    list: buildPtoListCard,
  },
  queryDescription: "Query PTO/time-off requests. Use when user asks about PTO, vacation, leave, days off.",
  filterableColumns: ["Status", "Requester", "StartDate"],
};

// Register
registerWorkflow(app, engine, ptoWorkflow);

pitfalls

  • Over-abstraction kills velocity. The composable platform should start with 2-3 template workflows and extract common patterns. Don't build the full generic engine before validating with real workflows.

  • Schema migrations are hard. Once a SharePoint List is created, adding required columns or changing types is disruptive. Version your schemas and handle missing columns gracefully.

  • Generic engines produce generic cards. Template card functions should be polished, not auto-generated. The best workflow UX comes from purpose-built card layouts, not generic field renderers.

  • Power Automate hybrid mode adds complexity. Supporting both bot-native and Power Automate execution means two code paths, two monitoring surfaces, and two failure modes. Default to bot-native for the FHL; add Power Automate later.

  • Ecosystem extensibility requires stable interfaces. Don't expose extension points until the core patterns stabilize through 3+ real workflow implementations.

references

instructions

Use this expert when designing the overall composable workflow architecture. Covers the five-element lifecycle framework, WorkflowDefinition interface, generic engine patterns, template workflows, auto-generated AI query schemas, and extensibility points. Pair with ../teams/workflow.sharepoint-lists-ts.md for state persistence, ../teams/workflow.message-native-records-ts.md for card-as-record patterns, ../teams/workflow.triggers-compose-ts.md for trigger unification, ../teams/ai.conversational-query-ts.md for NL retrieval, and ../teams/workflow.approvals-inline-ts.md for approval routing.

research

Deep Research prompt:

"Write a micro expert on designing a composable workflow platform inside Microsoft Teams (TypeScript). Cover: five-element lifecycle framework (trigger, state, logic, intelligence, visibility), WorkflowDefinition configuration interface, generic workflow engine that dispatches from definitions, template/reference workflows (PTO, equipment, standup), auto-generated AI function schemas from column definitions, SharePoint Lists as pluggable state backend, Power Automate hybrid execution mode, and ecosystem extensibility points. Include complete patterns for the definition interface, engine registration, and one template workflow."

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