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 validating custom templates (use template-authoring and template-validation), general single-template discov
npx skills add dotnet/skills --skill template-comparison --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Template Comparison 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. ## When to Use - User is deciding between similar templates (e.g., `webapi` vs `webapp`, `blazor` vs `blazorwasm`) - User asks "which template should I use for X?" - User wants to understand how two or more templates differ before creating a project ## When Not to Use - User wants to create a project — route to `template-instantiation` - User wants to author or validate a custom template — route to `template-authoring` or `template-validation` - User just needs to find or inspect a single template — route to `template-discovery` ## Inputs | 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) | ## Workflow ### Step 1: Inspect each template Run `dotnet new <template> --help` for each template being compared to collect its parameters (names, types, defaults
- When to Use
- When Not to Use
- Inputs
- Workflow
- Step 1: Inspect each template
- Step 2: Build the comparison table
- Step 3: Recommend
- Decision shortcuts for common pairs
- Validation
- Common Pitfalls
- More Info
dotnet new webapi --help dotnet new webapp --help
What does the template-comparison skill do?
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 validating custom templates (use template-authoring and template-validation), general single-template discov
How do I install it?
Run `npx skills add dotnet/skills --skill template-comparison --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dotnet/skills, a repository with 4,927 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.