CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

control-ui-e2e

Control UI browser tests, visual reviews and recordings, interaction performance audits, and Run Inspector evidence.

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exemplary skill body: a checkpoint-driven workflow, terse expert-level operational rules, and clean branch-based navigation to three real one-level-deep reference files, plus a runnable focused-test command. The only minor gap is that most common-case procedures (mock setup, capture helpers) live in the referenced files rather than the body itself.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — e.g. 'Install the mock before navigation. Act through visible controls and assert both the rendered outcome and relevant Gateway requests' — with zero concept explanations or padding; every section delivers operational rules. Not 4 because there is no over-explanation to trim: dense repo-specific facts (fixture helper path, artifact function, suite owners) are stated once, tersely.

5 / 5

Actionability

Provides concrete, executable guidance: a copy-paste-ready command ('node scripts/run-vitest.mjs run --config test/vitest/vitest.ui-e2e.config.ts ...'), a named fixture helper ('ui/src/test-helpers/control-ui-e2e.ts'), and an exact function signature ('createControlUiE2eArtifactDir(scope, parentDir?)'). Not 5 because the most common operations — mock installation, stress-test gallery build, screenshot/trace capture — are delegated to reference files rather than shown, so the body alone doesn't cover the common execution cases.

4 / 5

Workflow Clarity

The four-step workflow is clearly sequenced with an explicit validation checkpoint on every step ('Done: every changed behavior has a named scenario and proof boundary', 'Done: each scenario reaches its asserted outcome, or has a retained failure identifying the unmet assertion'), plus an error-recovery rule ('Resolve unexpected behavior at the product or fixture owner before replaying'). Not 4 because checkpoints are explicit, not implicit, and the failure/retention path is a concrete feedback loop.

5 / 5

Progressive Disclosure

The body is a concise overview with well-signaled, one-level-deep references — [visual proof](references/visual-proof.md), [interaction profiling](references/interaction-performance.md), and [Run Inspector capture](references/run-inspector.md) — all of which exist as real files in the bundle, including a valid anchor ('references/visual-proof.md#ui-stress-test' matches the '## UI Stress Test' heading). Not 4 because navigation is unambiguous per outcome type and no content that belongs in references is inlined.

5 / 5

Total

19

/

20

Passed

Description

66%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 concise, reasonably specific description that names four distinct capability areas anchored to a specific UI surface, with good natural trigger terms. Its main weakness is the missing 'when to use' guidance, which caps completeness and leaves triggering to inference.

Suggestions

Add an explicit trigger clause, e.g. 'Use when running or debugging browser E2E tests for the Control UI, capturing visual/screenshot or video evidence of UI changes, or investigating slow UI interactions.'

Include common user-facing synonyms such as 'E2E / end-to-end', 'screenshots', and 'UI responsiveness' to broaden natural trigger coverage.

Briefly unpack 'Run Inspector evidence' (e.g., 'capturing run/execution receipts') so the term triggers correctly for users unfamiliar with the tool.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — 'Control UI browser tests, visual reviews and recordings, interaction performance audits, and Run Inspector evidence' — which names multiple specific actions with only minor gaps. Not 5 because the actions are terse noun phrases without verbs or detail, and 'Run Inspector evidence' is unexplained project jargon; not 3 because it goes well beyond naming a domain with 1-2 actions.

4 / 5

Completeness

Has a clear 'what' (browser tests, visual reviews/recordings, interaction performance audits, Run Inspector evidence) but no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is entirely absent, which caps this dimension at 3 per the judging guidelines. Not 4 because there is no 'when' statement at all, even a weak or implicit one is barely inferable.

3 / 5

Trigger Term Quality

Contains natural phrases a user would plausibly say — 'browser tests', 'visual reviews', 'recordings', 'performance audits' — giving good keyword coverage. Not 5 because common variations like 'E2E', 'end-to-end', 'screenshots', or 'UI feels slow' are absent; not 3 because the included terms are natural rather than purely technical jargon and cover multiple distinct triggers.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific product surface ('Control UI') with a niche trigger ('Run Inspector evidence'), making it mostly distinct. Not 5 because generic terms like 'browser tests' and 'visual reviews' could overlap with a general testing or visual-verification skill in the same environment; not 3 because the Control UI scoping keeps overlap minor.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

openclaw/openclaw

Path

.agents/skills/control-ui-e2e/SKILL.md

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.