Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dotnet/template-comparison
Compares two or more dotnet new templates side by side to help users choose between them based on parameters, feature support, frameworks, and classifications. USE FOR: deciding between similar templates (webapi vs webapp, blazor vs blazorwasm, console vs worker), producing a side-by-side comparison of parameters and feature support, understanding how templates differ before creating a project. DO NOT USE FOR: creating a project from a template (use template-instantiation), authoring or validati
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 5 comparable cases; this report requires 8.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
When creating a side-by-side comparison matrix for `webapi` and `webapp`, what row specifies the official categories advertised by each template?
| Checked | Without skill | With skill |
|---|---|---|
| Includes a Classifications row in the comparison table | Missed | Passed |
| Cites categories advertised by the templates | Passed | Passed |
The instructions your model reads when the skill loads.
This skill helps an agent compare 2+ dotnet new templates side by side so the user can
pick the right one. It inspects each template's parameters and feature support and renders
a comparison table.
webapi vs webapp, blazor vs blazorwasm)template-instantiationtemplate-authoring or template-validationtemplate-discovery| Input | Required | Description |
|---|---|---|
| Template short names | Yes | Two or more template short names to compare (e.g., webapi, webapp) |
| Comparison focus | No | Optional aspect to emphasize (auth, AOT, frameworks, interactivity) |
Evidence contract: a side-by-side table is useful only when every option claim is
grounded in the currently installed templates. Run each --help command sequentially,
capture the same requested dimensions for each template, and label an unavailable option
as Not exposed rather than guessing or borrowing a flag from another template.
Decision contract: optimize the comparison for the user's stated decision, not table
size. Cover every requested dimension, omit unrelated option rows, give a scenario-specific
reason, and include one safe --dry-run command for the recommended starting point when it
would make the recommendation actionable.
Run dotnet new <template> --help for each template being compared to collect its
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.