CtrlK
BlogDocsLog inGet started
Tessl Logo

playwright-test

Generates native C# Playwright end-to-end (E2E) browser tests for user journeys (UC-* / TC-*) using Microsoft.Playwright.Xunit. Use when the user asks to "write e2e test", "create playwright test for dotnet", "write browser test in C#", or mentions Playwright with .NET.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./aiup-blazor-dotnet/skills/playwright-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable skill body with an executable code example, clear workflow, and a verification step. It is held at 4s rather than 5s by a referenced-but-undefined fixture, the absence of an explicit error-recovery feedback loop, and a body slightly exceeding the simple-skill length threshold.

Suggestions

Define or link the TestServerFixture (and the WebApplicationFactory<Program> host setup) so the example is fully copy-paste-runnable without an undefined dependency.

Add an explicit feedback loop after 'dotnet test' (e.g., on failure, debug, fix, and re-run until green) to push workflow_clarity toward 5.

Tighten the host-server configuration sentence and the 'If Tests... Already Exist' intro to remove minor verbosity and improve conciseness.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows (no 'what is Playwright' padding); minor prose such as the host-server configuration sentence and the 'If Tests... Already Exist' intro could be trimmed, fitting anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Provides a copy-paste-ready C# example, a concrete command ('dotnet test'), and named APIs (GetByRole, GetByLabel, Expect().ToBeVisibleAsync()); the TestServerFixture is referenced but not defined, leaving a minor gap that fits anchor 4.

4 / 5

Workflow Clarity

A clear 4-step sequence with a verification checkpoint (run 'dotnet test') and a 'run the whole test class afterwards' checkpoint in the update section; it lacks an explicit fail -> fix -> re-run feedback loop, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

Content is cleanly sectioned (Goal, If Tests Already Exist, Workflow, Verification) with no nested references and no bundle files; the body is ~60 lines, just over the under-50 simple-skill exception that would allow a 5, so it sits at anchor 4.

4 / 5

Total

16

/

20

Passed

Description

82%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 what the skill does and gives explicit, natural trigger phrases for when to use it, with minimal conflict risk. The only weak spot is specificity, which lists one primary action rather than a comprehensive set of concrete actions.

DimensionReasoningScore

Specificity

Names the domain and one richly detailed concrete action ('Generates native C# Playwright end-to-end (E2E) browser tests... using Microsoft.Playwright.Xunit'), but it is a single action rather than the 'several specific actions' the anchor 4 requires.

3 / 5

Completeness

Clearly answers 'what' ('Generates native C# Playwright... browser tests for user journeys (UC-* / TC-*)') and explicitly 'when' via a 'Use when...' clause with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Includes several natural phrases users would say ('write e2e test', 'create playwright test for dotnet', 'write browser test in C#', 'Playwright with .NET') with synonyms, though it lacks file-extension-style terms (none are natural for this domain), matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

A narrow, specific niche (native C# + Microsoft.Playwright.Xunit + UC/TC user journeys) with distinct triggers and minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

17

/

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
AI-Unified-Process/marketplace
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.