CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/electron-playwright

Use whenever an Electron desktop app needs end-to-end tests, or a Spectron suite must be migrated: Playwright's _electron.launch, renderer windows as Pages, main-process checks via electronApp.evaluate, and IPC and DOM assertions from one suite.

Quality

85%

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

75%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 highly actionable, well-sequenced skill with executable code at every step and a properly structured two-file bundle for deferred detail. Its main weakness is redundancy: evaluate/firstWindow semantics are explained repeatedly and the Traps section overlaps heavily with the Anti-patterns table, costing tokens without adding guidance.

Suggestions

Merge the 'Traps' subsection into the 'Anti-patterns' table (or vice versa) — items like the evaluate closure capture, firstWindow splash screen, and getFocusedWindow-under-xvfb currently appear in both forms.

Explain electronApp.evaluate's process-boundary semantics once (Step 2) and reference it from Steps 4-6 and the traps instead of restating it in each place.

Trim the per-member API narration in Steps 5-6 in favor of a pointer to the API table in references/electron-ci-and-api.md, which already covers the same members.

DimensionReasoningScore

Conciseness

The body is mostly efficient and Electron-specific, but there is real tightening potential: electronApp.evaluate semantics are explained in Step 2, Step 4, and again in Trap 1; firstWindow behavior is described in Steps 2, 5, and Trap 3; and the 'Traps' section substantially duplicates the 'Anti-patterns' table (evaluate closure capture, firstWindow splash screen, getFocusedWindow under xvfb all appear in both). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Every step ships copy-paste-ready TypeScript or bash: the canonical launch test, the per-platform executablePath resolver, the waitForEvent/Promise.all pattern, a complete playwright.config.ts, and exact npx commands. The common cases (dev launch, packaged launch, multi-surface assertion, secondary windows) are each covered by a runnable example.

5 / 5

Workflow Clarity

Steps 1-10 form a coherent install-to-CI sequence, Step 2's first test doubles as a launch smoke check, and the trace-viewer guidance in Step 8 plus the trap list give error-recovery feedback loops. It falls short of the 5 anchor because there is no explicit checkpoint guidance for iterating when a launch or assertion fails (recovery is scattered across traps rather than sequenced into the workflow).

4 / 5

Progressive Disclosure

The bundle structure is sound: both referenced files (references/electron-ci-and-api.md and references/spectron-migration.md) exist, are one level deep, clearly signaled with markdown links at the exact points they are needed, and hold the deferred material (full API table, CI YAML, Spectron migration). It sits just below the 5 anchor because the ~365-line body re-states API member semantics that also live in electron-ci-and-api.md, so the split is good but not perfectly clean.

4 / 5

Total

16

/

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: it states an explicit 'Use whenever...' trigger covering both new Electron e2e work and Spectron migration, and enumerates concrete API-level capabilities across both process surfaces. The only improvements are adding a few natural trigger synonyms and sharpening the boundary against generic web-Playwright skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete, API-level actions: "Playwright's _electron.launch, renderer windows as Pages, main-process checks via electronApp.evaluate, and IPC and DOM assertions from one suite" — comprehensive coverage of both the main-process and renderer surfaces. It is not merely above the score-4 anchor ('several specific actions; minor gaps') since every capability the skill covers is named explicitly.

5 / 5

Completeness

Both questions are explicitly answered: the 'when' via "Use whenever an Electron desktop app needs end-to-end tests, or a Spectron suite must be migrated", and the 'what' via the enumerated capabilities (_electron.launch, Pages, electronApp.evaluate, IPC and DOM assertions). This matches the anchor for a clear, explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords users would actually say: "Electron desktop app", "end-to-end tests", "Spectron suite", "migrated", "Playwright". A few common variations are missing (e.g., "e2e", "UI tests", "testing Electron apps"), which keeps it at the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The Electron/Spectron scope carves a clear niche with distinct triggers, but the skill ecosystem contains a closely related generic playwright skill (referenced in the body as 'playwright-testing'), and a request like 'write Playwright e2e tests' for an Electron app could plausibly pull both. This is 'mostly distinct; minor overlap risk with closely related skills' rather than minimal conflict 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