template-authoring

Generate and validate dotnet new templates from existing .csproj projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the process of creating and validating custom dotnet new templates, making it easier to develop and distribute reusable templates.

Core Features & Use Cases

  • Template Creation: Guides the generation of templates from existing projects.
  • Template Validation: Checks template.json files for schema compliance and parameter issues.
  • Bootstrapping: Assists in setting up .template.config/template.json with correct identity and parameters.
  • Packaging: Helps package templates into NuGet packages for distribution.
  • Use Case: A developer wants to create a new template from an existing .csproj file, validate the template.json, and package it for use in the dotnet ecosystem.

Quick Start

Use the template-authoring skill to create a new template from your project 'MyProject.csproj' and validate the 'MyTemplate.template.json'.

Frequently Asked Questions about template-authoring

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

FAQPage Schema
How do I create a dotnet new template from an existing .csproj file?

Validating a template.json file involves checking for schema compliance and parameter issues to ensure your custom template functions correctly. This validation step prevents runtime errors when users generate new projects from your packaged template.

What's the best way to package custom dotnet templates for distribution?

Packaging custom dotnet templates is best achieved by bundling the configured template files into a NuGet package. This allows other developers to easily install and distribute your reusable templates across the dotnet ecosystem using standard CLI commands.

Do I need the .NET SDK and template.json schema knowledge to author custom templates?

Yes, authoring custom templates requires the .NET SDK installed and a working knowledge of the template.json schema. Understanding the schema is essential for correctly defining parameters, identity, and boilerplate configurations during the bootstrapping process.

Why is my dotnet new template not working after packaging it into a NuGet package?

If your dotnet new template is not working after packaging, it likely contains a template.json schema violation or parameter misconfiguration. You must validate the template.json file for schema compliance and parameter issues before distributing the package.