vaadin-playwright-test

Generate Playwright integration tests for Vaadin 25 views using the DramaFinder library, including element interaction, form validation, grid assertions, and navigation checks. Use whenever you are about to write, edit, or run an integration/IT test for a Vaadin view — including when the requirement comes from a GitHub issue, PR, spec, or ticket rather than the user's direct words (e.g. "implement

Quality

90%

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

81%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 exemplary multi-step workflow and feedback loops. It is mostly lean and uses progressive disclosure well, with minor redundancy and bundle references that could not be verified as present.

Suggestions

Consolidate the raw-locator prohibition: state the rule once in Best practices and keep only the code example in the 'Do NOT drop to raw locators' subsection to remove triplicate restatement.

Verify and ship the referenced bundle files (api-reference.md, element-mapping.md, TESTING.md, setup.md) alongside SKILL.md so the progressive-disclosure navigation actually resolves.

Tighten the opening meta-blockquote about invoking via the Skill tool — the essential signal ('invoke, don't just read') can be conveyed in one line.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and domain-specific, but the raw-locator prohibition is restated three times (Best practices, the 'Do NOT drop to raw locators' subsection, and the decompile warning) and the opening meta-blockquote could be trimmed, keeping it just short of lean.	4 / 5
Actionability	Provides concrete, mostly executable template code (default class structure, smoke test, form validation, grid loading) and specific commands like 'mvn verify -Dit.test=<ViewName>IT', though examples are view-specific templates with placeholders rather than literally copy-paste ready.	4 / 5
Workflow Clarity	A clear five-step sequence (assess → map → generate → write → run) with parallel checks, explicit decision branches for missing/found DramaFinder and SpringPlaywrightIT location, and a run→fix-failures feedback loop in Step 5 plus an interactive confirmation checkpoint in Step 4.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references to api-reference.md, element-mapping.md, TESTING.md, and setup.md with a clear overview, but those referenced bundle files are not present in the skill directory to verify, weakening the navigation guarantee.	4 / 5
	Total	17 / 20 Passed

Description

100%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 when to invoke it, with rich natural trigger terms and a distinct niche. It uses third-person voice throughout and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'element interaction, form validation, grid assertions, and navigation checks' — alongside the core 'Generate Playwright integration tests for Vaadin 25 views', giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (generate Playwright IT tests for Vaadin views with DramaFinder) and when ('Use whenever you are about to write, edit, or run an integration/IT test...'), with concrete trigger phrases including issue/PR/spec-derived requests.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and file paths users actually say: 'Playwright', 'integration/IT test', 'DramaFinder', 'SpringPlaywrightIT', '@PlaywrightElement', 'implement #85', 'fix the failing test', and 'src/test/**/tests/it/'.	5 / 5
Distinctiveness Conflict Risk	A clear niche — Playwright integration tests for Vaadin 25 views via the DramaFinder library — with highly specific triggers that make overlap with other skills unlikely.	5 / 5
	Total	20 / 20 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: 11 missing	Warning

	Total	15 / 16 Passed

Repository: parttio/dramafinder
Path: skills/vaadin-playwright-test/SKILL.md
Commit: 3165b41

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.