bf-to-agents-sdk-dotnet-migration Skill
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK. Published by microsoft in Agents.
Decision snapshot
Is this a fit?
Developers using Agents, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is bf-to-agents-sdk-dotnet-migration Skill?
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK. Published by microsoft in Agents. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using Agents
Declared skill metadata
- Source file: agent-plugins/agents-for-net/skills/bf-to-agents-sdk-dotnet-migration/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use bf-to-agents-sdk-dotnet-migration Skill
- Use it for developers using agents.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Agents
- Skill file: agent-plugins/agents-for-net/skills/bf-to-agents-sdk-dotnet-migration/SKILL.md
What it does
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
Skill instructions
Bot Framework to Agents SDK Migration (.NET) Overview Migrates a Bot Framework SDK bot to Microsoft 365 Agents SDK using the ActivityHandler/TeamsActivityHandler compat layer — minimal code changes, original class names preserved. This skill stops at the compat layer. After completing this migration, ask the user whether to also convert to AgentApplication (see final step). Agents DotNet SDK repository: https://github.com/microsoft/agents-for-net Bot Framework DotNet SDK repository: https://github.com/microsoft/botbuilder-dotnet --- Core Rules - Retain the original bot class name. Do not rename or create a new class — renaming breaks git history. - Only change what is required for a clean migration. Do not refactor, restructure, or improve beyond what is needed to compile and run on Agents SDK. --- Package Replacements Version: Always use the latest stable (non-beta) version of Agents SDK packages by default. | Remove (Bot Framework) | Add (Agents SDK) | |------------------------|-----
Verified compatibility and discovery
Frequently asked questions
What is bf-to-agents-sdk-dotnet-migration?
bf-to-agents-sdk-dotnet-migration is a open-source AI agent skill with Copy skill directory. Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK.
Who is bf-to-agents-sdk-dotnet-migration best for?
bf-to-agents-sdk-dotnet-migration is best for reusing agent instructions, scripts, and references.
How do I install bf-to-agents-sdk-dotnet-migration?
Install or run bf-to-agents-sdk-dotnet-migration using Copy skill directory. Check bf-to-agents-sdk-dotnet-migration for the latest setup command.
Is bf-to-agents-sdk-dotnet-migration actively maintained?
bf-to-agents-sdk-dotnet-migration may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.