CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/webdriverio-testing

Use for any question or task about WebdriverIO, including converting Selenium code to WDIO and one runner for web and Appium mobile tests: npm init wdio scaffolding, services for Sauce Labs, BrowserStack, Appium and DevTools, spec, Allure and JUnit reporters, and Mocha, Jasmine or Cucumber frameworks.

Quality

82%

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

67%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 highly actionable with concrete, executable code and a clearly sequenced 7-step workflow, organized into clean sections. It is held back by an Overview that explains concepts Claude already knows, a Limitations section overlapping the Anti-patterns table, and small execution gaps (chai dependency, truncated step definitions).

Suggestions

Cut or drastically shrink the Overview's general description of WebdriverIO and its Selenium differentiators — Claude already knows this — and keep only the 'When to use' decision guidance.

Trim the Limitations section, which overlaps the Anti-patterns table and restates common knowledge (e.g. community size relative to Playwright/Cypress).

Make the Mocha example runnable as-is by either noting the chai dependency or using WebdriverIO's built-in matchers, and complete the truncated Cucumber step definitions or point to a reference file with the full set.

DimensionReasoningScore

Conciseness

The Overview section explains what WebdriverIO is and how it 'differentiates from Selenium' (Modern JS/TS API, service architecture) — concepts Claude already knows — and the Limitations section restates common knowledge, so the mostly efficient body includes some unnecessary explanation that could be tightened.

3 / 5

Actionability

Provides near copy-paste-ready material throughout (npm init wdio@latest, a complete wdio.conf.ts, a full Mocha spec, services config, run commands, CI YAML), but has minor gaps: the Mocha example imports chai without noting it must be installed, and the Cucumber step definitions are truncated with '// ... etc.'.

4 / 5

Workflow Clarity

Steps 1–7 give a clear, correctly ordered sequence (Scaffold → Configure → Author → Services → Run → Cucumber → CI) with embedded assertion checkpoints, but there is no explicit validation or error-recovery loop (e.g. what to do when a run fails or how to debug a flaky spec).

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well organized with clear section headers and no broken file references, but at ~240 lines the Cucumber and CI sections are candidates for split-out reference files, keeping it short of the ideal clear-overview-with-signaled-references structure.

4 / 5

Total

15

/

20

Passed

Description

88%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 description with an explicit trigger clause, comprehensive concrete capability list, and good natural keyword coverage including the WDIO synonym. Its only weaknesses are a few missing common trigger phrasings (E2E, browser automation) and slight overlap risk with sibling skills covering Appium, Cucumber and cloud device farms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions within the WDIO domain — 'converting Selenium code to WDIO', 'npm init wdio scaffolding', named services (Sauce Labs, BrowserStack, Appium, DevTools), named reporters (spec, Allure, JUnit) and frameworks (Mocha, Jasmine, Cucumber) — with no meaningful coverage gaps, matching the comprehensive anchor.

5 / 5

Completeness

Both halves are explicit: the trigger clause 'Use for any question or task about WebdriverIO, including converting Selenium code to WDIO' answers when, and the colon-delimited list of scaffolding, services, reporters and frameworks answers what with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage including the synonym pair 'WebdriverIO'/'WDIO' plus Selenium, Appium, Mocha/Jasmine/Cucumber, Sauce Labs and BrowserStack, but common phrasings users would say such as 'E2E', 'end-to-end testing', 'browser automation' or 'cross-browser testing' are missing.

4 / 5

Distinctiveness Conflict Risk

The description is firmly anchored to WebdriverIO, but it stakes claims on Appium, Cucumber, Sauce Labs and BrowserStack territory that closely related sibling skills (e.g. appium-testing, cucumber-testing) may also cover, creating minor overlap risk.

4 / 5

Total

18

/

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