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

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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.

The body is a strong, actionable workflow with executable code templates, clear sequencing, and well-signaled progressive disclosure. Its main weaknesses are some repetition of the raw-locator rule across three sections and references to bundle files that are not present in the bundle.

Suggestions

Consolidate the raw-locator prohibition into one place (Best Practices) and have Step 2 reference it, rather than restating the rule plus a dedicated subsection.

Ensure the referenced bundle files (api-reference.md, element-mapping.md, TESTING.md, setup.md) actually ship alongside SKILL.md, since the body relies on them being present at invocation time.

Tighten the opening blockquote: it spends several lines justifying the invoke-by-tool instruction and the jar rule, which could be cut to one sentence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept explanations Claude already knows, but the raw-locator prohibition is stated in Best Practices, restated in Step 2's intro, and expanded again in a dedicated "Do NOT drop to raw locators" subsection; the opening blockquote also over-explains invocation mechanics. These could be consolidated.	4 / 5
Actionability	Fully executable guidance: copy-paste-ready templates for the default class, smoke tests, form validation, and grid loading, plus concrete commands like `mvn verify -Dit.test=<ViewName>IT` and specific grep/find checks covering the common cases.	5 / 5
Workflow Clarity	Clear five-step sequence with explicit validation checkpoints (parallel project-state checks in Step 1, confirm-no-wrapper before raw locators, run-and-fix-failures feedback loop in Step 5) and branching by Spring/non-Spring and interactive/autonomous modes.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep references to api-reference.md, element-mapping.md, TESTING.md, and setup.md with guidance to grep rather than read whole files, but the referenced bundle files are not actually present in the bundle directory, preventing a top score.	4 / 5
	Total	18 / 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.

The description is exemplary: it states concrete capabilities, provides comprehensive and natural trigger terms, explicitly covers both what and when (including indirect triggers from issues/PRs), and occupies a distinct niche. Voice is third person with no over-claims.

Dimension	Reasoning	Score
Specificity	"Generate Playwright integration tests for Vaadin 25 views using the DramaFinder library, including element interaction, form validation, grid assertions, and navigation checks" names the domain, the library, and multiple specific concrete actions with comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ("Generate Playwright integration tests...") and when ("Use whenever you are about to write, edit, or run an integration/IT test...") with concrete trigger phrases, including indirect triggers via issues/PRs/specs.	5 / 5
Trigger Term Quality	Comprehensive natural terms including synonyms and code identifiers: "DramaFinder", "Playwright", "SpringPlaywrightIT", "@PlaywrightElement", "src/test/**/tests/it/", plus natural phrases like "implement #85" and "fix the failing test".	5 / 5
Distinctiveness Conflict Risk	Clear niche combining Vaadin 25, Playwright, and DramaFinder with distinct triggers; minimal conflict risk with other skills.	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: fe74d42

Reviewed: 6 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.