Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dotnet/template-discovery
Helps find, inspect, and compare (at a high level) .NET project templates. Resolves natural-language project descriptions to ranked template matches with pre-filled parameters. USE FOR: finding the right dotnet new template for a task, inspecting a template's parameters and constraints, understanding what a template produces before creating a project, resolving intent like "web API with auth" to concrete template + parameters. DO NOT USE FOR: actually creating projects (use template-instantiatio
Passed 3 of 9 test cases with the skill, and 4 of 9 without it.
and 1 more in the full report
4 fixed4 passed either way9 still failing7 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am searching for legacy or traditional Windows Forms C# application templates. What is the CLI short name to inspect its options and defaults?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends the winforms template short name. | Passed | Passed |
| Leads response formatted with **Use winforms** prior to supporting details. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill helps an agent find, inspect, and select the right dotnet new template for a given task using dotnet new CLI commands for search, listing, and parameter inspection.
template-instantiation skilltemplate-authoring skilltemplate-comparison skilltemplate-smart-defaults skilldotnet-msbuild pluginRecommendation requests: answer first, confirm second. Inspection requests: inspect first. For a general "which template?" question, start from the Step 1 mappings so a transient CLI failure cannot leave the user without an answer. When the user explicitly asks what is installed, requests exact options/defaults, or asks for dry-run output, run the relevant
dotnet newcommand before writing the final answer. Never end a turn on adotnet newcall or a "let me confirm..." teaser.
Inspection requests require inspection. If the user asks for installed choices, exact parameters/defaults, compatibility constraints, or the exact dry-run file list, run the corresponding
dotnet newcommand. Do not replace observed data with remembered flags. Report a flag only when the current template's--helpoutput contains it.
| Input | Required | Description |
|---|---|---|
| User intent or keywords | Yes | Natural-language description or keywords (e.g., "web API", "console app", "MAUI") |
| Language preference | No | C#, F#, or VB — defaults to C# |
| Framework preference | No | Target framework (e.g., net10.0, net9.0) |
test cases passed, vs 4 / 9 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.