bunit-test-migration
Migrate bUnit test files from deprecated beta API (1.0.0-beta-10) to bUnit 2.x stable API. Use this when working on .razor test files in BlazorWebFormsComponents.Test that contain old patterns like TestComponentBase, Fixture, or SnapshotTest.
72
88%
Does it follow best practices?
Impact
—
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, specific migration task with concrete actions, explicit trigger conditions, and highly distinctive terminology. It uses third person voice correctly and provides both the 'what' and 'when' with specific pattern names that serve as natural trigger terms. The description is concise yet comprehensive for its purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'Migrate bUnit test files from deprecated beta API (1.0.0-beta-10) to bUnit 2.x stable API' and names specific patterns like TestComponentBase, Fixture, SnapshotTest. Very specific about what it does. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate bUnit test files from deprecated beta API to 2.x stable API) and 'when' ('Use this when working on .razor test files in BlazorWebFormsComponents.Test that contain old patterns like TestComponentBase, Fixture, or SnapshotTest'). | 3 / 3 |
Trigger Term Quality | Includes highly natural and specific trigger terms: 'bUnit', '.razor test files', 'BlazorWebFormsComponents.Test', 'TestComponentBase', 'Fixture', 'SnapshotTest', 'beta API', '1.0.0-beta-10', '2.x stable API'. These are exactly the terms a user working on this migration would use. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely narrow niche: specific library (bUnit), specific version migration (beta-10 to 2.x), specific project (BlazorWebFormsComponents.Test), and specific deprecated patterns. Very unlikely to conflict with any other skill. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable migration skill with excellent use of diff blocks, complete before/after examples, and a solid verification workflow. Its main weakness is length — the special patterns and optional logging sections add bulk that could be offloaded to supplementary files. The core transformation rules and quick reference table are exceptionally well-crafted.
Suggestions
Remove or significantly trim the xUnit Logger section — it's explicitly optional and adds ~20 lines of marginal value.
Consider extracting the 'Special Patterns' section into a separate PATTERNS.md file and linking to it, keeping SKILL.md focused on the core transformation rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of diff blocks and tables, but includes some unnecessary sections like the xUnit Logger pattern which is marked as optional and adds bulk. The 'When to Apply' section slightly overlaps with the description. The logging example is particularly verbose for something explicitly optional. | 2 / 3 |
Actionability | Excellent actionability throughout. Every transformation rule has concrete before/after diff examples, the complete example shows a full file migration, and verification commands are copy-paste ready. Special patterns cover real-world scenarios with executable code. | 3 / 3 |
Workflow Clarity | The transformation rules are clearly numbered and sequenced. The verification section provides explicit build-check, test-discovery, and test-run steps. The common errors table serves as a feedback loop for troubleshooting. The overall flow from detection → transformation → verification is well-structured. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's a long monolithic file (~200 lines) with no references to external files. The special patterns section (services, auth, isolated context, logging) could be split into a separate reference file to keep the main skill leaner. | 2 / 3 |
Total | 10 / 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
147d0c4
- 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.