Localized reading guide
slack-to-teamsPurpose, usage and source
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 development without Slack (use parent skill instead).
Source retrieved:
- Source repository
- microsoft/skills
- SKILL.md
.github/plugins/microsoft-365-agents-toolkit/skills/teams-app-developer/slack-to-teams/SKILL.md- Repository stars
- 3,157
- Repository updated
- 2026-10-31
- Categories
- Agent workflows
- Last collected
License: MIT
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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 development without Slack (use parent skill instead).
How the upstream workflow works
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
Upstream passage · L12 ↗Step 1: Determine project type
Assess whether the developer has an existing codebase or is starting fresh. New project → go to New Project Flow Existing project → go to Existing Project Flow
Upstream passage · L25 ↗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.
Upstream passage · L6 ↗Requirements and setup
1c: Architecture setup
Read cross-platform-architecture (even for single-platform — establishes patterns for adding a second platform later). Let the domain router and advisor take over.
Upstream passage · L52 ↗Agents Toolkit Compatibility
For ATK-compatible project structure (m365agents.yml, env/ files, appPackage), see the parent skill: Parent SKILL.md — ATK CLI setup, sub-skill routing, workflow chains
Upstream passage · L125 ↗Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Slack to Teams Expert System
- When to Use
- Step 1: Determine project type
- 1a: Platform selection
- 1b: Load the expert system
- 1c: Architecture setup
- 1d: Implementation
- 2a: Analyze the project
- 2b: Language gate
- 2c: Expert coverage gap analysis
- 2d: Build missing experts (if needed)
- 2e: Load the expert system
- 2f: Architecture and implementation
- Agents Toolkit Compatibility
- Error Recovery
- Platform Comparison Docs
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
00d66a64919edca5bca2c673373444e36a4b5461- Source SHA-256
dfa8d4b75d5154b585ac470678d8bfee07e17af6c8bc804815f9b304763b50ba