CtrlK
BlogDocsLog inGet started
Tessl Logo

control-ui-e2e

Use when testing, fixing, or extending the OpenClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.

69

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-structured E2E skill body with concrete commands, a complete mock-pattern code example, and explicit validation/feedback guidance. Minor conciseness and workflow-organization refinements would push it to the top tier.

DimensionReasoningScore

Conciseness

Lean, sectioned body with executable commands and code that assumes Claude's competence; only minor prose could be trimmed (e.g. the worktree/Testbox guidance paragraph), keeping it just below the leanest anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance: exact vitest invocation, 'pnpm test:ui:e2e', and a complete Playwright mock example with real API calls covering the common chat-flow case.

5 / 5

Workflow Clarity

Clear sequenced workflows (start server -> install mock -> goto -> assert traffic+UI) with an explicit feedback loop on recorder failure; withheld from 5 because the steps are spread across sections rather than one unified validated checklist.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with one-level-deep references to real repo paths (test-helpers, .artifacts dirs) and no nested reference chains; not a 5 only because no separate bundle files exist to offload the detail.

4 / 5

Total

17

/

20

Passed

Description

87%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, well-scoped description with an explicit 'Use when' trigger and many concrete capabilities. It is narrowly tailored to Control UI E2E testing with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions ('testing, fixing, or extending', 'Vitest + Playwright end-to-end checks', 'mocked Gateway WebSocket flows', 'mocked dashboard runs', 'screenshots/videos', 'agent-verifiable browser proof') with only minor overlap/jargon gaps, sitting just below the fully comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what (the E2E/mock/visual-proof actions) and when via a concrete 'Use when testing, fixing, or extending...' trigger clause, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage ('testing, fixing, or extending', 'screenshots/videos', 'end-to-end checks') alongside technical jargon; a few common user phrasings are absent, so it is above the midpoint but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'OpenClaw Control UI GUI with Vitest + Playwright' E2E, a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
openclaw/openclaw
Reviewed

Table of Contents

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.