dotnetMicrosoft .NET platform, MIT licensed since 20164,500 installs on skills.shConvert to Cpm
Convert .NET projects and solutions (.sln.
Use Edge to load the skill convert-to-cpm from dotnet/skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the dotnet public repository. Edge did not write or edit this skill.
What it does
- Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props.
- USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects.
- Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM.
- Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report.
- DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.
Why dotnet
Open-source .NET platform organisation. Each fact links its public source.
- Open source platform
Wikipedia says .NET is free, open source under MIT, with .NET Core 1.0 released June 2016.
Wikipedia: .NET - ASP.NET Core repo
The aspnetcore repo has 38k+ GitHub stars.
GitHub repo - MAUI repo
The maui repo has 23k+ GitHub stars.
GitHub repo
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Convert to Cpm.
Related skills
Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props, and Directory.Build.rsp. USE FOR: structuring multi-project repos, centralizing build settings, i
.NET solution and project structure conventions. Covers .slnx format, Directory.Build.props, Directory.Packages.props for central package management, global usings, and naming conventions. Load this skill when setting up
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions wit
Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct
Workflow for fixing package version conflicts. Use this when `pub get` fails due to incompatible package versions.
Dependency health report for .NET solutions: outdated NuGet packages, vulnerable versions, and commercial-license traps (MediatR, MassTransit, FluentAssertions, AutoMapper) — powered by the get_nuget_packages MCP tool. I
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-17
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-17
Creator, source & licencedotnet
From the dotnet public repository. Edge did not write or edit this skill.
- Repository
- dotnet/skills
- Skill file
- View source at revision
- Revision
- 8599a06757aabf411ae28e0559063342d70386ef
- Package hash
- sha256:aab405d707afee71c0d8bf82d6f0cffed5f4666f84e15d39b0155d84d0b86ec5
- Licence
- MIT
- Description
- Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.
Quoted from the skill’s own description
Read skill files7 files
7 files, 40.3 KB at revision 8599a06757aa.
Questions about Convert to Cpm
What does Convert to Cpm do?
Convert .NET projects and solutions (.sln. Published by dotnet (dotnet/skills).
Is Convert to Cpm safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.
How do I use Convert to Cpm in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.