SKILL.md still tells users the tool is unpublished and to build it from source, and two of its instructions don't work on .NET 10.
1. The tool is on NuGet; the skill says it isn't
SKILL.md Prerequisites:
The tool is not yet published to NuGet. Install from source:
git clone <repo-url> && cd crap4dotnet
dotnet pack src/Crap4DotNet.Cli -o ./nupkg
dotnet tool install -g Crap4DotNet --add-source ./nupkg
Crap4DotNet has been on nuget.org since March (0.1.0 and 0.1.1 published). Anyone following the skill builds from source for no reason — and <repo-url> is a literal placeholder, so the first command fails as written.
Should be:
dotnet tool install -g Crap4DotNet
2. --run-tests is broken on .NET 10
--run-tests shells dotnet test --collect:"XPlat Code Coverage". That's the VSTest data collector, and the .NET 10 SDK refuses the VSTest path for test projects running on Microsoft.Testing.Platform — which is the default there, and mandatory for xUnit v3.
On that stack --coverage <cobertura-path> is the only mode that works. Worth either fixing the invocation or documenting the limitation in the skill.
3. Roll-forward: the tool won't launch on a .NET 10-only machine
Directory.Build.props pins net8.0 with no <RollForward>, so on a machine with only the .NET 10 runtime the tool fails to start unless installed with --allow-roll-forward (or DOTNET_ROLL_FORWARD=Major).
SKILL.md's compatibility field claims "Requires .NET 8.0+ SDK", which reads as though .NET 10 is fine. Either set <RollForward>Major</RollForward>, or say so in the install instructions.
Why this matters now
The skill is consumed as-is — the copy installed at ~/.claude/skills/crap/SKILL.md is byte-identical to this repo's — so the stale instructions reach users directly. It's also about to be recommended as the complexity gate for a new .NET 10 service, where items 2 and 3 both bite.
SKILL.mdstill tells users the tool is unpublished and to build it from source, and two of its instructions don't work on .NET 10.1. The tool is on NuGet; the skill says it isn't
SKILL.mdPrerequisites:Crap4DotNethas been on nuget.org since March (0.1.0 and 0.1.1 published). Anyone following the skill builds from source for no reason — and<repo-url>is a literal placeholder, so the first command fails as written.Should be:
2.
--run-testsis broken on .NET 10--run-testsshellsdotnet test --collect:"XPlat Code Coverage". That's the VSTest data collector, and the .NET 10 SDK refuses the VSTest path for test projects running on Microsoft.Testing.Platform — which is the default there, and mandatory for xUnit v3.On that stack
--coverage <cobertura-path>is the only mode that works. Worth either fixing the invocation or documenting the limitation in the skill.3. Roll-forward: the tool won't launch on a .NET 10-only machine
Directory.Build.propspinsnet8.0with no<RollForward>, so on a machine with only the .NET 10 runtime the tool fails to start unless installed with--allow-roll-forward(orDOTNET_ROLL_FORWARD=Major).SKILL.md'scompatibilityfield claims "Requires .NET 8.0+ SDK", which reads as though .NET 10 is fine. Either set<RollForward>Major</RollForward>, or say so in the install instructions.Why this matters now
The skill is consumed as-is — the copy installed at
~/.claude/skills/crap/SKILL.mdis byte-identical to this repo's — so the stale instructions reach users directly. It's also about to be recommended as the complexity gate for a new .NET 10 service, where items 2 and 3 both bite.