Implements the parameter alias pattern for Blazor components where multiple parameter names map to the same behavior. Covers independent auto-property declaration, invocation-site coalescing, and HasDelegate guard updates. Use when a Blazor component needs backward-compatible parameter names, supporting On-prefixed event aliases, or ensuring Web Forms markup migration works without breaking existing consumers.
95
92%
Does it follow best practices?
Impact
100%
1.36xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description that clearly defines a narrow technical niche. It lists specific implementation actions, includes natural trigger terms a developer would use, and has an explicit 'Use when' clause with multiple concrete scenarios. The description is concise yet comprehensive for its domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'independent auto-property declaration', 'invocation-site coalescing', and 'HasDelegate guard updates'. These are precise implementation steps rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (implements parameter alias pattern with specific techniques) and 'when' (explicit 'Use when' clause covering backward-compatible parameter names, On-prefixed event aliases, and Web Forms migration scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Blazor components', 'parameter alias', 'backward-compatible parameter names', 'On-prefixed event aliases', 'Web Forms markup migration'. These cover the domain well and match how developers would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: Blazor component parameter aliasing with Web Forms migration context. This is unlikely to conflict with other skills due to the very targeted combination of Blazor, parameter aliases, and Web Forms migration. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that clearly teaches a specific Blazor pattern with executable code examples and useful anti-patterns. Its main weakness is the 'Why This Works' section, which explains Blazor internals that Claude likely already knows and partially duplicates the 'Critical' note. Overall it's a strong skill that could be slightly tightened.
Suggestions
Remove or significantly condense the 'Why This Works' section — the critical behavioral note about independent auto-properties is already covered in step 1, and Blazor's parameter diffing mechanics are knowledge Claude already has.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why This Works' section explains Blazor parameter diffing mechanics that Claude likely already understands, and some of the rationale is redundant with the 'Critical' note in section 1. However, the anti-patterns section adds genuine value concisely. | 2 / 3 |
Actionability | All three steps provide fully executable, copy-paste-ready C# code with clear patterns. The anti-patterns section includes concrete wrong examples, making it unambiguous what to do and what to avoid. | 3 / 3 |
Workflow Clarity | The three-step process is clearly sequenced (add property → coalesce at invocation → update guards), each step is unambiguous, and the anti-patterns serve as validation guidance to prevent common mistakes. | 3 / 3 |
Progressive Disclosure | For a focused, single-purpose skill under 50 lines of effective content, the structure is well-organized with clear sections (When to Use, Pattern with numbered steps, Why This Works, Anti-Patterns). No external references are needed. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
1bd9b17
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.