CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/selenium-grid-4-runner

Author and operate Selenium Grid 4 - self-hosted distributed WebDriver. Covers the six-component architecture (Router / Distributor / Session Map / Event Bus / New Session Queue / Node), standalone vs hub-and-node modes, the Docker-image stack (selenium/standalone-chrome, selenium/hub, selenium/node-chrome), node registration, session-queue tuning, and observability. Use for self-hosted cross-browser testing when data residency or cost-control require an on-prem grid. This is the self-hosted execution RUNNER - for the zero-infra alternative use browser-matrix-runner (Playwright bundled engines); for managed cloud grids use browserstack-automate, saucelabs-automate, or lambdatest-automate; to decide WHICH browsers and tiers to run use browser-matrix-strategy-reference.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A tight, highly actionable authoring/operating reference with clean progressive disclosure and a validated CI workflow. The main weakness is conciseness: a pinned example version that will age and minor duplication of the cloud-alternatives list.

Suggestions

Replace the pinned example version `4.21.0` with a placeholder like `<latest>` or a note to set SE_VERSION from the Selenium downloads page, so the skill does not age.

De-duplicate the cloud-grid alternatives: list them once (in 'When to use' or 'References') rather than repeating them across both sections.

DimensionReasoningScore

Conciseness

Mostly efficient tables and code that assume Claude's competence, but it pins a time-sensitive version ('examples use 4.21.0', 'SE_VERSION=4.21.0') that will stale, and repeats the cloud-grid alternatives in both 'When to use' and 'References'. Not 3 because of the stale version pin and redundancy; not 1 because it is lean overall with little padding.

2 / 3

Actionability

Provides executable java -jar standalone/hub/node commands, a complete docker-compose.yml, a Python Remote WebDriver snippet, a W3C capabilities JSON, and a settings table with defaults - copy-paste ready. Not 2 because the code is complete and executable rather than pseudocode.

3 / 3

Workflow Clarity

The CI workflow (in the referenced file) sequences start grid -> wait for /status ready (validation loop with break) -> run tests -> tear down (if: always()), and the anti-patterns reinforce health-check gating. Not 2 because explicit validation checkpoints are present rather than missing.

3 / 3

Progressive Disclosure

Keeps the core standalone/hub-and-node/docker modes inline and offloads fully-distributed and CI detail to a single one-level-deep, clearly-signaled references/distributed-and-ci.md (linked twice, verified to exist). Not 2 because references are well-signaled and content is appropriately split, not monolithic.

3 / 3

Total

11

/

12

Passed

Description

100%

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 answers both what the skill does and when to use it, with explicit triggers and clear differentiation from sibling grid/browser skills. Third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities - 'Author and operate Selenium Grid 4', the 'six-component architecture (Router / Distributor / Session Map / Event Bus / New Session Queue / Node)', 'standalone vs hub-and-node modes', and 'session-queue tuning, and observability'. Not 2 because it enumerates far more than a domain plus a few actions.

3 / 3

Completeness

'Author and operate Selenium Grid 4...' answers what, and 'Use for self-hosted cross-browser testing when data residency or cost-control require an on-prem grid' gives an explicit when. Not 2 because the when is stated with an explicit trigger, not merely implied.

3 / 3

Trigger Term Quality

Includes natural terms a user would say - 'self-hosted cross-browser testing', 'data residency', 'cost-control', 'on-prem grid', and 'Selenium Grid 4'. Not 2 because it covers the common variations rather than missing obvious ones.

3 / 3

Distinctiveness Conflict Risk

Carves out a clear 'self-hosted execution RUNNER' niche and explicitly names the alternatives (browser-matrix-runner, browserstack/sauce/lambdatest-automate, browser-matrix-strategy-reference), making wrong-skill triggering unlikely. Not 2 because it is distinctly bounded rather than overlapping.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents