dotnet-version-upgrade Skill
Upgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets. Published by microsoft in upgrade-agent-plugins.
Decision snapshot
Is this a fit?
Data analysis, Writing, Research, Includes SKILL.md
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 dotnet-version-upgrade Skill?
Upgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets. 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
- Data analysis
- Writing
- Research
- Data analysis use cases
- Writing use cases
Declared skill metadata
- Source file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/dotnet-version-upgrade/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 dotnet-version-upgrade Skill
- Use it for data analysis.
- Use it for writing.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/dotnet-version-upgrade/SKILL.md
What it does
Upgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets.
Skill instructions
.NET Version Upgrade Scenario Upgrade .NET projects from their current target framework to a newer version of .NET. Current Facts <!-- Last updated: 2025-11-12 -- | Version | Status | Support Level | End of Life | |---------|--------|---------------|-------------| | .NET 10 | GA | LTS | 2028-11-14 | | .NET 9 | GA | STS | 2026-11-10 | | .NET 8 | GA | LTS | 2026-11-10 | | .NET 11 | Preview | — | 2030-11-12 (projected) | Staleness check: If the user asks about a version listed as Preview above, verify its current status using an internet search tool before answering — it may have shipped since this data was last updated. Scenario Overview Goal: Migrate one or more .NET projects to a target framework version while maintaining functionality. Workflow Stages Run these stages in order: 0. Pre-Initialization — Confirm target framework + source-control + flow parameters, then set up source control, call initializescenario, and write scenario-instructions.md. Consumed during pre-initialization b
Verified compatibility and discovery
Frequently asked questions
What is dotnet-version-upgrade?
dotnet-version-upgrade is a open-source AI agent skill with Copy skill directory. Upgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets.
Who is dotnet-version-upgrade best for?
dotnet-version-upgrade is best for reusing agent instructions, scripts, and references, data analysis workflows, writing workflows, research workflows.
How do I install dotnet-version-upgrade?
Install or run dotnet-version-upgrade using Copy skill directory. Check dotnet-version-upgrade for the latest setup command.
Is dotnet-version-upgrade actively maintained?
dotnet-version-upgrade 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.
