Name: dramafinder/vaadin-playwright-test
Rating: 73.6 (1 reviews)
Author: dramafinder

dramafinder/vaadin-playwright-test

Generate Playwright integration tests for Vaadin 25 views using the DramaFinder library. Use when the user wants to write IT tests for a Vaadin view, mentions DramaFinder, or asks about Playwright testing in a Vaadin project.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

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

A well-structured, highly actionable skill body with clear sequencing and validation feedback. The one substantive weakness is progressive disclosure: four referenced files are signaled but not actually shipped in the bundle, leaving dangling links.

Suggestions

Ship the referenced files (TESTING.md, element-mapping.md, setup.md, api-reference.md) alongside SKILL.md, or inline the essential content so the skill is self-contained.

Verify each relative link resolves to a real bundle file so progressive disclosure actually delivers the promised detail.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence — no explaining of what Vaadin/Playwright are — with concrete code and commands throughout; the only repetition (the 'no raw locators' rule) is deliberate reinforcement of a critical anti-pattern.	3 / 3
Actionability	Fully executable guidance: complete Java test-class templates, copy-paste component patterns (smoke, form validation, grid), and exact commands (grep pom.xml, find SpringPlaywrightIT.java, mvn verify -Dit.test=<ViewName>IT).	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with branching logic (DramaFinder found/not-found, SpringPlaywrightIT 0/1/multiple hits) and a validate→fix feedback loop in Step 5 ('run it directly and fix any failures before finishing').	3 / 3
Progressive Disclosure	The design is excellent — a concise overview with well-signaled one-level-deep references to TESTING.md, element-mapping.md, setup.md, and api-reference.md — but none of those referenced files are present in the bundle, so the navigation is non-functional.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 with excellent trigger coverage, clear what/when structure, and low conflict risk. Its only flaw is second-person voice in the trigger clause, which costs it a specificity point per the rubric guidelines.

Suggestions

Rewrite the trigger clause in third person to avoid the second-person penalty, e.g. 'Use when writing, editing, or running an integration/IT test for a Vaadin view' instead of 'Use whenever you are about to write'.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('element interaction, form validation, grid assertions, and navigation checks'; 'write, edit, or run an integration/IT test') which would warrant a 3, but the description uses second-person voice ('Use whenever you are about to write'), which the guidelines penalize by reducing specificity by one.	2 / 3
Completeness	Explicitly states both what ('Generate Playwright integration tests for Vaadin 25 views...') and when ('Use whenever you are about to write, edit, or run an integration/IT test for a Vaadin view'), with multiple explicit trigger scenarios.	3 / 3
Trigger Term Quality	Strong coverage of natural triggers users/issues actually say: 'DramaFinder', 'Playwright', 'SpringPlaywrightIT', '@PlaywrightElement', 'implement #85', 'fix the failing test', 'add coverage for this view'.	3 / 3
Distinctiveness Conflict Risk	Narrow niche — Vaadin 25 + DramaFinder + Playwright IT tests — with highly specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 8 missing	Warning

	Total	15 / 16 Passed

Reviewed

~2 months ago

Table of Contents

Discovery Implementation Validation