[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVMBCQYHBHHPCRSWNBF18M":3,"skill-same:01M7CVMBCQYHBHHPCRSWNBF18M":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CVMBCQYHBHHPCRSWNBF18M","template-validation",null,"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 templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).","deadmade\u002Fdead-agent-skills","deadmade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F130925709?v=4","01M7CTQ65AGYR4J9K9TX0YR9V3","01M7CTQ66B4VMJFEDZP4EKKE6K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-validation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: template-validation\ndescription: >\n  Validates custom dotnet new templates for correctness before publishing.\n  Catches missing fields, parameter bugs, shortName conflicts, constraint issues,\n  and common authoring mistakes that cause templates to fail silently.\n  USE FOR: checking template.json files for errors before publishing or testing,\n  diagnosing why a template doesn't appear after installation, reviewing template\n  parameter definitions for type mismatches and missing defaults, finding shortName\n  conflicts with dotnet CLI commands, validating post-action and constraint configuration.\n  DO NOT USE FOR: finding or using existing templates (use template-discovery),\n  creating projects from templates (use template-instantiation), creating templates\n  from existing projects (use template-authoring).\nlicense: MIT\n---\n\n# Template Validation\n\nThis 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`.\n\n## When to Use\n\n- User asks to check or validate a template.json file\n- User reports \"my template doesn't show up after installing\"\n- User wants to review a template before packaging and publishing to NuGet\n- User encounters unexpected behavior from a custom template\n\n## When Not to Use\n\n- User wants to find or use existing templates — route to `template-discovery`\n- User wants to create a project — route to `template-instantiation`\n- User wants to create a template from an existing project — route to `template-authoring`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| template.json path | Yes | Path to the template.json file or the template directory containing `.template.config\u002Ftemplate.json` |\n\n## Validation Rules\n\nWhen reviewing a template.json, check ALL of the following categories systematically. Report every finding as an error, warning, or suggestion.\n\n> **Parse gate — stop on syntax errors.** Parse JSON before applying any semantic rule. If\n> parsing fails, report the parser's line and column, show only the smallest concrete syntax\n> correction, and stop. Do not invent required-field, symbol, post-action, or discoverability\n> findings from a document that did not parse. Re-parse after the correction before making any\n> semantic claim.\n>\n> The malformed-JSON final response has exactly two parts: the one-line parse verdict and a\n> corrected snippet showing the exact edit. Do not append semantic recommendations, optional\n> metadata, or a full replacement manifest.\n\n### 1. Required Fields\n\n| Field | Severity | Rule |\n|-------|----------|------|\n| `identity` | ERROR | Must be present and non-empty |\n| `name` | ERROR | Must be present and non-empty |\n| `shortName` | ERROR | Must be present and non-empty |\n| `sourceName` | WARNING | Without it, `--name` won't customize the generated project name |\n| `author` | WARNING | Improves template discoverability |\n| `description` | SUGGESTION | Helps users understand what the template creates |\n| `classifications` | SUGGESTION | Improves search and categorization (e.g., `[\"Web\", \"API\"]`) |\n| `defaultName` | SUGGESTION | Provides a fallback project name when `--name` is not specified |\n\n### 2. Identity Format\n\n- ERROR if identity contains spaces — use dots or dashes (e.g., `MyCompany.WebApi.CSharp`)\n- WARNING if identity has no namespace separator (`.` or `-`) — use reverse-DNS format\n\n### 3. ShortName Conflicts\n\nA shortName that matches a `dotnet new` subcommand conflicts, because `dotnet new \u003Cname>` is then parsed as that subcommand instead of instantiating the template. Read the reserved set for the installed SDK from the `Commands:` section of `dotnet new --help` — that is the authoritative source and avoids this rule going stale.\n\nAs of current SDKs the subcommands include (illustrative only — version-dependent, do not hardcode this list; the live `dotnet new --help` output is canonical): `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`. Note that top-level `dotnet` verbs like `build`, `run`, `test`, and `publish` do NOT conflict — `dotnet new test` does not collide with `dotnet test`.\n\n- ERROR if shortName matches any subcommand reported by `dotnet new --help` (case-insensitive)\n- WARNING if shortName is only 1 character — too short for discoverability\n- Note: shortName can be a string or an array of strings; check all values\n\n### 4. Symbol Validation\n\nFor each symbol in the `symbols` object:\n\n- ERROR if a symbol is missing the `type` field\n- For `type: \"parameter\"`:\n  - WARNING if no `datatype` specified (defaults to `string`)\n  - SUGGESTION if no `description` (improves `--help` output)\n  - If `datatype: \"choice\"`:\n    - ERROR if no `choices` defined\n    - ERROR if `choices` is empty\n    - ERROR if `defaultValue` is not in the choices list\n    - WARNING if optional (not `isRequired`) and no `defaultValue` — users get unexpected behavior\n  - If `datatype: \"bool\"`:\n    - ERROR if `defaultValue` is not a valid boolean\n  - If `datatype: \"int\"`:\n    - ERROR if `defaultValue` is not a valid integer\n  - Valid datatypes: `string`, `bool`, `choice`, `int`, `float`, `hex`, `text`\n  - ERROR if datatype is not in the valid list\n- For `type: \"computed\"`:\n  - ERROR if missing `value` expression\n- For `type: \"generated\"`:\n  - ERROR if missing `generator` field\n  - Valid generators: `casing`, `coalesce`, `constant`, `port`, `guid`, `now`, `random`, `regex`, `regexMatch`, `switch`, `join`\n\nCustom parameter help is template-specific: it appears under\n`dotnet new \u003CshortName> --help`, not the global `dotnet new --help`. Correct that premise\nwhen necessary, then explain which invalid symbol definitions prevent the parameters from\nappearing reliably.\n\nA valid choice parameter uses a non-empty choices object, for example:\n\n```json\n\"Color\": {\n  \"type\": \"parameter\",\n  \"datatype\": \"choice\",\n  \"defaultValue\": \"Blue\",\n  \"choices\": {\n    \"Blue\": { \"displayName\": \"Blue\" },\n    \"Green\": { \"displayName\": \"Green\" }\n  }\n}\n```\n\n**Parameter prefix collisions**: WARNING if any parameter name is a prefix of another parameter name (e.g., `Auth` and `AuthMode`) — this creates ambiguous parsing in expression contexts.\n\n### 5. Sources Validation\n\nFor source modifier conditions:\n- WARNING if a condition string doesn't contain parentheses around symbol names — expected format is `(symbolName)`, not bare `symbolName`\n\n### 6. Post-Action Validation\n\nFor each post-action:\n- ERROR if missing `actionId`\n- WARNING if missing `description` — this text is shown to users when the action requires manual steps\n- SUGGESTION if missing `manualInstructions` — these are shown when the action can't run automatically (e.g., in an IDE)\n\n### 7. Constraint Validation\n\nFor each constraint:\n- ERROR if missing `type` field\n- WARNING if missing `args` — most constraint types require arguments\n- For `type: \"host\"`, missing `args` is an ERROR. `args` is a required array; each entry needs `hostname`. Supported\n  built-in identifiers include `dotnetcli`, `vs`, `vs-mac`, `ide`, and\n  `dotnetcli-preview`. An optional `version` uses NuGet version\u002Frange syntax such as\n  `[10.0.100,)`. The engine matches argument keys case-insensitively, so the documented\n  `hostName` spelling is also valid. Reject unrelated fields such as `pattern` and `value`.\n- For `type: \"sdk-version\"`, `args` is a version string or array using the same syntax.\n\n### 8. Tags Validation\n\n- SUGGESTION if no `language` tag — adding `tags.language` (e.g., `\"C#\"`) improves filtering in `dotnet new list --language`\n- SUGGESTION if no `type` tag — adding `tags.type` (e.g., `\"project\"` or `\"item\"`) improves categorization\n\n## Workflow\n\n### Step 1: Locate the template.json\n\nThe file can be at:\n- Direct path: `path\u002Fto\u002Ftemplate.json`\n- In a template directory: `path\u002Fto\u002F.template.config\u002Ftemplate.json`\n- In a `.template.config` directory: `path\u002F.template.config\u002Ftemplate.json`\n\n### Step 2: Parse and validate\n\nRead the JSON. If it's malformed, report the JSON parse error with line and column.\nIf an absolute-path read fails, retry the user-supplied relative path from the working\ndirectory before concluding the file is unavailable.\n\nOnly after parsing succeeds, run all 8 validation categories above. Collect errors, warnings,\nand suggestions separately. Verify schema-sensitive claims against the installed SDK or the\ncurrent template-engine schema; do not infer a runtime failure from a field name alone.\n\n### Step 3: Report results\n\n**Lead with a one-line verdict**, then a single findings table. This decisive shape is required — do not scatter findings across prose paragraphs.\n\nVerdict header (pick one):\n- `❌ Not ready — N error(s), M warning(s)` — has errors\n- `⚠️ Publishable but N warning(s)` — no errors, has warnings\n- `✅ Ready to publish — 0 errors, 0 warnings` — no errors or warnings (optional suggestions may still apply)\n\nThen one table, ordered errors → warnings → suggestions:\n\n| Severity | Location (JSON path or `line:col`) | Issue | Fix |\n|----------|------------------------------------|-------|-----|\n| ERROR | `shortName` | `\"list\"` conflicts with a `dotnet new` subcommand | Rename to a distinctive value, e.g. `\"my-list\"` |\n| ERROR | `symbols.maxRetries.defaultValue` | `\"abc\"` is not a valid `int` | Set a numeric default, e.g. `\"3\"` |\n| WARNING | `sourceName` | Missing replacement token | Set it to the source project name |\n\n**Every ERROR and WARNING MUST include a concrete fix** — the corrected value, JSON snippet, or a specific edit instruction (e.g. \"remove the trailing comma\"), not just a restatement of the problem. A finding without an actionable fix is incomplete. This is the single biggest thing that separates a useful validation from a generic lint.\n\nClose with the total: \"N error(s), M warning(s), K suggestion(s).\"\n\nFor malformed JSON the output is intentionally smaller and has exactly two parts:\n\n`❌ Not ready — JSON parse error at line N, column M: \u003Cmessage>.`\n\n```json\n\u003Csmallest corrected fragment showing the exact edit>\n```\n\nDo not append a findings table or semantic totals until the corrected file parses.\n\n## Common Pitfalls\n\n| Pitfall | Impact |\n|---------|--------|\n| ShortName = \"list\" or \"search\" | Template can never be created — conflicts with a `dotnet new` subcommand |\n| Missing `sourceName` | `--name MyProject` doesn't rename anything in the generated files |\n| Choice parameter without `defaultValue` | Confusing user experience on optional choice params |\n| Invalid `datatype` value | Template engine ignores the symbol, causing silent failures |\n| Computed symbol without `value` | Template engine throws at instantiation time |\n| Parameter prefix collision (`Auth` vs `AuthMode`) | Ambiguous expression evaluation |\n| Source condition without parentheses | Condition may not evaluate correctly |\n| Continuing semantic validation after JSON parsing failed | Findings are speculative. Report the exact parse fix and stop. |\n| Host constraint uses scalar `args`, the invalid `dotnet-cli` host ID, or unrelated fields | Use `args: [{ \"hostname\": \"dotnetcli\", \"version\": \"[10.0.100,)\" }]`; `hostName` is also accepted case-insensitively. |\n\n## More Info\n\n- [template.json reference](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FReference-for-template.json) — full schema\n- [Available Symbol Generators](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FAvailable-Symbols-Generators) — generator types\n- [Post-action registry](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FPost-Action-Registry) — action IDs\n- [Constraints](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FConstraints) — constraint types\n","# Template Validation\n\nThis 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`.\n\n## When to Use\n\n- User asks to check or validate a template.json file\n- User reports \"my template doesn't show up after installing\"\n- User wants to review a template before packaging and publishing to NuGet\n- User encounters unexpected behavior from a custom template\n\n## When Not to Use\n\n- User wants to find or use existing templates — route to `template-discovery`\n- User wants to create a project — route to `template-instantiation`\n- User wants to create a template from an existing project — route to `template-authoring`\n\n## Inputs\n\n| Input | Required | Description |\n|-------|----------|-------------|\n| template.json path | Yes | Path to the template.json file or the template directory containing `.template.config\u002Ftemplate.json` |\n\n## Validation Rules\n\nWhen reviewing a template.json, check ALL of the following categories systematically. Report every finding as an error, warning, or suggestion.\n\n> **Parse gate — stop on syntax errors.** Parse JSON before applying any semantic rule. If\n> parsing fails, report the parser's line and column, show only the smallest concrete syntax\n> correction, and stop. Do not invent required-field, symbol, post-action, or discoverability\n> findings from a document that did not parse. Re-parse after the correction before making any\n> semantic claim.\n>\n> The malformed-JSON final response has exactly two parts: the one-line parse verdict and a\n> corrected snippet showing the exact edit. Do not append semantic recommendations, optional\n> metadata, or a full replacement manifest.\n\n### 1. Required Fields\n\n| Field | Severity | Rule |\n|-------|----------|------|\n| `identity` | ERROR | Must be present and non-empty |\n| `name` | ERROR | Must be present and non-empty |\n| `shortName` | ERROR | Must be present and non-empty |\n| `sourceName` | WARNING | Without it, `--name` won't customize the generated project name |\n| `author` | WARNING | Improves template discoverability |\n| `description` | SUGGESTION | Helps users understand what the template creates |\n| `classifications` | SUGGESTION | Improves search and categorization (e.g., `[\"Web\", \"API\"]`) |\n| `defaultName` | SUGGESTION | Provides a fallback project name when `--name` is not specified |\n\n### 2. Identity Format\n\n- ERROR if identity contains spaces — use dots or dashes (e.g., `MyCompany.WebApi.CSharp`)\n- WARNING if identity has no namespace separator (`.` or `-`) — use reverse-DNS format\n\n### 3. ShortName Conflicts\n\nA shortName that matches a `dotnet new` subcommand conflicts, because `dotnet new \u003Cname>` is then parsed as that subcommand instead of instantiating the template. Read the reserved set for the installed SDK from the `Commands:` section of `dotnet new --help` — that is the authoritative source and avoids this rule going stale.\n\nAs of current SDKs the subcommands include (illustrative only — version-dependent, do not hardcode this list; the live `dotnet new --help` output is canonical): `install`, `uninstall`, `update`, `list`, `search`, `details`, `create`. Note that top-level `dotnet` verbs like `build`, `run`, `test`, and `publish` do NOT conflict — `dotnet new test` does not collide with `dotnet test`.\n\n- ERROR if shortName matches any subcommand reported by `dotnet new --help` (case-insensitive)\n- WARNING if shortName is only 1 character — too short for discoverability\n- Note: shortName can be a string or an array of strings; check all values\n\n### 4. Symbol Validation\n\nFor each symbol in the `symbols` object:\n\n- ERROR if a symbol is missing the `type` field\n- For `type: \"parameter\"`:\n  - WARNING if no `datatype` specified (defaults to `string`)\n  - SUGGESTION if no `description` (improves `--help` output)\n  - If `datatype: \"choice\"`:\n    - ERROR if no `choices` defined\n    - ERROR if `choices` is empty\n    - ERROR if `defaultValue` is not in the choices list\n    - WARNING if optional (not `isRequired`) and no `defaultValue` — users get unexpected behavior\n  - If `datatype: \"bool\"`:\n    - ERROR if `defaultValue` is not a valid boolean\n  - If `datatype: \"int\"`:\n    - ERROR if `defaultValue` is not a valid integer\n  - Valid datatypes: `string`, `bool`, `choice`, `int`, `float`, `hex`, `text`\n  - ERROR if datatype is not in the valid list\n- For `type: \"computed\"`:\n  - ERROR if missing `value` expression\n- For `type: \"generated\"`:\n  - ERROR if missing `generator` field\n  - Valid generators: `casing`, `coalesce`, `constant`, `port`, `guid`, `now`, `random`, `regex`, `regexMatch`, `switch`, `join`\n\nCustom parameter help is template-specific: it appears under\n`dotnet new \u003CshortName> --help`, not the global `dotnet new --help`. Correct that premise\nwhen necessary, then explain which invalid symbol definitions prevent the parameters from\nappearing reliably.\n\nA valid choice parameter uses a non-empty choices object, for example:\n\n```json\n\"Color\": {\n  \"type\": \"parameter\",\n  \"datatype\": \"choice\",\n  \"defaultValue\": \"Blue\",\n  \"choices\": {\n    \"Blue\": { \"displayName\": \"Blue\" },\n    \"Green\": { \"displayName\": \"Green\" }\n  }\n}\n```\n\n**Parameter prefix collisions**: WARNING if any parameter name is a prefix of another parameter name (e.g., `Auth` and `AuthMode`) — this creates ambiguous parsing in expression contexts.\n\n### 5. Sources Validation\n\nFor source modifier conditions:\n- WARNING if a condition string doesn't contain parentheses around symbol names — expected format is `(symbolName)`, not bare `symbolName`\n\n### 6. Post-Action Validation\n\nFor each post-action:\n- ERROR if missing `actionId`\n- WARNING if missing `description` — this text is shown to users when the action requires manual steps\n- SUGGESTION if missing `manualInstructions` — these are shown when the action can't run automatically (e.g., in an IDE)\n\n### 7. Constraint Validation\n\nFor each constraint:\n- ERROR if missing `type` field\n- WARNING if missing `args` — most constraint types require arguments\n- For `type: \"host\"`, missing `args` is an ERROR. `args` is a required array; each entry needs `hostname`. Supported\n  built-in identifiers include `dotnetcli`, `vs`, `vs-mac`, `ide`, and\n  `dotnetcli-preview`. An optional `version` uses NuGet version\u002Frange syntax such as\n  `[10.0.100,)`. The engine matches argument keys case-insensitively, so the documented\n  `hostName` spelling is also valid. Reject unrelated fields such as `pattern` and `value`.\n- For `type: \"sdk-version\"`, `args` is a version string or array using the same syntax.\n\n### 8. Tags Validation\n\n- SUGGESTION if no `language` tag — adding `tags.language` (e.g., `\"C#\"`) improves filtering in `dotnet new list --language`\n- SUGGESTION if no `type` tag — adding `tags.type` (e.g., `\"project\"` or `\"item\"`) improves categorization\n\n## Workflow\n\n### Step 1: Locate the template.json\n\nThe file can be at:\n- Direct path: `path\u002Fto\u002Ftemplate.json`\n- In a template directory: `path\u002Fto\u002F.template.config\u002Ftemplate.json`\n- In a `.template.config` directory: `path\u002F.template.config\u002Ftemplate.json`\n\n### Step 2: Parse and validate\n\nRead the JSON. If it's malformed, report the JSON parse error with line and column.\nIf an absolute-path read fails, retry the user-supplied relative path from the working\ndirectory before concluding the file is unavailable.\n\nOnly after parsing succeeds, run all 8 validation categories above. Collect errors, warnings,\nand suggestions separately. Verify schema-sensitive claims against the installed SDK or the\ncurrent template-engine schema; do not infer a runtime failure from a field name alone.\n\n### Step 3: Report results\n\n**Lead with a one-line verdict**, then a single findings table. This decisive shape is required — do not scatter findings across prose paragraphs.\n\nVerdict header (pick one):\n- `❌ Not ready — N error(s), M warning(s)` — has errors\n- `⚠️ Publishable but N warning(s)` — no errors, has warnings\n- `✅ Ready to publish — 0 errors, 0 warnings` — no errors or warnings (optional suggestions may still apply)\n\nThen one table, ordered errors → warnings → suggestions:\n\n| Severity | Location (JSON path or `line:col`) | Issue | Fix |\n|----------|------------------------------------|-------|-----|\n| ERROR | `shortName` | `\"list\"` conflicts with a `dotnet new` subcommand | Rename to a distinctive value, e.g. `\"my-list\"` |\n| ERROR | `symbols.maxRetries.defaultValue` | `\"abc\"` is not a valid `int` | Set a numeric default, e.g. `\"3\"` |\n| WARNING | `sourceName` | Missing replacement token | Set it to the source project name |\n\n**Every ERROR and WARNING MUST include a concrete fix** — the corrected value, JSON snippet, or a specific edit instruction (e.g. \"remove the trailing comma\"), not just a restatement of the problem. A finding without an actionable fix is incomplete. This is the single biggest thing that separates a useful validation from a generic lint.\n\nClose with the total: \"N error(s), M warning(s), K suggestion(s).\"\n\nFor malformed JSON the output is intentionally smaller and has exactly two parts:\n\n`❌ Not ready — JSON parse error at line N, column M: \u003Cmessage>.`\n\n```json\n\u003Csmallest corrected fragment showing the exact edit>\n```\n\nDo not append a findings table or semantic totals until the corrected file parses.\n\n## Common Pitfalls\n\n| Pitfall | Impact |\n|---------|--------|\n| ShortName = \"list\" or \"search\" | Template can never be created — conflicts with a `dotnet new` subcommand |\n| Missing `sourceName` | `--name MyProject` doesn't rename anything in the generated files |\n| Choice parameter without `defaultValue` | Confusing user experience on optional choice params |\n| Invalid `datatype` value | Template engine ignores the symbol, causing silent failures |\n| Computed symbol without `value` | Template engine throws at instantiation time |\n| Parameter prefix collision (`Auth` vs `AuthMode`) | Ambiguous expression evaluation |\n| Source condition without parentheses | Condition may not evaluate correctly |\n| Continuing semantic validation after JSON parsing failed | Findings are speculative. Report the exact parse fix and stop. |\n| Host constraint uses scalar `args`, the invalid `dotnet-cli` host ID, or unrelated fields | Use `args: [{ \"hostname\": \"dotnetcli\", \"version\": \"[10.0.100,)\" }]`; `hostName` is also accepted case-insensitively. |\n\n## More Info\n\n- [template.json reference](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FReference-for-template.json) — full schema\n- [Available Symbol Generators](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FAvailable-Symbols-Generators) — generator types\n- [Post-action registry](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FPost-Action-Registry) — action IDs\n- [Constraints](https:\u002F\u002Fgithub.com\u002Fdotnet\u002Ftemplating\u002Fwiki\u002FConstraints) — constraint types\n",{"name":5,"license":14,"description":23},"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 templates (use template-discovery), creating projects from templates (use template-instantiation), creating templates from existing projects (use template-authoring).\n","main","ccab8dffc0ecc173838f51e4c5f0d3b51a704f41","plugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-validation","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills","https:\u002F\u002Fgithub.com\u002Fdeadmade","https:\u002F\u002Fdeadmade.github.io\u002F","Blood, an Ocean of blood","2026-11-14 02:03:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add deadmade\u002Fdead-agent-skills --skill template-validation",{"tool":38,"command":39},"bunx","bunx skills add deadmade\u002Fdead-agent-skills --skill template-validation",{"tool":41,"command":42},"pnpm","pnpm dlx skills add deadmade\u002Fdead-agent-skills --skill template-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Ftemplate-validation\u002FSKILL.md",true,[],[47,54,63,71,78,85],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7CVRBFTXSTTQ7F5P6PJEFYA","rust-best-practices","Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Frust-skills\u002Fskills\u002Frust-best-practices\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7CVR0W7B8EGTNPSPA7FPC4Z","postgres-database-migration","Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases.\n\n**Trigger when user asks to:**\n- Test a schema migration before applying it to production\n- Add, remove, or rename columns safely on a live table\n- Change a column's data type without downtime\n- Add or drop indexes, constraints, or foreign keys on large tables\n- Understand which ALTER TABLE operations lock the table\n- Roll back a failed migration\n- Plan a zero-downtime migration strategy\n- Fork a database to test a migration safely\n\nCovers: lock-level reference for every common DDL operation, safe migration patterns, fork-based testing, zero-downtime column changes, index creation, constraint addition, backfill strategies, pre\u002Fpost-migration validation, and rollback planning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-database-migration\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":58,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7CVQWK20ASAZN5VETZC8J99","postgres-best-practices","Best practices and guidelines for working with Postgres. Covers schema design, indexing strategies, query optimization, migrations, and common pitfalls. Use when writing SQL, designing database schemas, optimizing queries, or setting up a Postgres database.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fpostgres\u002Fskills\u002Fpostgres-best-practices\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7CVQ5CY7AQHY7A2Y99RE6A7","writing-mstest-tests","ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwriting-mstest-tests\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7CVPWJZ63GB0810F0SCGZ1K","winforms-expert","Create, modify, debug, or review Windows Forms applications only when the request contains a concrete Windows Forms marker. USE FOR: WinForms, Windows Forms, System.Windows.Forms, WinForms Form or UserControl designer files (*.Designer.cs or *.Designer.vb), Visual Studio WinForms Designer, TableLayoutPanel, BindingSource, DataGridView, Control.InvokeAsync, component-tray ownership, or custom control serialization. DO NOT USE FOR: WPF or WPF XAML, including Window.InputBindings, KeyBinding, commands, or DataContext; .NET MAUI; Avalonia; or any request where none of the listed Windows Forms markers is present.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fwinforms-expert\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7CVPR0QFZ1HMJ6GZRBQAQ7W","vectorization","Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64\u002F128\u002F256\u002F512, or platform hardware intrinsics; reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.","https:\u002F\u002Fgithub.com\u002Fdeadmade\u002Fdead-agent-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fopt-in\u002Fimplementation\u002Fcsharp-skills\u002Flibrary\u002Fvectorization\u002FSKILL.md",[],[]]