shared-base-extraction
Extracts duplicated properties, methods, and logic from sibling Blazor components into a shared intermediate base class. Covers identification of duplicated surfaces, base class creation, member migration, and @inherits directive updates. Use when three or more components share copy-pasted Parameter declarations, consolidating shared helper methods, or refactoring component inheritance hierarchies.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly defines a narrow, well-scoped task with specific concrete actions and explicit trigger conditions. It uses domain-appropriate terminology that Blazor developers would naturally use, and the 'Use when' clause provides three distinct scenarios for activation. The description is concise yet comprehensive, making it easy for Claude to select this skill precisely when needed.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: extracting duplicated properties/methods/logic, base class creation, member migration, and @inherits directive updates. These are all concrete, well-defined operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (extracts duplicated properties/methods/logic into shared base class, covers identification, creation, migration, directive updates) and 'when' (explicit 'Use when' clause with three specific trigger scenarios: three+ components sharing copy-pasted Parameters, consolidating shared helpers, refactoring inheritance hierarchies). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Blazor components', 'base class', 'duplicated', 'Parameter declarations', 'shared helper methods', 'refactoring', 'component inheritance', '@inherits directive'. These cover the natural vocabulary of a Blazor developer seeking this kind of refactoring. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: specifically targets Blazor component inheritance refactoring with base class extraction. The combination of Blazor, @inherits, Parameter declarations, and sibling component deduplication makes it very unlikely to conflict with other skills. | 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, concise skill that clearly guides the base class extraction refactoring workflow. Its main weakness is limited actionability — the guidance is instructional rather than providing complete before/after code examples that would make the pattern copy-paste ready. The workflow clarity and organization are strong, with appropriate validation steps and a useful checklist.
Suggestions
Add a concrete before/after code example showing a complete sibling component being refactored (e.g., 2 components with duplicated [Parameter] properties → shared base class + simplified subclasses)
Include a minimal example of the .razor file @inherits update alongside the .razor.cs change to make step 4 fully executable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude understands Blazor, C#, and component inheritance without explaining basics. Every section adds actionable value without padding. | 3 / 3 |
Actionability | Steps are clear and specific but mostly instructional rather than executable. The single code snippet is a class declaration fragment, not a complete executable example. Missing a before/after code example showing the full refactoring pattern would significantly improve actionability. | 2 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with a logical progression from identification through verification. Step 5 includes a validation checkpoint (build and verify) with a specific error code to watch for (CS0263), and the checklist provides additional verification. The feedback loop is implicit but appropriate for a non-destructive refactoring operation. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single focused task, the content is well-organized into clear sections (When to Use, Steps, Key Facts, Checklist) without needing external references. The structure supports quick scanning and progressive reading. | 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.
- Repository
- FritzAndFriends/BlazorWebFormsComponents
- Commit
1bd9b17
- Reviewed
Table of Contents
Is this your skill?
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.