Sub-skill of microsoft-365-agents-toolkit. Routed expert system with 100+ micro-expert files for migrating Slack bots to Teams, cross-platform bridging, and dual-platform bot development. USE FOR: migrating Slack bot to Teams, adding Teams support to Slack bot, building dual-platform bots, converting Block Kit to Adaptive Cards, identity/OAuth bridging, deploying bots to Azure or AWS, configuring AI model providers. DO NOT USE FOR: general web development, non-bot projects, standalone Teams deve
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/11/2026
What it changes
Passed 19 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill86%
Checks it passed that the model alone missed
References docs/workflows.md
Classifies Go as Tier 4 No SDK
References docs/ui-components.md
and 24 more in the full report
16 fixed3 passed either way3 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+48%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/11/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Which file provides instructions for packaging, validating, sharing, and managing environments with Microsoft Agents Toolkit CLI commands?
What was checked, without and with the skill
Checked
Without skill
With skill
References commands.md located at toolkit/commands.md
Missed
Passed
case-13 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md163 linessingle file
Slack to Teams Expert System
A routed expert system with 100+ micro-expert files for migrating Slack bots to Teams and building cross-platform bots.
Parent skill: For ATK CLI setup and routing, see ../SKILL.md. For local testing, see ../test-playground/test-playground.md or ../test-teams/test-teams.md. For cloud deploy, see ../provision-deploy/provision-deploy.md. For troubleshooting, see ../troubleshoot/troubleshoot.md.
When to Use
Building a new Slack bot, Teams bot, or dual-platform bot
Adding Teams support to an existing Slack bot (or vice versa)
Migrating a bot between platforms
Deploying a bot to Azure or AWS
Configuring AI model providers for a bot
Converting UI between Block Kit and Adaptive Cards
Bridging identity, events, files, or transport between platforms
Making a Teams bot project compatible with Microsoft Agents Toolkit (m365agents.yml, env/, appPackage placeholders)
Procedure
Step 1: Determine project type
Assess whether the developer has an existing codebase or is starting fresh.
Converts VitePress/GFM wiki markdown to Azure DevOps Wiki-compatible format. Generates a Node.js build script that transforms Mermaid syntax, strips front matter, fixes links, and outputs ADO-compatible copies to dist/ado-wiki/.