teams-app-developer

name

teams-app-developer

description

Build, test, and deploy code-based Teams apps using the M365 Agents Toolkit CLI. USE FOR: Custom Engine Agents (CEA), Teams bots, tabs, message extensions, Agents Playground local testing, Azure provision/deploy, Slack-to-Teams migration, cross-platform bot development, Block Kit to Adaptive Cards conversion, AI model integration (OpenAI/Azure/Anthropic/Bedrock). DO NOT USE FOR: declarative agents — use the `declarative-agent-developer` skill instead. Triggers: "build a teams bot", "custom engine agent", "CEA", "teams agent", "tab app", "message extension", "test with agents playground", "provision to azure", "deploy to azure", "migrate slack bot", "slack to teams", "convert block kit", "add azure openai to my bot"

Teams App Developer Skill

Build code-based Microsoft 365 agents and Teams apps (CEA, bot, tab, message extension) using the ATK CLI.

Declarative Agents (DA): Use the declarative-agent-developer skill — it owns all DA workflows including scaffolding, manifest editing, capability config, API/MCP plugins, OAuth, localization, and deployment. This skill covers code-based project types only.

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