Slack-to-Teams Migration Expert
Guides developers through Slack bot migration, Teams enablement, and cross-platform bot delivery.
The skill explicitly covers OAuth, identity, files, cloud deployment, and AI model configuration, but it does not define least privilege, user confirmation, sensitive-data handling, data-flow disclosure, rollback, or boundaries for external actions. Points are deducted for those omissions; no explicit red-line risk is shown.
The new-project and existing-project flows, language tiers, and fallback path are internally coherent. However, the procedure depends heavily on more than 100 referenced expert files not included in the supplied evidence, with no skill-specific reproducible tests or detailed abnormal-input feedback. The score remains within the static-review cap.
The audience, scenarios, and non-fit cases are relatively clear, covering Slack, Teams, bridging, deployment, and language selection. It provides no explicit Chinese-language support or mainland-China network assessment, and trigger precision still depends on the parent skill and referenced routers.
The document uses layered routing and links to parent skills, expert domains, platform comparisons, and recovery guidance. The repository supplies MIT licensing and official attribution, but the selected skill lacks concrete versioning, changelog, maintenance ownership, update-path, installation, and dependency details.
The procedure can guide project analysis, routing, PLAN.md creation, and phased implementation, so it has clear practical value. However, core guidance is distributed across referenced files absent from the evidence, and there are no representative outputs or skill-specific acceptance results. Significant manual review remains necessary, so the static-review ceiling applies.
The selected SKILL.md is auditable, and the repository includes general CI and harness tests. The supplied material does not establish that those tests cover this Slack-to-Teams skill's key paths, and provides no third-party execution evidence or corroborating reproduction, so only limited credit is justified.
- Before deployment, OAuth, file bridging, or cloud-resource actions, add permission scope, user-confirmation, sensitive-data, and rollback requirements.
- Verify that every relative link and expert file exists in the installed package, and add reproducible acceptance tests for the key Slack-to-Teams paths.
- The fallback depends on web search; provide an offline alternative and version-pinning strategy for mainland-China inaccessibility or stale information.
What it does & when to use it
This is a sub-skill of microsoft-365-agents-toolkit for building Slack, Teams, and dual-platform bots. It routes work across micro-experts covering platform migration, Block Kit and Adaptive Cards conversion, identity and OAuth bridging, deployment, and AI model configuration. For existing projects, it analyzes language, platform, features, and architecture before selecting an expert workflow. It is not intended for general web development or standalone Teams work without Slack.
It instructs the agent to scan project manifests, dependencies, and source files to detect language, current platform, bot features, and deployment architecture; classify language into SDK-support tiers; read routing, architecture, and domain expert files; interview developers about platform choices for new projects; perform coverage-gap analysis for existing projects; load experts and implement features in priority order; write a PLAN.md containing platform and routing or analysis results; and use the fallback workflow, including web search when documented knowledge gaps remain.
- A developer maintaining a Slack bot who wants to add Teams support.
- A team migrating an existing Slack bot to Teams while retaining cross-platform behavior.
- An engineer building a new bot for both Slack and Teams.
- A developer converting Slack Block Kit interfaces into Teams Adaptive Cards.
- A bot team bridging identity, OAuth, events, files, or transport between platforms.
- A developer preparing bot deployment to Azure or AWS and configuring AI model providers.
Pros & cons
- Covers concrete bot work including migration, cross-platform bridging, UI conversion, identity, deployment, and model configuration.
- Separates workflows for new and existing projects and includes language and SDK coverage analysis.
- Provides routing for Azure and AWS deployment and Microsoft Agents Toolkit compatibility.
- Structures complex implementation through expert routing and a generated PLAN.md.
- Its core knowledge is distributed across more than 100 micro-expert files whose contents are not included here.
- It is explicitly out of scope for general web development and standalone Teams projects without Slack.
- The supplied material does not identify independent tests or exact version requirements for this sub-skill.
- Some workflows depend on repository scanning, filesystem changes, web search, and potentially MCP or Agents Toolkit context.
How to install
Run npx skills add microsoft/skills in the project, then select the needed skill in the installation wizard. The README says skills are installed in the selected agent directory, such as .github/skills/ for GitHub Copilot, and can be symlinked across agents. The source does not document how to target this specific nested sub-skill directly in the wizard.
How to use
After installation, use a prompt such as “Migrate this existing Slack Bolt bot to Teams while preserving dual-platform support” or “Add Teams support to this Slack bot and convert its Block Kit UI to Adaptive Cards.” For a new project, the workflow first asks whether to support Slack, Teams, or both. For an existing project, it begins with repository analysis. Use the parent skill for standalone Teams development without Slack.
Compared to similar skills
Compared with its microsoft-365-agents-toolkit parent skill, this sub-skill focuses on Slack-to-Teams migration and cross-platform bots. ATK CLI setup, general routing, and standalone Teams development belong to the parent skill.