CtrlK
BlogDocsLog inGet started
Tessl Logo

control-ui

Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI. Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs.

80

Quality

100%

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

100%

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

The body is lean and actionable, with executable Playwright code for both web and CDP flows, clearly sequenced workflows with verify checkpoints, and well-organized sections needing no external references. It avoids explaining concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence — it never explains what browsers, CDP, or Playwright are — and every section delivers actionable guidance rather than padded context, fitting the 'lean and efficient' anchor.

3 / 3

Actionability

Provides fully executable Playwright snippets for both launch and connectOverCDP flows, plus concrete guardrails like 'Prefer accessibility roles, labels, and stable data-* selectors over coordinates', matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

Setup Pattern and Interaction Loop are explicitly sequenced, and the loop includes a verify checkpoint ('Verify the expected state change') with before/after capture, giving clear feedback loops.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; content is organized into well-signaled single-purpose sections (Setup Pattern, Generic Web/CDP Harness, Interaction Loop, CDP Capabilities, Guardrails) with no nested references, matching the well-organized anchor.

3 / 3

Total

12

/

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.

The description is specific, uses natural trigger terms, and explicitly pairs a what-statement with a 'Use for...' when-clause in third-person imperative voice. It carves a clear niche around local UI browser/CDP harnessing with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build or adapt a local browser/CDP harness to drive and inspect' plus 'screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ('Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI') and when via an explicit 'Use for...' trigger clause, matching the top anchor.

3 / 3

Trigger Term Quality

Covers natural terms a developer would say — 'UI verification', 'screenshots', 'accessibility snapshots', 'perf profiles', 'visual diffs', 'reproducing UI bugs' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The 'local browser/CDP harness' for 'web, IDE, or Electron UI' niche is specific and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

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.

Repository
cursor/plugins
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.