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/convert/ruby-to-ts-ts.md

ruby-to-ts-ts

purpose

Rewriting Ruby source code as idiomatic TypeScript — mapping Ruby language constructs, OOP patterns, metaprogramming, and common idioms to their TypeScript equivalents.

rules

  1. Ruby blocks (do...end / { |x| }) map to arrow functions. array.each { |item| puts item } becomes array.forEach((item) => console.log(item)). Ruby's yield inside methods maps to calling a callback parameter.

  2. Ruby mixins (include Module) map to TypeScript interfaces + composition. Do NOT use class inheritance to simulate mixins — use interface implementation with helper functions or the mixin pattern (applyMixins).

  3. Ruby duck typing maps to TypeScript structural typing. If Ruby code checks obj.respond_to?(:method), define an interface with that method and use a type guard: function hasMethod(obj: unknown): obj is HasMethod.

  4. Ruby attr_accessor :name maps to a class property with TypeScript accessor shorthand: constructor(public name: string) {} or explicit get/set pairs if logic is needed.

  5. Ruby symbols (:name) map to string literal types or enum members. A method accepting type: :admin | :user becomes type: 'admin' | 'user' in TypeScript.

  6. Ruby hashes ({ key: value }) map to TypeScript objects or Record<string, T>. Named-parameter hashes (def method(opts = {})) become destructured typed parameters: function method({ key1, key2 }: Options).

  7. Ruby nil maps to null or undefined. Use null for explicit absence and undefined for optional/missing. Ruby's &. safe navigator maps to optional chaining (?.).

  8. Ruby begin/rescue/ensure maps to try/catch/finally. Ruby's typed rescue (rescue TypeError => e) maps to catching and narrowing: catch (e) { if (e instanceof TypeError) ... }.

  9. Ruby open classes and monkey-patching have NO TypeScript equivalent. Redesign as wrapper functions, decorator patterns, or module augmentation (declare module for extending third-party types).

  10. Ruby metaprogramming (define_method, method_missing, send) has no direct equivalent. Replace define_method loops with computed property patterns or factory functions. Replace method_missing with Proxy objects (sparingly) or explicit handler maps.

  11. Ruby's Enumerable methods map to JavaScript array methods: map→map, select→filter, reject→filter (inverted), reduce→reduce, detect/find→find, flat_map→flatMap, each_with_object→reduce, group_by→custom groupBy or Object.groupBy().

  12. Ruby string interpolation "Hello #{name}" maps to template literals `Hello ${name}`.

  13. Ruby Proc.new / lambda / -> all map to arrow functions. Ruby's distinction between procs and lambdas (arity checking, return behavior) disappears — TypeScript arrow functions always behave like Ruby lambdas.

  14. Ruby modules used as namespaces map to TypeScript modules (files) with named exports. Do NOT use TypeScript namespace keyword — use ES module export instead.

patterns

Ruby class with mixins → TypeScript interface + composition
# --- Before (Ruby) ---
module Greetable
  def greet
    "Hello, I'm #{name}"
  end
end

module Trackable
  def track(event)
    puts "Tracking #{event} for #{name}"
  end
end

class User
  include Greetable
  include Trackable

  attr_accessor :name, :email

  def initialize(name, email)
    @name = name
    @email = email
  end
end

user = User.new("Alice", "[email protected]")
puts user.greet
user.track("login")
// --- After (TypeScript) ---
interface Greetable {
  name: string;
  greet(): string;
}

function greetMixin<T extends { name: string }>(obj: T): T & Greetable {
  return Object.assign(obj, {
    greet() {
      return `Hello, I'm ${obj.name}`;
    },
  });
}

interface Trackable {
  name: string;
  track(event: string): void;
}

function trackMixin<T extends { name: string }>(obj: T): T & Trackable {
  return Object.assign(obj, {
    track(event: string) {
      console.log(`Tracking ${event} for ${obj.name}`);
    },
  });
}

class User {
  constructor(
    public name: string,
    public email: string,
  ) {}
}

// Apply mixins
function createUser(name: string, email: string): User & Greetable & Trackable {
  const user = new User(name, email);
  return trackMixin(greetMixin(user));
}

const user = createUser("Alice", "[email protected]");
console.log(user.greet());
user.track("login");
Ruby hash options / keyword args → TypeScript typed parameters
# --- Before (Ruby) ---
class SlackNotifier
  def initialize(opts = {})
    @webhook_url = opts[:webhook_url] || ENV['SLACK_WEBHOOK']
    @channel = opts[:channel] || '#general'
    @username = opts[:username] || 'bot'
  end

  def notify(message, opts = {})
    icon = opts.fetch(:icon_emoji, ':robot_face:')
    thread_ts = opts[:thread_ts]
    # ... send notification
  end
