CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bunit-testing

Write bUnit v2 component tests for BlazorWebFormsComponents. Covers BlazorWebFormsTestContext base class, Render() with inline Razor syntax, Shouldly assertions, testing data-bound components, validation components, event callbacks, JS interop mocking, service registration, authentication testing, and xUnit logger integration. Use when writing new component tests, testing complex scenarios, or understanding the BWFC test infrastructure.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured test-authoring skill that leads with executable examples and closes with a verification checklist. The only real opportunity for improvement is trimming the longer inline code blocks to sharpen token efficiency.

Suggestions

Shorten the longest examples (GridView event callbacks, cancel-event) to a minimal reproduction, or move the full variants behind a brief 'see also' note, to improve token efficiency.

Tighten the checklist so each item names a concrete pass/fail check (e.g. specify the assertion library call or the exact `dotnet test` filter to re-run) rather than a restatement of the convention.

DimensionReasoningScore

Conciseness

The body is code-forward and assumes Claude's competence — there is no 'what is bUnit' padding — but several inline examples (notably the event-callback and GridView sections) are long enough they could be trimmed without losing clarity.

4 / 5

Actionability

Provides copy-paste-ready, executable Razor and C# examples across the common cases (basic rendering, properties, data binding, events, validation, JS interop, services, auth, component access, markup matching) plus concrete `dotnet test` commands.

5 / 5

Workflow Clarity

The authoring patterns are clearly organized by topic and the closing Checklist acts as an explicit verification checkpoint ('dotnet test ... passes across all target frameworks'); this is a non-destructive authoring skill so no validate-fix-retry loop is required, but a few checklist items lack a concrete pass/fail signal.

4 / 5

Progressive Disclosure

No bundle files are present (references/, scripts/, assets/ are empty), so the skill is a single self-contained file; it is well-organized into clearly headed sections with no nested references, which for a file like this satisfies the well-organized-structure standard.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capabilities and trigger conditions. The main weakness is trigger-term naturalness — the vocabulary leans on project-internal jargon rather than the phrasings a user would naturally utter.

Suggestions

Soften the jargon load in the trigger clause by adding user-facing phrasings such as 'Blazor component tests' or 'Razor test authoring' alongside the existing 'writing new component tests'.

Add an explicit boundary cue to the description itself (e.g. 'Not for migrating bUnit beta tests to v2') so the distinction from the migration skill is visible without reading the body.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Render() with inline Razor syntax, Shouldly assertions, testing data-bound components, validation components, event callbacks, JS interop mocking, service registration, authentication testing, and xUnit logger integration' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (write bUnit v2 component tests covering the listed areas) and 'when' via the concrete 'Use when writing new component tests, testing complex scenarios, or understanding the BWFC test infrastructure' clause.

5 / 5

Trigger Term Quality

Includes natural phrases a user might say ('writing new component tests', 'testing complex scenarios'), but the term set is dominated by project jargon (bUnit, BlazorWebFormsComponents, BWFC) and lacks common user-facing synonyms.

4 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (bUnit v2 tests for BlazorWebFormsComponents) with distinctive trigger phrasing, giving it a clear slot with minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

FritzAndFriends/BlazorWebFormsComponents

Path

.github/skills/bunit-testing/SKILL.md

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.