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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a well-structured, actionable skill that provides concrete browser automation patterns with executable code examples and clear workflows. Its main strengths are the complete code examples for both web and CDP scenarios, the explicit interaction loop with validation steps, and practical guardrails. Minor weaknesses include some unnecessary explanatory text and a CDP Capabilities section that could benefit from being split into a reference file rather than listed inline.

Suggestions

Trim the 'What It Is Used For' section to 2-3 items or remove it entirely since the skill's purpose is clear from the title and opening paragraph.

Consider extracting the CDP Capabilities bullet list into a separate reference file to improve progressive disclosure and reduce the main file's length.

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some sections that could be tightened. The 'What It Is Used For' section is somewhat redundant given the description, and some explanatory text (e.g., 'Use raw CDP only when higher-level browser APIs are insufficient') states things Claude would already know. However, the code examples and guardrails are lean.

2 / 3

Actionability

Provides fully executable JavaScript code examples for both web and CDP harnesses with realistic patterns. The interaction loop, page selection strategy, and selector guidance are concrete and specific. Code is copy-paste ready with clear placeholder conventions (<port>, <debug-port>, <app-root-selector>).

3 / 3

Workflow Clarity

The Setup Pattern provides a clear sequence for getting started. The Interaction Loop is an explicit step-by-step workflow with validation checkpoints (capture before, act, capture after, verify state change). The CDP harness includes error handling with a feedback mechanism (list pages if no match found). Page Selection includes fallback behavior.

3 / 3

Progressive Disclosure

The content is well-organized with clear section headers and logical progression from setup to web harness to CDP harness to interaction patterns. However, with no bundle files, the CDP Capabilities section is a flat bullet list that could benefit from linking to detailed references. The document is moderately long (~100 lines of content) and some sections like CDP Capabilities could be split out.

2 / 3

Total

10

/

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.

This is a strong skill description that concisely covers specific capabilities (CDP harness, screenshots, accessibility snapshots, visual diffs, perf profiles) and clearly states when to use it. It uses proper third-person voice and includes a good range of natural trigger terms. The description is well-structured with a clear 'what' and 'when' separation.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'build or adapt a local browser/CDP harness', 'drive and inspect a web, IDE, or Electron UI', 'screenshots', 'accessibility snapshots', 'perf profiles', 'visual diffs', 'reproducing UI bugs'. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both what ('Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI') and when ('Use for local UI verification, screenshots, accessibility snapshots, perf profiles, visual diffs, or reproducing UI bugs'). The 'Use for' clause serves as an explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'browser', 'CDP', 'screenshots', 'accessibility snapshots', 'visual diffs', 'UI bugs', 'Electron', 'perf profiles', 'UI verification'. Good coverage of terms across the domain, though 'CDP harness' is somewhat technical.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche around browser/CDP-based local UI automation and inspection. The combination of CDP, browser harness, Electron, accessibility snapshots, and visual diffs creates a distinct profile unlikely to conflict with general testing or web development skills.

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.

Validation11 / 11 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.