template-validation
Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templa
npx skills add dotnet/skills --skill template-validation --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 Validation This skill helps validate custom `dotnet new` templates for correctness before publishing. It encodes the validation rules that catch common authoring mistakes — issues that cause templates to silently fail, produce broken projects, or not appear in `dotnet new list`. ## When to Use - User asks to check or validate a template.json file - User reports "my template doesn't show up after installing" - User wants to review a template before packaging and publishing to NuGet - User encounters unexpected behavior from a custom template ## When Not to Use - User wants to find or use existing templates — route to `template-discovery` - User wants to create a project — route to `template-instantiation` - User wants to create a template from an existing project — route to `template-authoring` ## Inputs | Input | Required | Description | |-------|----------|-------------| | template.json path | Yes | Path to the template.json file or the template directory containing `.template.config/template.json` | ## Validation Rules When reviewing a template.json, check ALL of the following categories systematically. Report every finding as an error, warning, or suggestion. ### 1. R
- When to Use
- When Not to Use
- Inputs
- Validation Rules
- 1. Required Fields
- 2. Identity Format
- 3. ShortName Conflicts
- 4. Symbol Validation
- 5. Sources Validation
- 6. Post-Action Validation
- 7. Constraint Validation
- 8. Tags Validation
- Workflow
- Step 1: Locate the template.json
What does the template-validation skill do?
Validates custom dotnet new templates for correctness before publishing. Catches missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes that cause templates to fail silently. USE FOR: checking template.json files for errors before publishing or testing, diagnosing why a template doesn't appear after installation, reviewing template parameter definitions for type mismatches and missing defaults, finding shortName conflicts with dotnet CLI commands, validating post-action and constraint configuration. DO NOT USE FOR: finding or using existing templa
How do I install it?
Run `npx skills add dotnet/skills --skill template-validation --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.