template-validation

Validates dotnet new template.json files for correctness before publishing.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill template-validation-d1ssolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-validation
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/template-validation
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill template-validation-d1ssolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Custom dotnet new templates often fail silently after installation due to authoring mistakes like missing required fields, shortName conflicts with CLI commands, or invalid symbol definitions. This Skill systematically checks a template.json file against a comprehensive rule set so you catch errors before packaging and publishing to NuGet. ## Core Features & Use Cases - Eight-Category Validation: Checks required fields, identity format, shortName conflicts, symbol definitions, source conditions, post-actions, constraints, and tags. - Severity-Based Reporting: Organizes findings into errors, warnings, and suggestions with a summary count so you know what must be fixed versus what is optional. - Use Case: You built a custom Web API template but it does not appear in dotnet new list after installation. Point this Skill at your .template.config/template.json and it will flag issues like a shortName conflicting with a reserved CLI command or a choice parameter missing its default value. ## Quick Start Validate the template.json file in my .template.config directory and report all errors, warnings, and suggestions.

Frequently Asked Questions about template-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a dotnet new template.json file?

Provide the path to your template.json file or the template directory containing .template.config/template.json. The validation checks eight categories including required fields, identity format, shortName conflicts, symbols, sources, post-actions, constraints, and tags, then reports errors, warnings, and suggestions.

Why doesn't my custom template show up in dotnet new list?

Common causes include a shortName conflicting with reserved CLI commands like test or build, missing required fields such as identity or name, or malformed JSON. Validating the template.json against the full rule set identifies which issue prevents registration.

What shortName values conflict with dotnet CLI commands?

Reserved names include new, build, run, test, publish, restore, clean, pack, add, remove, list, nuget, tool, sln, and help. Using any of these as a shortName, case-insensitively, produces an error because the template can never be invoked.

What are common dotnet template.json authoring mistakes?

Frequent pitfalls include missing sourceName so --name does not rename output, choice parameters without a defaultValue, invalid datatype values that the engine silently ignores, computed symbols missing a value expression, and parameter prefix collisions like Auth versus AuthMode.

When should I not use template validation?

Do not use it to find existing templates, create projects from templates, or author templates from existing projects. Those tasks belong to template-discovery, template-instantiation, and template-authoring respectively. Validation only reviews an existing template.json for correctness.