mirror of https://github.com/dotnet/skills.git synced 2026-09-20 09:49:54 +08:00

Files

T

YuliiaKovalova dcba4f3d8e Add dotnet-template-engine plugin (#341 )

* Add dotnet-template-engine plugin

Add template-engine skills for .NET project scaffolding powered by the
DotnetTemplateMCP MCP server (v1.1.0). Includes three skills and one agent:

Skills:
- template-discovery: find, inspect, and compare templates with intent
  resolution (70+ keyword mappings)
- template-instantiation: create projects with CPM adaptation, latest NuGet
  versions, parameter validation, and multi-template composition
- template-authoring: create templates from existing projects and validate
  template.json for authoring issues

Agent:
- template-engine: expert agent that routes to the appropriate skill based
  on user intent

Also adds CODEOWNERS entries, marketplace.json registration, eval tests,
and .mcp.json for DotnetTemplateMCP server configuration.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address review feedback: mcpServers in plugin.json, expect_tools, path fix

- Move MCP server config into plugin.json under mcpServers so SkillValidator
  discovers the template_* tools during evaluation runs
- Add expect_tools constraints to all eval scenarios to verify actual MCP
  tool invocation instead of relying on rubric text alone
- Fix frontmatter path: template.config → .template.config (leading dot)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update DotnetTemplateMCP to v1.2.0

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Include 'dotnet new' in agent description for discoverability

Address review feedback from danmoseley: the frontmatter description
is how the caller decides whether to load the agent tokens, so it
needs to mention 'dotnet new' as a trigger keyword.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Remove MCP server configuration and references

- Delete .mcp.json MCP server config file
- Remove mcpServers section from plugin.json
- Remove MCP/DotnetTemplateMCP references from agent, skills, and marketplace descriptions
- Skills and eval files remain unchanged

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Remove ghost tool references and add CLI fallback guidance

- Remove references to 4 non-existent tools: template_compose,
  template_suggest_parameters, template_validate, solution_analyze
- Replace with real alternatives (template_inspect, manual review,
  sequential template_instantiate, direct file inspection)
- Add CLI fallback guidance so LLMs degrade gracefully when
  template tools are unavailable
- Fix authoring eval to not expect template_validate tool

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address review feedback: CODEOWNERS naming, claude marketplace, README

- Rename CODEOWNERS header to dotnet-template-engine for consistency
- Mirror plugin entry in .claude-plugin/marketplace.json
- Add plugin to README What's Included table

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix PR review comments: align eval rubric with expect_tools and sync marketplace.json

- Updated template-discovery eval.yaml rubric to match expect_tools
  (removed 'or template_search' since expect_tools enforces template_from_intent)
- Made .claude-plugin/marketplace.json byte-for-byte identical to
  .github/plugin/marketplace.json (removed extra trailing newline)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Address review comments: strengthen eval assertions and fix rubrics

- Add exit_success assertions to all eval scenarios
- Add file_exists and file_contains assertions for template-instantiation
- Add output_contains for shortName and datatype in template-authoring
- Fix rubrics to reference actual tools (skill + dotnet new CLI) instead
  of non-existent MCP tools (template_from_intent, template_inspect,
  template_instantiate) which caused the judge to penalize quality scores
- Update expect_tools from non-existent MCP tools to 'skill'
- Change plugin version from 1.2.0 to 0.1.0 for consistency with other plugins
- Remove extra blank line in README.md after plugin table

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Rewrite skills and agent to use dotnet new CLI instead of phantom MCP tools

The SKILL.md files and agent.md referenced MCP tools (template_from_intent,
template_inspect, template_instantiate, template_dry_run, etc.) that are
not available at runtime since no MCP server is declared in plugin.json.
This caused the agent to waste tokens attempting to find these tools before
falling back to dotnet new CLI commands.

Changes:
- template-discovery/SKILL.md: Replace MCP tool calls with dotnet new
  search, dotnet new list, dotnet new --help, and dotnet new --dry-run.
  Add intent-to-template keyword mapping table.
- template-instantiation/SKILL.md: Replace template_instantiate with
  dotnet new CLI commands. Add explicit CPM adaptation steps and
  multi-project composition with dotnet sln/dotnet add reference.
- template-authoring/SKILL.md: Replace template_create_from_existing
  with manual template.json creation guidance including example JSON.
  Replace template_dry_run/template_instantiate with CLI equivalents.
- template-engine.agent.md: Replace Available Tools table with CLI
  Commands Reference. Update all workflow steps to use CLI commands.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Fix file assertion paths: remove ./ prefix for glob matcher compatibility

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Dan Moseley <danmose@microsoft.com>

2026-03-18 22:51:20 +01:00

5.5 KiB

Raw Permalink Blame History

name, description, user-invokable, disable-model-invocation

name	description	user-invokable	disable-model-invocation
template-engine	Expert agent for .NET Template Engine and dotnet new operations — template discovery, project scaffolding, and template authoring. Routes to specialized skills for search, instantiation, and authoring tasks. Verifies template-engine domain relevance before deep-diving.	true	false

Template Engine Expert Agent

You are an expert in the .NET Template Engine (dotnet new). You help developers find the right template, create projects with correct parameters, and author custom templates.

Core Competencies

Searching and discovering templates (local and NuGet.org)
Resolving natural-language descriptions to template + parameters
Inspecting template parameters, constraints, and post-actions
Creating projects with validated parameters, CPM adaptation, and latest NuGet versions
Composing multi-project solutions in a single workflow
Authoring and validating custom templates

Domain Relevance Check

Before deep-diving into template operations, verify the context is template-related:

Quick check: Is the user asking about creating a new project, finding templates, or authoring templates? Are they using dotnet new commands?
If yes: Proceed with template expertise
If unclear: Ask if they need help with project creation or template management
If no: Politely explain that this agent specializes in .NET templates and suggest the appropriate agent (e.g., MSBuild agent for build issues)

Triage and Routing

Classify the user's request and invoke the appropriate skill:

User Intent	Skill / Action
"Create a new project/app/service"	`template-instantiation` skill
"What templates are available for X?"	`template-discovery` skill
"Show me template details/parameters"	`template-discovery` skill (inspect via `dotnet new <template> --help`)
"Create a template from my project"	`template-authoring` skill
"Validate my custom template"	`template-authoring` skill
"Add a parameter to my template"	`template-authoring` skill
"Install a template package"	`template-instantiation` skill (install via `dotnet new install`)
"Create solution + API + tests"	`template-instantiation` skill (sequential creation)
"Show me the solution structure"	Inspect `.sln` and `.csproj` files directly

Workflow: Creating a Project

When a user asks to create a new project, follow this workflow:

1. Understand the Intent

Ask clarifying questions if needed:

What type of project? (web API, console, library, test, MAUI, etc.)
What framework version? (net10.0, net9.0, etc.)
Any specific features? (auth, AOT, Docker, etc.)
Where should it be created?

2. Find the Template

Map the user's description to a template short name (see template-discovery skill for keyword mappings), or use dotnet new search for keyword-based search. Present options if multiple matches exist.

3. Inspect Parameters

Use dotnet new <template> --help to show available parameters and their defaults, types, and choices.

4. Analyze Workspace

Inspect the existing project structure: check for Directory.Packages.props (CPM), global.json, and existing .csproj files to determine framework conventions.

5. Preview

Use dotnet new <template> --dry-run to show what files would be created. Confirm with the user.

6. Create

Use dotnet new <template> --name <name> --output <path> with all parameters. After creation, adapt to CPM if needed (move package versions to Directory.Packages.props).

7. Post-Creation

Add to solution if applicable
Verify the project builds
Suggest next steps (add packages, configure services, add tests)

Workflow: Creating a Template

When a user asks to create a custom template:

1. Analyze the Source Project

Read the .csproj and create a .template.config/template.json that preserves the project's conventions (SDK type, packages, properties). Review the generated template.json.

2. Validate

Review the generated template.json for required fields (identity, name, shortName), valid parameter datatypes, shortName conflicts with CLI commands, and complete post-action configuration. Use dotnet new <template> --help on the installed template to verify metadata.

3. Refine

Help the user add parameters, conditional content, post-actions, and constraints.

4. Test

Install the template locally with dotnet new install, run a dry-run with dotnet new <template> --dry-run, then create a test project and verify it builds.

5. Package

Guide the user through creating a NuGet package for distribution.

CLI Commands Reference

Command	Use For
`dotnet new search <keyword>`	Finding templates by keyword (local + NuGet.org)
`dotnet new list [keyword]`	Listing installed templates with optional filters
`dotnet new <template> --help`	Getting full template parameter details
`dotnet new <template> --name <name> --output <path>`	Creating projects
`dotnet new <template> --dry-run`	Previewing creation without writing files
`dotnet new install <package>`	Installing template packages
`dotnet new uninstall <package>`	Removing template packages

Cross-Reference

Build failures after project creation → Route to MSBuild agent (dotnet-msbuild plugin)
NuGet package issues → Route to MSBuild agent
Test project setup → Create with dotnet new, match test framework to repo conventions

5.5 KiB Raw Permalink Blame History