sdk-style-conversion Skill
Converts legacy .NET projects to SDK-style project format. Use when user wants to convert to SDK-style, modernize project files, or migrate from legacy csproj format. Does not change target frameworks. Published by microsoft in upgrade-agent-plugins.
Decision snapshot
Is this a fit?
Developers using upgrade-agent-plugins, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is sdk-style-conversion Skill?
Converts legacy .NET projects to SDK-style project format. Use when user wants to convert to SDK-style, modernize project files, or migrate from legacy csproj format. Does not change target frameworks. Published by microsoft in upgrade-agent-plugins. 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 upgrade-agent-plugins
Declared skill metadata
- Source file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/sdk-style-conversion/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 sdk-style-conversion Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/sdk-style-conversion/SKILL.md
What it does
Converts legacy .NET projects to SDK-style project format. Use when user wants to convert to SDK-style, modernize project files, or migrate from legacy csproj format. Does not change target frameworks.
Skill instructions
SDK-style Project Conversion 1. Assessment Scan the solution to identify which projects need conversion and what complications to expect. Capture findings in assessment.md. How to Identify Non-SDK-Style Projects A project is non-SDK-style if it has any of: - No Sdk attribute on the <Project element - Explicit file includes (<Compile Include="..." for every source file) - packages.config file in the project directory - <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" / or similar explicit tool imports Patterns to Identify For each non-SDK-style project, record: | Pattern | What to Record | |---------|---------------| | packages.config | Present? — must be migrated to PackageReference | | Explicit file includes (Compile, Content, None, EmbeddedResource) | Count — SDK-style uses globbing, these become implicit | | Custom Import elements | Which targets are imported — may need preservation | | AssemblyInfo.cs with assembly attributes | SDK-style auto-generates these — potenti
Verified compatibility and discovery
Frequently asked questions
What is sdk-style-conversion?
sdk-style-conversion is a open-source AI agent skill with Copy skill directory. Converts legacy .NET projects to SDK-style project format. Use when user wants to convert to SDK-style, modernize project files, or migrate from legacy csproj format.
Who is sdk-style-conversion best for?
sdk-style-conversion is best for reusing agent instructions, scripts, and references.
How do I install sdk-style-conversion?
Install or run sdk-style-conversion using Copy skill directory. Check sdk-style-conversion for the latest setup command.
Is sdk-style-conversion actively maintained?
sdk-style-conversion 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.
