CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/selenium-testing

Use for any question or task about Selenium WebDriver tests in Java, Python, C# or other bindings, including quick how-to questions and one pasted test to fix: explicit waits instead of sleeps, stable locators instead of absolute XPath, driver version errors (Selenium Manager), page objects, BiDi console errors, Grid in Docker and JUnit XML. New projects usually pick Playwright.

Quality

92%

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

Overview
Quality
Evals
Security
Files

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 strong, highly actionable skill body with complete executable examples, a well-sequenced 8-step workflow, and explicit verification checkpoints with error-recovery guidance. Its main weaknesses are token efficiency — inline version pins that will rot and deep-dive material that belongs in reference files — and only minimal use of the bundle for content splitting.

Suggestions

Move the 'Selenium Manager on locked-down CI' env-var enumeration and the Grid uploads/downloads mechanics into a references/ file (like language-bindings.md), keeping only the most common cases inline in SKILL.md.

Consolidate the pinned versions (selenium-java 4.52.0, junit-jupiter 6.1.3, Grid tag 4.51.0-20261010) into the single dated 'Versions' note in the References section instead of inlining them in Steps 1 and 6, so time-sensitive details rot in one place.

Trim the Overview's protocol description ("W3C-standard browser automation protocol with the broadest language support") to one line — Claude already knows what Selenium is.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no re-teaching of Selenium basics), but it embeds time-sensitive version pins inline — "4.52.0", "6.1.3", "4.51.0-20261010", "versions current on Maven Central, 3 Nov 2026" in Steps 1 and 6 — rather than confining them to an 'old patterns'/'Versions' section, and deep-dive sections like the Selenium Manager env-var enumeration and Grid uploads/downloads could be tightened or offloaded. This matches anchor 3 ('mostly efficient but... could be tightened') better than anchor 4.

3 / 5

Actionability

Fully executable throughout: a complete pom.xml, a copy-paste-ready JUnit test with setup/teardown and waits, a page object class, a BiDi error handler, docker-compose Grid config, and a CI YAML workflow. Specific examples cover the common cases, matching the anchor-5 example.

5 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced (install → author → locators → waits → page objects/BiDi → Grid → bindings → CI) with explicit validation checkpoints and error recovery: "Verify: curl http://localhost:4444/wd/hub/status reports \"ready\": true... if not, the hub or nodes haven't registered - check docker compose ps and the node container logs" and the surefire-reports existence check. This matches anchor 5's 'explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

The single bundle file references/language-bindings.md is real, clearly signaled in Step 7 ("worked examples: [references/language-bindings.md](references/language-bindings.md)"), one level deep, and section headers aid navigation. However, at ~480 lines several deep-dive sections (Selenium Manager lockdown env vars, Grid uploads/downloads) remain inline and could be split into reference files, so it fits anchor 4 ('most content appropriately placed; minor organization gaps') rather than anchor 5's 'content appropriately split'.

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.

An exemplary description: it states a concrete capability list, gives explicit 'Use for...' trigger guidance with natural user phrasing, and even includes boundary guidance steering new projects to Playwright. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete, action-framed capabilities — "explicit waits instead of sleeps, stable locators instead of absolute XPath, driver version errors (Selenium Manager), page objects, BiDi console errors, Grid in Docker and JUnit XML" — which is comprehensive coverage within the domain, matching the anchor-5 example rather than anchor 4's 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers both questions: the what ("explicit waits instead of sleeps, stable locators..., page objects, BiDi console errors, Grid in Docker and JUnit XML") and the when ("Use for any question or task about Selenium WebDriver tests..., including quick how-to questions and one pasted test to fix") with concrete trigger phrases, exactly matching the anchor-5 example.

5 / 5

Trigger Term Quality

Covers the natural terms users say when they need this skill: "Selenium WebDriver tests", "Java, Python, C#", "quick how-to questions", "one pasted test to fix", "sleeps", "XPath", "driver version errors", "JUnit XML". No meaningful natural phrase for this domain is missing, so it fits anchor 5 rather than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Selenium WebDriver tests) with distinct triggers, and the closing "New projects usually pick Playwright" explicitly routes modern-tooling requests away, minimizing conflict with sibling skills like playwright-testing.

5 / 5

Total

20

/

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.

Reviewed

On this page