Applies cross-parameter default rules when creating .NET projects with dotnet new, filling gaps consistently without overriding values the user set explicitly. USE FOR: choosing which target framework to pair with native AOT, deciding whether to keep HTTPS when authentication is enabled, recognizing that controllers and minimal-API flags are mutually exclusive, filling unset related parameters during project creation, explaining why a default was applied and ensuring an explicit user value is ne
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 9/1/2026
What it changes
Passed 21 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill95%
Checks it passed that the model alone missed
The CLI command includes --dry-run.
The table assigns net10.0 to --framework.
The CLI command includes --framework net10.0.
and 13 more in the full report
16 fixed5 passed either way0 still failing1 broke
Pass-rate lift
+68 pp
Tokens
+131%
Agent turns
0%
Response time
+12%
Model gemini-3.6-flashMeasured 9/1/2026v221 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Give me the exact single dotnet new webapi command for --auth Individual containing only my explicitly requested choices without adding arbitrary project names.
What was checked, without and with the skill
Checked
Without skill
With skill
The CLI command omits the --name parameter.
Passed
Passed
The table marks the auth row with Source set to user.
Missed
Passed
case-14 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md102 linessingle file
Template Smart Defaults
This skill helps an agent fill in cross-parameter defaults when creating a dotnet new
project. The rules below are guidance heuristics that keep related parameters consistent —
they only fill gaps and never override a value the user set explicitly.
When to Use
The user asks to create a project but leaves related parameters unspecified
A parameter the user chose implies a sensible value for another parameter
You need to explain why a particular default was selected
When Not to Use
User wants to actually create the project — route to template-instantiation
User wants to find or compare templates — route to template-discovery or template-comparison
User wants to author or validate a custom template — route to template-authoring or template-validation
Inputs
Input
Required
Description
Template short name
Yes
The template the project will be created from (e.g., webapi)
Parameters already chosen
Yes
The parameter values the user has explicitly set
Available choices
Recommended
Parameter names/choices from dotnet new <template> --help
Workflow
Gather the parameters the user has explicitly set.
Apply each rule below only where the corresponding parameter is unset — never override a value the user set explicitly.
Confirm the chosen parameter names and choices against dotnet new <template> --help
whenever the user asks for an exact command. This inspection does not create files and is
worthwhile even for advice-only requests. Skip it only for a conceptual explanation that
does not claim exact option names.
Emit the two required outputs (see below) — this is what makes the skill decisive rather than inert.
For advice-only prompts that say "don't create files", make the displayed command safe to run
by appending --dry-run. If a scenario needs a named example and the user omitted the name,
choose a short descriptive sample name and mark it Source = rule. Do not add a name when the
user asked for a command containing only explicitly requested choices or when the template can