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.
New Project Flow
1a: Platform selection
Ask the developer which platform(s) to support:
- Slack + Teams (dual-platform)
- Slack only
- Teams only
1b: Load the expert system
- Read experts/index.md — the root router.
- Execute the pre-task interview defined in that file.
- Route based on platform choice:
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.
- Write a
PLAN.md in the target project root with platform, features, experts loaded.
1d: Implementation
Follow the advisor's or domain router's output. Implement feature by feature:
- Pick the next feature from the prioritized list.
- Load the expert(s) specified for that feature.
- Implement using the expert's patterns and rules.
- Verify against the expert's pitfalls section.
Existing Project Flow
2a: Analyze the project
Run these four sub-analyses in parallel:
Detect language — Scan for package.json+tsconfig.json (TypeScript), pom.xml/build.gradle (Java), *.csproj/*.sln (C#), go.mod (Go), requirements.txt/pyproject.toml (Python), Gemfile (Ruby), Cargo.toml (Rust).
Detect current platform — Scan dependencies for SDK indicators:
- Slack:
@slack/bolt, @slack/web-api, slack_bolt, app.message, app.command, ack()
- Teams:
@microsoft/teams-ai, botbuilder, TeamsActivityHandler, app.turn, Adaptive Cards
Detect features — Scan for slash commands, Block Kit/Adaptive Cards, action handlers, OAuth, file upload/download, scheduling, threading, AI/LLM calls, proactive messages.
Detect architecture — Scan for web framework (Express, Fastify, etc.), hosting target (Azure, AWS, Docker), cloud provider, architecture pattern (single bot, dual-bot, monolith).
2b: Language gate
Classify the detected language into SDK tiers:
2c: Expert coverage gap analysis
- Read experts/analyzer.md.
- Execute the analyzer workflow: scan manifests, dependencies, source files.
- Cross-reference detected tech against existing experts.
- Present gap analysis — covered vs uncovered technologies.
2d: Build missing experts (if needed)
- Read experts/builder.md.
- For each gap: analyze project usage → read package source → draft expert → validate → wire into routing.
- Use experts/_expert-ts.md as the template.
2e: Load the expert system
- Read experts/index.md — the root router.
- Execute the pre-task interview, pre-filling with analysis results from 2a.
- Route based on detected platform and task intent:
- Has Slack, wants Teams → Bridge domain
- Has Teams, wants Slack → Bridge domain
- Has both → Route by task (bridge refinement, deploy, models, etc.)
- Has neither → Ask which platform(s) to target
- Load cross-platform-advisor if bridging. Feed analysis results into Phase 1.
2f: Architecture and implementation
- Read cross-platform-architecture.
- Write a
PLAN.md with analysis results, routing decisions, and feature migration order.
- Implement feature by feature using the advisor's prioritized list.
Agents Toolkit Compatibility
For ATK-compatible project structure (m365agents.yml, env/ files, appPackage), see the parent skill:
For Teams manifest schema and packaging, see runtime.manifest-ts.
Error Recovery
If the expert system fails to cover a topic:
- Read experts/fallback.md.
- Phase 1: Re-scan all domain routers for missed experts.
- Phase 2: Web-search for remaining knowledge gaps.
- Consider creating a new expert using experts/builder.md.
Expert Domains
| Domain |
Index |
Description |
| Slack |
experts/slack/index.md |
Bolt framework, events, OAuth, commands, UI, CLI |
| Teams |
experts/teams/index.md |
Teams AI SDK, Adaptive Cards, Graph, MCP, A2A, deploy |
| Bridge |
experts/bridge/index.md |
27 cross-platform conversion experts (the core differentiator) |
| Deploy |
experts/deploy/index.md |
Azure & AWS deployment walkthroughs |
| Models |
experts/models/index.md |
AI model providers (OpenAI, Anthropic, Bedrock, etc.) |
| Convert |
experts/convert/index.md |
Language conversion to TypeScript |
| Security |
experts/security/index.md |
Input validation, secrets management |
Platform Comparison Docs
Reference guides for side-by-side platform comparison:
1---2name: slack-to-teams3description: "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)."4metadata:5 source: https://skillmd.com/skills/microsoft/slack-to-teams6---78# Slack to Teams Expert System910A routed expert system with 100+ micro-expert files for migrating Slack bots to Teams and building cross-platform bots.1112> **Parent skill:** For ATK CLI setup and routing, see [../SKILL.md](../SKILL.md). For local testing, see [../test-playground/test-playground.md](../test-playground/test-playground.md) or [../test-teams/test-teams.md](../test-teams/test-teams.md). For cloud deploy, see [../provision-deploy/provision-deploy.md](../provision-deploy/provision-deploy.md). For troubleshooting, see [../troubleshoot/troubleshoot.md](../troubleshoot/troubleshoot.md).1314## When to Use1516- Building a new Slack bot, Teams bot, or dual-platform bot17- Adding Teams support to an existing Slack bot (or vice versa)18- Migrating a bot between platforms19- Deploying a bot to Azure or AWS20- Configuring AI model providers for a bot21- Converting UI between Block Kit and Adaptive Cards22- Bridging identity, events, files, or transport between platforms23- Making a Teams bot project compatible with Microsoft Agents Toolkit (m365agents.yml, env/, appPackage placeholders)2425## Procedure2627### Step 1: Determine project type2829Assess whether the developer has an existing codebase or is starting fresh.3031- **New project** → go to [New Project Flow](#new-project-flow)32- **Existing project** → go to [Existing Project Flow](#existing-project-flow)3334---3536### New Project Flow3738#### 1a: Platform selection3940Ask the developer which platform(s) to support:41- Slack + Teams (dual-platform)42- Slack only43- Teams only4445#### 1b: Load the expert system46471. Read [experts/index.md](../experts/index.md) — the root router.482. Execute the **pre-task interview** defined in that file.493. Route based on platform choice:50 - **Slack + Teams** → Read [experts/bridge/index.md](../experts/bridge/index.md). Load [cross-platform-advisor](../experts/bridge/cross-platform-advisor-ts.md).51 - **Slack only** → Read [experts/slack/index.md](../experts/slack/index.md).52 - **Teams only** → Read [experts/teams/index.md](../experts/teams/index.md).5354#### 1c: Architecture setup55561. Read [cross-platform-architecture](../experts/bridge/cross-platform-architecture-ts.md) (even for single-platform — establishes patterns for adding a second platform later).572. Let the domain router and advisor take over.583. Write a `PLAN.md` in the target project root with platform, features, experts loaded.5960#### 1d: Implementation6162Follow the advisor's or domain router's output. Implement feature by feature:631. Pick the next feature from the prioritized list.642. Load the expert(s) specified for that feature.653. Implement using the expert's patterns and rules.664. Verify against the expert's pitfalls section.6768---6970### Existing Project Flow7172#### 2a: Analyze the project7374Run these four sub-analyses **in parallel**:7576**Detect language** — Scan for `package.json`+`tsconfig.json` (TypeScript), `pom.xml`/`build.gradle` (Java), `*.csproj`/`*.sln` (C#), `go.mod` (Go), `requirements.txt`/`pyproject.toml` (Python), `Gemfile` (Ruby), `Cargo.toml` (Rust).7778**Detect current platform** — Scan dependencies for SDK indicators:79- Slack: `@slack/bolt`, `@slack/web-api`, `slack_bolt`, `app.message`, `app.command`, `ack()`80- Teams: `@microsoft/teams-ai`, `botbuilder`, `TeamsActivityHandler`, `app.turn`, Adaptive Cards8182**Detect features** — Scan for slash commands, Block Kit/Adaptive Cards, action handlers, OAuth, file upload/download, scheduling, threading, AI/LLM calls, proactive messages.8384**Detect architecture** — Scan for web framework (Express, Fastify, etc.), hosting target (Azure, AWS, Docker), cloud provider, architecture pattern (single bot, dual-bot, monolith).8586#### 2b: Language gate8788Classify the detected language into SDK tiers:8990| Tier | Languages | Guidance |91|---|---|---|92| **1: Full SDK** | TypeScript / JavaScript | Full expert system available |93| **2: Adapt** | Python | Both SDKs exist — adapt TS patterns. Load [bolt-python](../experts/slack/bolt-python.md), [teams-python](../experts/teams/teams-python.md), [python-cross-platform](../experts/bridge/python-cross-platform.md) |94| **3: Split SDK** | Java, C# | One platform has SDK, other needs REST. Load [bolt-java](../experts/slack/bolt-java.md) or [teams-dotnet](../experts/teams/teams-dotnet.md) + [rest-only](../experts/bridge/rest-only-integration-ts.md) |95| **4: No SDK** | Go, Ruby, Rust | REST-only for both. Load [rest-only](../experts/bridge/rest-only-integration-ts.md) |9697#### 2c: Expert coverage gap analysis98991. Read [experts/analyzer.md](../experts/analyzer.md).1002. Execute the analyzer workflow: scan manifests, dependencies, source files.1013. Cross-reference detected tech against existing experts.1024. Present gap analysis — covered vs uncovered technologies.103104#### 2d: Build missing experts (if needed)1051061. Read [experts/builder.md](../experts/builder.md).1072. For each gap: analyze project usage → read package source → draft expert → validate → wire into routing.1083. Use [experts/_expert-ts.md](../experts/_expert-ts.md) as the template.109110#### 2e: Load the expert system1111121. Read [experts/index.md](../experts/index.md) — the root router.1132. Execute the pre-task interview, pre-filling with analysis results from 2a.1143. Route based on detected platform and task intent:115 - Has Slack, wants Teams → **Bridge** domain116 - Has Teams, wants Slack → **Bridge** domain117 - Has both → Route by task (bridge refinement, deploy, models, etc.)118 - Has neither → Ask which platform(s) to target1194. Load [cross-platform-advisor](../experts/bridge/cross-platform-advisor-ts.md) if bridging. Feed analysis results into Phase 1.120121#### 2f: Architecture and implementation1221231. Read [cross-platform-architecture](../experts/bridge/cross-platform-architecture-ts.md).1242. Write a `PLAN.md` with analysis results, routing decisions, and feature migration order.1253. Implement feature by feature using the advisor's prioritized list.126127## Agents Toolkit Compatibility128129For ATK-compatible project structure (m365agents.yml, env/ files, appPackage), see the parent skill:130- **[Parent SKILL.md](../SKILL.md)** — ATK CLI setup, sub-skill routing, workflow chains131- **[manifest-and-yaml.md](../toolkit/manifest-and-yaml.md)** — Project files, YAML config, env vars, .localConfigs flow132- **[commands.md](../toolkit/commands.md)** — Package, validate, share, collaborate, environment management133- **[templates.md](../toolkit/templates.md)** — All templates with language support134135For Teams manifest schema and packaging, see [runtime.manifest-ts](../experts/teams/runtime.manifest-ts.md).136137## Error Recovery138139If the expert system fails to cover a topic:1401. Read [experts/fallback.md](../experts/fallback.md).1412. Phase 1: Re-scan all domain routers for missed experts.1423. Phase 2: Web-search for remaining knowledge gaps.1434. Consider creating a new expert using [experts/builder.md](../experts/builder.md).144145## Expert Domains146147| Domain | Index | Description |148|---|---|---|149| Slack | [experts/slack/index.md](../experts/slack/index.md) | Bolt framework, events, OAuth, commands, UI, CLI |150| Teams | [experts/teams/index.md](../experts/teams/index.md) | Teams AI SDK, Adaptive Cards, Graph, MCP, A2A, deploy |151| Bridge | [experts/bridge/index.md](../experts/bridge/index.md) | 27 cross-platform conversion experts (the core differentiator) |152| Deploy | [experts/deploy/index.md](../experts/deploy/index.md) | Azure & AWS deployment walkthroughs |153| Models | [experts/models/index.md](../experts/models/index.md) | AI model providers (OpenAI, Anthropic, Bedrock, etc.) |154| Convert | [experts/convert/index.md](../experts/convert/index.md) | Language conversion to TypeScript |155| Security | [experts/security/index.md](../experts/security/index.md) | Input validation, secrets management |156157## Platform Comparison Docs158159Reference guides for side-by-side platform comparison:160161- [UI Components](../docs/ui-components.md) — Block Kit vs Adaptive Cards162- [Messaging & Commands](../docs/messaging-and-commands.md)163- [Identity & Auth](../docs/identity-and-auth.md)164- [Interactive Responses](../docs/interactive-responses.md)165- [Files & Links](../docs/files-and-links.md)166- [Middleware & Handlers](../docs/middleware-and-handlers.md)167- [Infrastructure](../docs/infrastructure.md)168- [Advanced Features](../docs/advanced-features.md)169- [Feature Gaps](../docs/feature-gaps.md)170- [Workflow Scenarios](../docs/workflows.md) — Message-native workflow patterns (triggers, state, logic, AI, visibility) for Teams bots