end

notifier = SlackNotifier.new(webhook_url: 'https://...', channel: '#alerts')
notifier.notify('Deploy complete', icon_emoji: ':rocket:')
// --- After (TypeScript) ---
interface SlackNotifierOptions {
  webhookUrl?: string;
  channel?: string;
  username?: string;
}

interface NotifyOptions {
  iconEmoji?: string;
  threadTs?: string;
}

class SlackNotifier {
  private readonly webhookUrl: string;
  private readonly channel: string;
  private readonly username: string;

  constructor({
    webhookUrl = process.env.SLACK_WEBHOOK ?? '',
    channel = '#general',
    username = 'bot',
  }: SlackNotifierOptions = {}) {
    this.webhookUrl = webhookUrl;
    this.channel = channel;
    this.username = username;
  }

  notify(message: string, { iconEmoji = ':robot_face:', threadTs }: NotifyOptions = {}): void {
    // ... send notification
  }
}

const notifier = new SlackNotifier({ webhookUrl: 'https://...', channel: '#alerts' });
notifier.notify('Deploy complete', { iconEmoji: ':rocket:' });
Ruby Enumerable → TypeScript array methods
# --- Before (Ruby) ---
users = get_users()
active_admins = users
  .select { |u| u.active? }
  .reject { |u| u.guest? }
  .select { |u| u.role == :admin }
  .map { |u| { name: u.name, email: u.email } }
  .sort_by { |h| h[:name] }
// --- After (TypeScript) ---
interface User {
  name: string;
  email: string;
  active: boolean;
  guest: boolean;
  role: 'admin' | 'user' | 'guest';
}

const users: User[] = getUsers();
const activeAdmins = users
  .filter((u) => u.active)
  .filter((u) => !u.guest)
  .filter((u) => u.role === 'admin')
  .map((u) => ({ name: u.name, email: u.email }))
  .sort((a, b) => a.name.localeCompare(b.name));

pitfalls

  • Ruby truthiness vs JS truthiness: In Ruby, only nil and false are falsy. In JS/TS, 0, "", NaN, null, undefined, and false are all falsy. Ruby code like if count (truthy when 0) must become if (count !== null && count !== undefined) in TS.

  • Ruby == is value equality; JS === is identity for objects: Ruby == on strings/numbers compares values. TS === on primitives works the same, but on objects it compares references. Deep equality requires a library or custom check.

  • each return value: Ruby's each returns the original array. JS forEach returns undefined. Don't chain after forEach.

  • Ruby ranges (1..10): No TS equivalent. Use Array.from({ length: 10 }, (_, i) => i + 1) or a simple for loop.

  • String is mutable in Ruby, immutable in JS: Ruby str.gsub! mutates in place. TS strings are immutable — always reassign: str = str.replace(...).

  • Ruby exception hierarchy: Ruby has StandardError, RuntimeError, etc. TS/JS only has Error. Use custom error classes extending Error if you need a hierarchy.

  • Snake_case to camelCase: Ruby uses snake_case for methods/variables. TypeScript convention is camelCase. Convert all identifiers, but keep API payloads in their original format (e.g., Slack payloads use snake_case).

  • Ruby require is file-level, not scoped: All Ruby require statements load globally. TS import is scoped to the file. This means Ruby's implicit global availability must become explicit imports in every file that uses the dependency.

  • Sinatra/Rack → Express: Ruby Sinatra routes (get '/' do ... end) map to Express (app.get('/', (req, res) => { ... })). The middleware patterns are similar but request/response APIs differ completely.

references

instructions

Use this expert when rewriting Ruby source code in TypeScript. Start by identifying the Ruby constructs in use (classes, modules/mixins, blocks, metaprogramming, Enumerable chains) and map each to its TS equivalent using the rules above. Pay special attention to truthiness differences, mixin patterns, and naming convention changes (snake_case → camelCase). Pair with dependency-mapping-ts.md for gem → npm package equivalents, and type-mapping-ts.md for cross-language type reference.

research

Deep Research prompt:

"Write a micro expert on converting Ruby to TypeScript. Cover: blocks to arrow functions, mixins to interfaces/composition, duck typing to structural typing, attr_accessor to class properties, symbol to string literals, hash options to typed parameters, metaprogramming alternatives, Enumerable methods to array methods, exception handling, truthiness differences, and naming convention conversion (snake_case to camelCase). Include 3 worked 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