template-validation

Validate `template.json` files for custom `dotnet new` templates.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill template-validation-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template-validation
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-template-engine/skills/template-validation
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill template-validation-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for a reliable mechanism to validate the correctness of custom dotnet new templates before they are published, thereby preventing issues that could lead to broken projects or silent failures.

Core Features & Use Cases

  • Template Validation: Inspects template.json files for common errors and issues.
  • Error Detection: Identifies missing fields, parameter bugs, shortName conflicts, and constraint problems.
  • Use Case: Before packaging and publishing a custom template, use this Skill to diagnose why a template doesn't appear after installation or to review parameter definitions for type mismatches and missing defaults.

Quick Start

Validate the template located at '/path/to/template.json' using the template-validation skill.

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 custom dotnet new template before publishing?

To validate a dotnet new template before publishing, inspect the template.json file to detect missing fields, parameter bugs, shortName conflicts, and constraint problems that cause silent failures during project generation.

Why does my dotnet new template not appear after installation?

A dotnet new template might not appear after installation due to authoring mistakes in template.json, such as shortName conflicts or missing fields. Validating the file structure helps diagnose and resolve these execution issues.

What common errors should I check for in a template.json file?

When checking a template.json file, look for common errors including missing fields, parameter type mismatches, missing default values, shortName conflicts, and constraint problems that prevent correct template execution.

Can I check my dotnet template for parameter bugs before packaging?

Yes, you can check dotnet templates for parameter bugs before packaging by reviewing parameter definitions in template.json to identify type mismatches, missing defaults, and constraint issues that lead to broken project generation.

Does template validation work with dotnet custom templates?

Template validation is designed specifically for dotnet custom templates, inspecting the template.json configuration to ensure correctness and prevent issues with template execution before you publish your project.

What are the limitations of validating template.json files manually?

Validating template.json files manually risks overlooking subtle constraint problems and shortName conflicts; automated validation detects these specific authoring mistakes to ensure template correctness before publishing.