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.
90
88%
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, specific migration task with concrete version numbers, target file types, and deprecated patterns to look for. It uses third person voice, provides both 'what' and 'when' clauses, and includes highly distinctive trigger terms that make it virtually impossible to confuse with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: migrate bUnit test files, specifies the source version (1.0.0-beta-10) and target version (2.x stable API), and names specific patterns to replace (TestComponentBase, Fixture, SnapshotTest). | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate bUnit test files from deprecated beta API to 2.x stable API) and 'when' (when working on .razor test files in BlazorWebFormsComponents.Test that contain old patterns like TestComponentBase, Fixture, or SnapshotTest) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes highly specific natural keywords users would use: 'bUnit', 'migrate', '.razor test files', 'TestComponentBase', 'Fixture', 'SnapshotTest', 'BlazorWebFormsComponents.Test', 'beta API'. These are terms a developer would naturally mention when needing this migration. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche: bUnit migration from a specific beta version to 2.x, targeting a specific project (BlazorWebFormsComponents.Test) with named 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 a reference file. The core transformation rules and quick reference table are well-crafted and immediately useful.
Suggestions
Move the 'Special Patterns' section (services, auth, isolated context, logger) to a separate PATTERNS.md file and link to it, keeping SKILL.md focused on the core transformation rules.
Remove the xUnit Logger section entirely or reduce it to a one-line mention — it's optional, verbose, and unlikely to be needed during most migrations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of diff blocks and tables, but the xUnit Logger section and some explanatory text (e.g., the intro paragraph restating what's in the description) add unnecessary tokens. The logging example is verbose for an optional, edge-case feature. | 2 / 3 |
Actionability | Excellent actionability throughout — every transformation rule has concrete before/after diff blocks, the complete example is fully executable, verification commands are copy-paste ready, and the common errors table provides specific fixes. | 3 / 3 |
Workflow Clarity | The transformation rules are clearly numbered and sequenced, the complete before/after example demonstrates the full workflow, and there's an explicit verification section with build, list, and run steps. The common errors table serves as a feedback loop for error recovery. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but it's a fairly long monolithic file. The special patterns section (authentication, services, logger, isolated context) 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
9bf8669
- 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.